Skip to main content

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

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Avoiding revision management backward compatibility issues

Updated on September 10, 2021

Customizing or changing the underlying process that governs the revision life cycle can cause backward compatibility issues when there are open revisions in the system. To prevent any compatibility issues from occurring, you must resolve all open revisions before you do any of the following types of actions:

  • Upgrade to the latest version of the Pega 7 Platform (the revision management process might change, depending on the Pega 7 Platform version you are upgrading to)
  • Modify the Revision or Change Request case types (for example, by adding or removing stages, steps, or assignments)

You can resolve an open revision or change request by submitting or withdrawing it. If you do not resolve an open revision or change request before modifying a case type or upgrading, any attempt to process an unresolved work object results in an error with an option to remove the revision or change request from the 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