Skip to main content
LinkedIn
Copied!

Table of Contents

Data management for upgrading and patching highly available systems

Version:

Only available versions of this content are shown in the dropdown

Follow Pega best practices for production data management to ensure successful upgrades and patches.

Organizations seeking to use rolling restarts and split schema to perform minimal or no down time upgrades or patches must plan for production data management. To ensure that data is migrated to the production system:

  • If new rules and data are backward-compatible, import the application or framework RAP into production after a rolling restart, upgrade, or patch. Any new content in existing data tables and changes to work queues are visible immediately.

    To make new rules available at the next login, configure:

    Authorization/RSLUpdateBehavior = fixedreq
  • If new rules and data are not backward-compatible, import the application or framework RAP into production after a rolling restart, upgrade, or patch at a period of low to no activity. New rules, work queues, and data tables are visible immediately upon next login.
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