Skip to main content

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

Troubleshooting output templates

Updated on September 15, 2022

Use the following troubleshooting tips to help solve issues related to output template processing.

Pega Customer Decision Hub

Issue: After updating to version 8.6, files generated from output templates are no longer recognized by downstream processing logic

File output templates export data out of Pega Customer Decision Hub in the form of files which can be imported into another tool. Before version 8.6, the file created from a template used the name specified in the template configuration, without a unique identifier.

Starting in Pega Platform 8.6.3, each file name has a unique identifier, automatically generated based on the data flow node, thread ID, and timestamp. Because of that, if your process to consume output files expects files with a specific name, it may not be able to process the resulting files correctly.

If you have configured the process before updating to Pega Customer Decision Hub version 8.6, but the exported files are no longer recognized by downstream processing logic after the update, ensure that the downstream tool is configured to recognize the files by a pattern rather than the full name. For example, use Export*.csv instead of the file name to refer to files exported to the repository.

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