Naming pattern changed for file output templates

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 upgrade, 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.

Checklist functionality removed

In previous releases of Pega Customer Decision Hub you could use the Checklist feature to list actionable steps that need to take place in order for your Action/Campaign to be accomplished. The Checklist functionality has been removed and is no longer available in the Pega Customer Decision Hub 8.6.

Deprecated and withdrawn rules

The following rules are withdrawn in Pega Customer Decision Hub 8.6:

Deprecated strategy shape

The Interaction history strategy shape is considered deprecated in Pega Customer Decision Hub 8.6, and will be withdrawn in future releases. If your strategies use this shape, you should rework them to use the Interaction history summary shape instead.

Deprecated unversioned propositions

Unversioned propositions are considered deprecated in Pega Customer Decision Hub 8.6, and will be withdrawn in future releases. If your strategies use unversioned propositions, you should rework them to use versioned propositions instead.

Customer Journeys refactored

In the 8.6 release, Pega refactored the Customer Journeys to better align with the opinionated approach to customer engagement with Next-Best-Action Designer.

If you previously implemented Customer Journeys, you will be impacted by this upgrade and your existing Customer Journeys will become inaccessible. You will need to recreate all existing Customer Journeys within Next-Best-Action Designer. Note that there is no upgrade or migration script, so you will have to recreate all Customer Journeys manually.

For more information, see Creating a customer journey.