Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Creating file templates

Updated on August 4, 2022

To create a new template for file exports, complete the following steps:

Pega Customer Decision Hub
  1. In the Pega Customer Decision Hub portal, click ContentTreatments.
  2. On the Treatments landing page, click CreateFile.
  3. Enter a description of the template.
  4. Select the issue and group for storing the output template rule.
    To create the rule at the top level of your next-best-action business structure, leave the Issue and Group fields empty. The level at which you create the template determines the attributes (action details) that are available for use within the template.
  5. Click Create and open.
  6. Provide the following information:
    1. In the Repository name field, enter the name of the repository where you want to store the file.
    2. In the File path field, enter the path on the repository where you want to store the output file, and the name of the file where you want to store the output content.
      The format for the file path and name is /folder/filename. The file name that you provide is automatically appended with a unique identifier when the file is generated.
      For example: actions/output/mailing-list-kjssbwuamqoo91335643959855560.csv.
      Note: If you configure multiple output templates,each file should have a unique name.
  7. Specify whether you want to finalize the template at the end of each outbound run.
    By finalizing a template at the end of each run, you ensure that all data in the file is the result of a single run. That is, the final output includes all data related to the run that triggered the finalization. If want the data from multiple campaigns to be written to the same file, leave this option unselected.
  8. If you chose to finalize the template at the end of each run, select Include run ID in the file name if you want the file name to include the run ID for easier identification.
    For example: actions/output/mailing-list_PR1-kjssbwuamqoo91335643959855560.csv.
  9. Specify whether you want to include the date and time in the file name when you finalize the template.
    When the template is finalized, the name of the output file includes the date and time configured in the MKTFileNameDateMask dynamic system setting. By default, the format is YYYY-MM-DD-hhmmss
    For example: actions/output/mailing-list_PR1_2020-02-03-111609-kjssbwuamqoo91335643959855560.csv.
    Tip: As a best practice, if you chose to finalize the template at the end of each run, configure the file name to include the run ID, the data and time of the template finalization, or both.
  10. In the Delimiter type field, select the delimiter for the output CSV file.
    Use a delimiter which is recognized by the target repository for the file. Common delimiters include commas (,) and semicolons (;).
  • Previous topic Configuring an action flow to write information to an external system
  • Next topic Creating database templates

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us