Deployment Manager version 5.5.2 includes the following enhancements:
Bug fixes and improvements
- Deployment Manager now provides the option to abort a
deployment that is in the queue.
For more information see Stopping a deployment.
- The system enables the DMAgentUser operator automatically after you start Deployment Manager for the first time.
- New user roles now do not include the PegaRULES:SysAdm4
Note: Only the SuperAdmin role includes the PegaRULES:SysAdm4 access role.
- Pipelines do not get stuck because of invalid email addresses to which Deployment Manager sends notifications.
- The artifact name is now consistent in both the development and production repositories.
- Email notifications about deployment progress now have more informative titles. Each email title includes the name of the pipeline and its current stage.
- In Deployment Manager, you can now remove tasks during the first stage of deploy
Note: Create a new deploy artifact pipeline in case you need to edit the pipeline. Deployments on existing deploy artifact pipelines are not impacted.
- In business change pipelines, you can now add an optional task at the end of
each stage. In this way, progressing to the next stage depends on the completion
of that task.
For more information, see Creating a business change pipeline.
- Do not use DevOps environment for development. If you use Deployment Manager instance for multiple roles, users with non-Deployment Manager access group set as default can experience issues while using the Deployment Manager portal. To fix this issue, update the Custom applications access group with the DeploymentManager:User role, and add PegaDeploymentManager application as a build-on application.