Updating the Pega Call application
You can use Pega Call™ as part of the Pega Customer Relationship Management (CRM) suite of applications or as a standalone application.
- This document applies only to Pega customers who are running the applications on premises or on a third-party cloud installation.
- In Pega Call used with Pega Customer Service, ensure that both these applications are always on the same patch release version. For example, if your Pega Call version is 8.6.3, then your Pega Customer Service version needs to also be 8.6.3. When you update one of these applications, you need to update the other one as well.
- Perform the procedures that apply to your update scenario:
Update type Required actions Update of Pega Call with Pega CRM suite of applications - Update the CRM suite of applications. For more information, see Pega CRM 8.6 Update Guide on the Pega Customer Service product page or the Pega Sales Automation product page.
- When you update to the latest version of Pega Platform™, if the PerformDefaults, NewDefaults, OpenDefaults, and PreClose extension activities in Pega Call are overridden in the implementation layer, incorporate the changes from the PegaCA-Work or PegaCA-Work-Interaction classes into the implementation layer.
- Import the Pega Call with CRM application bundle. For more information, see Importing the Pega Call with CRM application bundle.
- Disable background class saving. For more information, see Disabling background class saving with JBoss e-Tier.
- Verify your update. For more information, see Verifying your update.
- Optional: If you customized Pega Call rules accessed by service rules, reconfigure service packages or access groups. For more information, see Modifying the service packages and access groups.
- Optional: If you built custom applications with Pega Call, update the version number of your built-on application. For more information, see Setting the version number of your built-on application.
Update of Pega Call without Pega Customer Relationship Management (Standalone) - Import the standalone application bundle. For more information, see Importing the Pega Call application bundle.
- Update the CTIService access group. For more information, see Updating the CTIService access group.
- Disable background class saving. For more information, see Disabling background class saving with JBoss e-Tier.
- Verify your update. For more information, see Verifying your update.
- Optional: If you customized Pega Call rules accessed by service rules, reconfigure service packages or access groups. For more information, see Modifying the service packages and access groups.
- Optional: If you built custom applications with Pega Call, update the version number of your built-on application. For more information, see Setting the version number of your built-on application.
Previous topic Adding the Pega Call security privilege to custom access roles Next topic Importing the Pega Call application bundle