Skip to main content

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

Updating from previous versions of Pega Customer Decision Hub

Updated on August 22, 2022

This section provides information for customers updating to Pega Customer Decision Hub 8.7 from a previous release.

Pega Customer Decision Hub Release Notes

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.

Changes to Pega Next-Best-Action Advisor features

If you use Pega Next-Best-Action Advisor with the default extension strategy rules and supporting decisions, refer to the Pega Next-Best-Action Advisor Upgrade Guide for information about the post-update impact of changes to features such as advertised bundles, channel processing, Q&A weighting, and time-bound decay levers.

Customer Contact Policy moved to Outbound Limits

If you are updating to Pega Customer Decision Hub version 8.7, your Customer Contact Policy will be moved to Outbound Limits. This is a required migration and there is no backward compatibility once Next-Best-Action Designer has been updated to version 8.7. The Quarterly and Yearly policy periods will no longer be supported and therefore will not be updated. If the Customer Contact Policy is not currently in use, meaning that the dates have passed, or have not yet begun, or that the policy is marked as unavailable, but there are policies defined, the policies will be migrated to version 8.7 as a current available Contact Policy.

For more information, see Change from Customer Contact Policy to Outbound Limits.

Converting a change request to fast track is not supported for Pega 1:1 Operations Manager

If your application stack includes Pega 1:1 Operations Manager, after updating to Pega Customer Decision Hub 8.7, the option to convert a normal change request to fast track will no longer be available. You will still be able to create new fast-track change requests.

Deprecated features

The following features are deprecated in Pega Customer Decision Hub 8.7, and will be withdrawn in future releases. It is advised to move away from these features soon and switch to alternatives:

  • Self-optimizing campaigns
    Note: Your existing self-optimizing campaigns will still run and you can edit them. They will still appear on the Campaigns landing page, but they will display indicators and warning messages that they are deprecated. You cannot create new self-optimizing campaigns from the landing page. The Save-as option will still work using the existing self-optimizing campaigns.
  • Microsites
    Note: Your existing Microsites will still work. However, Microsites do not work on new systems created after February 2022 on Pega Cloud due to technical limitations.
  • Analysis projects
  • Samples
  • Non-visual segments
  • Passbooks
  • Visual Business Director (VBD) planner
  • Field Marketing functionality

Do not use these features going forward.

Deprecated and withdrawn rules

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

Rules that were deprecated as part of the OutboundLimits migration from contact policy

Rule typeRule name
Note: Would be generated at customer layer.
Contact PolicyCustomerContactPolicy
Note: Would be generated at customer layer. Replaced by OutboundContactsByPeriod.

If your application references any of these rules, you should save a copy of the referenced rule into your implementation ruleset before you update to version 8.7.

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