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.

Stage-based revision and change request management

Updated on September 10, 2021

Revision and change request processes are based on the case management capability provided by the Pega 7 Platform. The change from flow-based to stage-based revision management in this release makes both revision and change request more transparent and easier to modify. Based on specific requirements and factors that influence various types of businesses, you can edit stages, steps, processes, and assignments that are part of either case type to make it simpler or more complex. The customizable flows that controlled the behavior of the revision and change request management processes (pyManageRevision, pyManageChangeSet, pyApproveChangeSet, and pyDirectDeployment) are now part of two case types that govern the behavior of revision management:

The Revision case type covers all aspects of the life cycle of a revision.

.Revision case type screen

Revision case type

The Change Request case type controls how change requests are created, submitted, and resolved.

Change Request case type screen

Change Request case type

  • Previous topic Rule creation and simulations of changes in a change request in the Decision Manager portal
  • Next topic Scaling decisions and managing data

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