Skip to main content


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

Stages of the Change Request case type

Updated on May 17, 2024

By default, the Change Request case type is the subcase that is created in the first stage of the Revision case type life cycle.

The Change Request case type defines the way that change requests are created, submitted, and resolved. You can modify the stages, steps, processes, or assignments that are part of the Change Request case type to make it simpler or more complex, depending on the business needs.

The primary path in the Change Request case type is represented by the following stages:

StageStepStatusPurpose
CreateDefine ChangesFinalProvide change request details.
Create Change RequestFinalCreate a change request through the designated activity.
OpenView Change RequestAvailableReview the change request. Optionally, update change request details or withdraw it.
Submit for testingSubmit for testingPending-TestingSimulate and test the changes of this change request, before submitting and completing it. Open a Next-Best-Action Designer configuration rule, action rule, or proposition filter rule, and run audience simulations.
SubmitSubmit ChangesFinalSubmit the change request for review and approval.
Approval Required?AvailableDecide whether approval is required.
ApproveApprove ChangesAvailableView the list of rules for approval.
ReassignReassign CRFinalView the rules in the change request to assign back to the originator.

The situations in which you cancel, withdraw, or reject change requests are represented by the following alternate stages:

StageStepStatusPurpose
WithdrawWithdraw ChangesFinalWithdraw a change request in-progress.
RejectReject ChangesFinalReject the change request after it has been reviewed.

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us