The below configuration tasks are optional and depend on specific features of your implementation application.
- Updating real-time container configuration
If you use real-time containers and you previously extended the ExtendedContainerProperties data transform with additional properties, copy these properties into the pyDefaultWorkingSet data transform after the upgrade to ensure that the values are populated correctly.
- Configuring properties for use in engagement policies
To make a property available for use in an engagement policy, define it as a Relevant Record for your primary context class, which by default is your Customer class.
- Granting access to the Data menu, data flows, and interaction history summaries
Update the definition of all user groups which should have access to the Data menu, data flows, and interaction history summaries in the Pega Customer Decision Hub portal.
- Running the optimization check utility for decision strategies
Run a post-upgrade utility that checks strategies within your application for areas that you can optimize, for example, by reducing the number of page properties that are copied from one shape to another. Running the utility produces a report that you can use to plan the required updates to your strategies.
- Configuring the data retention period for Visual Business Director
Starting in Pega Customer Decision Hub 8.5, collections data accumulated in Visual Business Director is automatically cleaned out after the time period specified in the vbd/dataRetentionTimeout dynamic system setting. You can configure the time period to match your requirements.
- Enabling the Paid channel in Next-Best-Action Designer
If you use Paid Media Manager, after completing the upgrade, enable the Paid channel in Next-Best-Action Designer. Use the Paid channel to enable advertising on paid destinations, such as Facebook Ads, Google Ads, and others.
- Cleaning the Paid Media master table on successful migration
After a successful migration of customer audience sync data, clean the Paid Media master table and associated artifacts to remove unnecessary data and free up space. By cleaning up the Paid Media master table, you ensure that your system runs smoothly.
- Configuring the PaidMediaSync queue processor to optimize performance
The PaidMediaSync queue processor manages the synchronization queue for Paid Media Manager. To help optimize performance, configure the queue processor as described below.
- Enabling delayed learning for paid strategies
By default, upgrading Pega Customer Decision Hub to version 8.6 disables delayed learning for adaptive models used in paid strategies due to significant performance impact. If you have configured paid strategies that include adaptive models for paid media synchronization through outbound runs, real-time contains, or real-time event triggers, you can continue to use delayed learning, or leave the option disabled and refresh your Next-Best-Action Designer configuration.
- Optional: Assigning operators to new access groups
After you upgrade to Pega Customer Decision Hub, new standard access groups become available in your application. The new groups provide an updated set of access roles and portal permissions. Give your operators the latest access privileges by updating the operator accounts to use the new access groups.
- Setting the response timeout
To trigger a negative feedback signal when the waiting time for an outbound campaign has expired, set the response timeout for the relevant predictions. Starting with Pega Customer Decision Hub version 8.5, you configure the response timeout in a prediction in Prediction Studio.
Previous topic Completing recommended post-upgrade steps