8.8 product changes with update impacts
Adopting Pulse notifications (Pega Customer Service)
Starting in Pega Customer Service version 8.8, the Interaction Portal header displays the Pulse Notifications icon. If you are updating from a previous version, this new icon is hidden by default so that it does not interfere with your existing interfaces. To adopt this feature, see Adopting Pulse notifications.
Setting the toggle for related cases (Pega Customer Service)
To define criteria for case suggestions in App Studio, you must first set the toggle in Dev Studio. For information, see Setting the toggle for related cases.
Setting the toggle for configuration set use (Pega Customer Service)
To take advantage of the new Pega Customer Decision Hub configuration set, you need to enable the UseCDHConfigSet setting. For information, see Setting the toggle for configuration set use.
Optimizing the czRemoteCaseId property (Pega Customer Service)
Starting in Pega Customer Service version 8.8, the czRemoteCaseId database property was optimized to improve reporting and search performance. If updating from version 8.5 or later, and if this property is not already optimized, then optimize this property for your implementation application. Specifically, optimize this property for your work tables in the implementation application class that inherits from PegaCA-Work-Service.
For information, see Optimizing database properties.
Pega Customer Service
You must use the Interaction Portal that was introduced in Pega Customer Service 7. CPM/CSR legacy portals are no longer supported and do not function in this version.
Before updating to the latest version of Pega Platform, drop triggers because SQL database triggers are no longer supported.
Deleting PegaSalesAutomationHybrid system runtime context (Pega Sales Automation or Pega Customer Service)
Perform this action in Pega Sales Automation if present. Otherwise, perform this action in Pega Customer Service.
If you are updating from version 8.6.x or 8.7.x of Pega Customer Service or Pega Sales Automation to version 8.8, to ensure that the product works as expected, delete the system runtime context associated with the PegaSalesAutomationHybrid application from your implementation layer for either of the applications.
Pega Customer Service version 8.8 does not include the PegaSalesAutomationHybrid application. However, the system runtime context associated with the application still exists, and as a result, some rulesets in your Pega Customer Service and Pega Sales Automation resolve to version 8.7 instead of version 8.8. This discrepancy might impact features that use job schedulers or queue processors that are created or modified in version 8.8. Deleting the PegaSalesAutomationHybrid system runtime context is necessary to ensure proper functioning of all the application features.
For information, see Deleting PegaSalesAutomationHybrid system runtime context.
Copying response time-out (Pega Sales Automation)
After the update, copy the response time-out value from Dev Studio to App Studio. Copy the value manually to preserve any customizations of the setting from your pre-8.8 system.
For information, see Copying response time-out.
Updating PegaHCSPM system runtime context (Pega Sales Automation)
If you are updating from an earlier version of Pega Sales Automation™ for Healthcare to version 8.8, doublecheck the system runtime context associated with the PegaHCSPM application in your implementation layer, and ensure that the application version is set to 8.If the application version is set to 8, when you update to the next 8.x version, the system automatically applies the changes in the new version to your implementation layer. However, if you set it to a specific version, for example, 8.5, the system does not apply the changes that are made to the product after that version, in this example, 8.5, to your implementation layer. Setting the correct system runtime context is necessary to ensure that your implementation includes the latest product features..
For information, see Updating PegaHCSPM system runtime context.
Adopting changes to Opportunity case types (Pega Sales Automation)
If you built your implementation application on a Pega Sales Automation™ for Healthcare version prior to 8.8, ensure that your implementation layer includes a change that is made to the Analysis stage in all the Opportunity case types in version 8.8.
In Pega Sales Automation™ for Healthcare version 8.8, for a more guided and logical workflow, an opportunity moves from the Analysis stage to Quote stage immediately after opportunity creation. Some steps that sales representatives previously had to perform in the Analysis stage are now removed, and, therefore, the Analysis stage is now set to automatically move to the next stage rather than waiting for user action. If you built your application on a pre-8.8 version, you must manually replicate this setting in your implementation application, unless you had already customized your application to use the new setting.
For information, see Adopting changes to Opportunity case types.
Adopting changes to Batch Renewal case type (Pega Sales Automation)
After you update from an earlier version to Pega Sales Automation™ for Healthcare 8.8, save the Batch Renewal case type rule from version 8.8 to your implementation layer. Copying the new case type rule is necessary to ensure that the Batch Renewal case type works as expected in your implementation.
For information, see Adopting changes to Batch Renewal case type.
Lead stages sourced from case life-cycle (Pega Sales Automation)
Starting with Pega Sales Automation 8.1, the data page D_crmStages is populated from the stages defined on the lead case type.
If this data page is customized at the client implementation layer, this may not be an issue. In other cases, customers updating from releases prior to 8.1 should manually add the stages to the implementation layer equivalent of the lead case type.
Pega Sales Automation mobile application
The Pega Sales Automation mobile app is an intelligent mobile sales tool that empowers teams to close deals faster, manage the selling process, and collaborate directly from their mobile devices, whether in the office, on the road, at a meeting, or anywhere in the world.
For update-related information, see:
Previous topic Crucial update information for Pega Customer Relationship Management Next topic 8.7 product changes with update impacts