Skip to main content

Completing the prerequisite tasks

Before starting the update, review this section carefully! You must complete all required prerequisites to prepare your environment for the update.

Complete the following prerequisites before you update the application.

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 issue. For instructions, see Backing up your system.

  1. When updating from a version that is not the previous version, review the update guides and release notes for each of the interim versions. For example, if updating from release 8.4 to release 8.6, review the 8.5 update guide, 8.5 release notes, and this guide.

    Some product changes, such as deprecated and withdrawn features, require user action before the update. See Pega Community for legacy 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.
  2. If using a Pega Customer Service application, update legacy portals if necessary. For information, see Updating legacy Pega Customer Service portals.

  3. Run the Sales Automation Upgrade Checker to identify rule conflicts in Pega Sales Automation.

  4. Before starting an 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.

    During the application update process, the import tool will have an option to automatically apply database schema updates or extract the database scripts to provide to the database administrators. If the schema updates are executed manually, the jar file installation is paused until the schema updates are applied.

  5. Update to the latest version of Pega Platform 8.6, and ensure that you can log in as an administrator. For more information, see the Pega Platform Update Guide for your environment on the Deploy Pega Platform page.

  6. Determine which language packs are applicable to your product and check for availability.

    For information, see Pega Marketplace.
  7. Optional:

    Because SQL database triggers are no longer supported, before you update the application, have your database administrator check for and drop triggers.

Did you find this content helpful?

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us