Skip to main content

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

Completing the prerequisite tasks

Updated on March 16, 2022
Attention: Before starting the update, review this section carefully! You must complete all required prerequisites to prepare your environment for the update.

This document describes how to update the Pega Customer Service for Communications and Pega Sales Automation applications. Pega Customer Relationship Management for Communications (CRM) provides a single installer for both applications, but each application is licensed separately.

When completing the prerequisites, back up your system after key milestones to ensure that you can revert to the last working version of the system if you encounter an issues. For instructions, see Backing up your system.

Pega Customer Relationship Management for Communications Update Guide
  1. Verify that you have already run the required Pega Customer Service Upgrade Checker. For information, see Pega Customer Service Upgrade Checker.
  2. When updating from a version that is not the previous version, review the update guides and release notes for each of the interim versions. Some product changes, such as deprecated and withdrawn features, require user action before the update. See the Pega Customer Service product page for update guides and release notes. To review a list of the product changes that have update impacts, see Crucial update information for Pega Customer Relationship Management.
  3. Complete all in-flight cases before updating your application. Because of enhancements made in existing cases each release, you might not be able to process the in-flight cases after the update.
  4. Before starting the update, and before backing up your system, review the database policies and application permissions that are used by your Pega Platform update. Determine whether the application is permitted to update the database automatically or if you must generate the database scripts that your organization will use to manually make schema changes. To automatically update the application schema, your access group must have the SchemaImport privilege and the dynamic system setting database/AutoDBSchemaChanges must be set to true. Otherwise, you can create a DDL file to apply the schema changes manually.
  5. Update to the latest version of Pega Platform 8.7, and ensure that you can log in as an administrator. For more information, see the Pega Platform Update Guide for your environment on the Deploying Pega Platform page.
  6. Determine which language packs are applicable to your product and check for availability.
    For information, see Pega Marketplace
  7. Update to Pega Foundation for Communications 8.7 as described in the Pega Foundation for Communications Update Guide.
  8. Apply any hotfixes that are required to support Pega Foundation for Communications before continuing with the update. For more information, see Applying hotfixes.
  9. Update to Pega Customer Service 8.7 and Pega Sales Automation 8.7 base applications. There is a single procedure to update both of those applications. Follow all of the instructions, including prerequisites, in the update guides on the Pega Documentation home page.
  10. Update the optional Pega Product Catalog for Communications application as described in the Pega Foundation for Communications Update Guide. (The Product Catalog for Communications is included in the Pega Foundation for Communications license.)
  11. Apply hotfixes that are required to support Pega product Catalog for Communications 8.7 before continuing with the update. For more information, see Applying hotfixes.
  12. If the distribution media files for Pega Customer Service and Pega Sales Automation include patch releases, import the patch release files before continuing with the update.
  13. Optional: Because SQL database triggers are no longer supported, before you update the application, have your database administrator check for and drop triggers.
  • Previous topic Oracle database users only: Verifying the primary key of the CPMCFW service history table
  • Next topic Backing up your system

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