Skip to main content


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

Resolving revisions

Updated on July 5, 2022

As a revision manager, assess whether the rule updates are satisfactory. If you approve of the changes, you can submit the revision for deployment. Before you can submit a revision, you must approve all change requests that comprise that revision.

  1. Log in to the Pega Customer Decision Hub portal as an operator with the RevisionManager access role.
  2. On the Home screen, in the Work under Revision Management section, open a change request that the strategy designer completed.
  3. In the Scope of changes section, inspect the rule changes.
  4. To accept the changes, click Approve.
  5. Click Submit.
  6. Repeat steps 2-5 for each change request associated with the revision that you want to submit for deployment.
  7. After you resolve all change requests that comprise a revision, ensure that you understand the impact of the changes by selecting the Simulate revision action.
    Simulating the revision tests the changes using predefined simulation settings. Make sure that you understand the impact of the changes before deploying the revision.
  8. Submit that revision for deployment to other environments.
    • The recommended way to deploy your revisions is by using Pega Deployment Manager 4.8 or newer. For more information, see Deploying revisions with Deployment Manager.
    • Alternatively, you can manually package the revision for deployment by clicking SubmitDownload revision. After that, you can manually import the revision into the target environment. For more information, see Optional: Managing revisions manually.

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