Variables & Templating Skill

Substitute runtime placeholders in filenames, folders, and email content.

75|8|Updated Dec 20, 2023
One-click install
npx skills add https://github.com/flowkraft/datapallas --skill variables-templating-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Variables & Templating Skill
Source: https://github.com/flowkraft/datapallas/tree/main/asbl/src/main/external-resources/db-template/_apps/flowkraft/_ai-hub/.skills/datapallas-variables
Command: npx skills add https://github.com/flowkraft/datapallas --skill variables-templating-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of producing personalized, correctly routed documents and messages at burst time without manually editing filenames, paths, or email content for every output.

Core Features & Use Cases

  • Built-in runtime variables for burst tokens, input document metadata, extracted file paths, and timestamped archiving (e.g., burst_token, input_document_name, now?string formats).
  • User-defined variables extracted from your source reports (PDF XML-style tags <0>...</0> through <19>...</19>, or Excel burst metadata via a userVariables column).
  • Configurable application points where variables can be used, including burst file names, output/backup/quarantine folders, FTP/SFTP/HTTP upload commands, and email fields (To/CC/BCC, subject, body, and mail server settings).
  • Use Case: Generate customer- and date-specific invoice PDFs and emails by naming files like ${var1}-${burst_token}-${var0}.pdf and archiving them into customer/year-quarter folders automatically.

Quick Start

Use this Skill to replace placeholders such as ${burst_token} and ${var0} in your burst file name, folder, and email subject/body so each produced document and message is personalized from the report runtime.

Frequently Asked Questions about Variables & Templating Skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I personalize PDF filenames and email subjects during document bursting?

Document bursting personalizes filenames and email subjects by substituting runtime placeholders like ${burst_token} and ${var0} with report-extracted values. This enables dynamic routing and personalized message generation without manual edits.

What syntax is required for variables in document templating?

Document templating requires correct ${variable_name} syntax for runtime substitution. You can extract user-defined variables from source reports using XML-style PDF tags (<0>..</0> to <19>..</19>) or Excel userVariables column mappings.

Can I automatically route burst PDFs to customer-specific folders and FTP destinations?

Yes, you can route burst PDFs to customer-specific folders and FTP destinations by configuring variables within output folder paths and FTP, SFTP, or HTTP upload commands. This ensures each document reaches its correct destination automatically.

How do I extract custom values from Excel burst metadata for email personalization?

To extract custom values from Excel burst metadata for email personalization, map a userVariables column in your source report. These values populate placeholders in email To, CC, BCC, subject, body, and mail server settings at runtime.

Why are my document templating variables not resolving at runtime?

Document templating variables fail to resolve at runtime due to incorrect ${variable_name} syntax or improper placement. Ensure your PDF XML tags (<0>..</0>) or Excel userVariables mappings are correctly formatted and carefully positioned so values are found.