Skip to main content

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

Deployment Manager 5.4.1

Updated on December 13, 2021

Deployment Manager 5.4.1 includes the following new features and minor improvements.


This release contains the following new features:

  • Deployment Manager now automatically detects best practice violations, detecting issues early in the deployment lifecycle minimizing production issues. The following new tasks have been added to standardize application quality across all application deployments.
    Note: You can only implement the following tasks if you are using a 5.4 orchestrator and a 5.4 or 4.8.5 candidate environment or above.
    • Validate application testing - Validates if each case type is exercised at least once after a deployment. This is a lightweight task that validates the case instances you create, which is ideal for a staging environment.Deployment Manager returns an error if any case type is not covered as part of the testing.
    • Check application compliance - Validates test rulesets, branches, and missing rule references against the configuration.
    • Validate development standards - Enforces development standards on an application by enforcing guardrails warnings configured through a policy. For more information on policies, see Managing development standards. This task is recommended on both merge and deployment pipelines.
    • Check rule override - Ensures that you do not overwrite any internal Pega rules during branch merge.
  • Deployment Manager now provides a seamless authentication for Pega Cloud services users. For more information, see Quick-start guide for Deployment Manager on Pega Cloud Services.

Bug fixes and minor improvements

Deployment Manager 5.4.1 contains the minor improvements and fix:

  • When you perform a branch merge, you now have access to more information around branch details in the deployment report. This information includes any rules and data instances that are merged, as well as user stories and bug items from your Agile Workbench.
  • On task completion (success or failure), Deployment Manager provides the View output parameters link on the timeline, which displays the details of all output parameters for a given task.
  • You can now save and reuse pipelines, copying all tasks within the pipeline model for a given pipeline type. You can update the pipeline name, application name, and version when you copy a pipeline.
  • The OrchestratorURL and Client Secret now show the Last updated timestamp to help you assess if the configuration was saved after Deployment Manager import.
  • You no longer need to set and save the OrchestratorURL explicitly on the orchestrator. Pega Cloud users can ignore this configuration on the candidate systems.

Dependencies and issues

Note: Updating to Deployment Manager 5.4 overwrites any existing service packages. Any customization to your existing service package is lost at the time of update.

Deployment Manager 5.4.1 contains the following dependencies and known issues:

  • If you update from Deployment Manager 4.8 or 5.1 to the latest version, you must recreate business change pipelines because of an internal property configuration. If you update from Deployment Manager 5.2, you can reuse the existing pipeline.
  • Rolling back to Deployment Manager 5.3 requires you to manually update the service package and change the authentication type from Custom to oAuth2.0.
  • Candidate environments on Pega Platform 8.1 and PegaDevOpsFoundation 4.8.5 must use oAuth2.0 authentication.
  • If the default email account in the orchestrator is not configured, or if the email ID is not configured for a user, Deployment Manager prints an exception stack trace in the logs. To avoid this issue, turn off the logging level for and com.pegarules.generated.pega_integrationengine_default.
  • The enterprise application in a business change pipeline cannot increment a minor version later than 99. You must manually roll over your version if your application or ruleset versions encounter this scenario.
Note: Rolling back to Deployment Manager 5.3 requires you to manually update the service package and change the authentication type from Custom to oAuth2.0.

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