Skip to main content

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

Configuring the finalization schedule for a file or database template

Updated on September 15, 2022

Configure the finalization schedule, notifications, and post-finalization activity for the output template.

Note: Because the finalization takes place after action initiation, it does not work for actions in waiting state.
Pega Customer Decision Hub

Finalizing a template writes any pending data to the output file or table. For file templates, finalization converts the staging output template <container name>_LOCK table) to its proper version (without lock in its name). For database templates, this happens only if you select the the Overwrite existing data writing option.

Pega Customer Decision Hub uses the standard queue processor for template finalization. If you want to use a dedicated queue processor, add a new dynamic system setting called CDHDedicatedFileDBQueueProcessor, and set its value to true.

Tip: If you configure the output template to be finalized after action initiation, you do not need to enable scheduled finalization. As a best practice, enable scheduled finalization for templates that capture data for actions triggered by mechanisms other than outbound runs, such as real-time events or containers.
  1. In the Schedule section, select the Enable schedule check box to configure when and how frequently to finalize this output template.
    Tip: As a best practice, do not schedule the template to be finalized more often than every 30 minutes. Finalizing the template too frequently can result in unexpected behavior.
  2. Optional: In the Delivery options section, configure the notification that you want to send when the template is finalized.
  3. Optional: In the Advanced section, configure a post-finalization activity for this output template:
    1. In the Task name field, enter a name for the task.
    2. In the Task description field, enter a description for the task.
    3. In the Activity class field, select the Applies To class of the post-finalization activity from the list.
      Note: The post-finalization activity must reside in the PegaMKT-Work-Offer class or in one of its descendant classes.
    4. In the Activity name, select the post-finalization activity (Rule-Obj-Activity) from the list.
What to do next: After you specify the contents of an output template, you can configure the following outbound shapes in an action flow to write to the template:
  • Send Email
  • Send SMS
  • Send Generic
  • Sent Multiple Treatments
  • Previous topic Configuring the contents of a file or database template
  • Next topic File and Database landing page details

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