Skip to main content


Deployment Manager 1.1.2

Suggest edit Updated on April 13, 2020

Deployment Manager 1.1.2 includes the following known and resolved issues.

Known issues

The following issue exists in this release:

  • The PegaDevOps-ReleaseManager agent points to the wrong access group.

    Because this agent is not associated with the correct access group, it cannot process Deployment Manager activities in the background.

    To resolve the issue, after you import and install Deployment Manager 01.01.02, perform the following steps on the orchestration server:

    1. Update your Pega Platform application so that it is built on PegaDeploymentManager 01.01.02:
      1. In the Designer Studio header, click the name of your application, and then click Definition.
      2. In the Built on application section, in the Version field, press the Down Arrow key and select 01.01.02.
      3. Click Save.
    2. Update the agent schedule for the Pega-DevOps-ReleaseManager agent to use the PegaDeploymentManager:Administrators access group.
      1. In Designer Studio, click RecordsSysAdminAgent Schedule.
      2. Click the Pega-DevOps-ReleaseManager agent.
      3. Click Security.
      4. In the Access Group field, press the Down Arrow key and select PegaDeploymentManager:Administrators.
      5. Click Save.

Resolved issues

The following issue was resolved in this release:

  • Selections that were made to the Start build on merge check box were not applied when editing a pipeline.

    When you edit a pipeline and either select or clear the Start build on merge check box, your changes are now applied. Additionally, the check box is cleared by default.

Did you find this content helpful? YesNo

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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us