Deployment Manager 4.8.2
Deployment Manager 4.8.2 includes the following new feature and resolved issues.
The following new features are available in this release:
- You can now independently perform package and deploy actions with ad hoc tasks, outside of the context of a deployment.
- The connection timeout of rest connectors can now be customized as a user-input value (in milliseconds) through a new dynamic system setting, DMConnectorTimeOut. The value specified should be greater than 30000 (30 seconds), otherwise, the default value specified in the rest connector will take precedence.
The following issues were resolved in this release:
- Unable to create new roles for usersThe add role functionality failed if a description for the role was not provided. This dependency has been removed, and roles can now be created with or without descriptions.
- External links to documentation were not workingThe hyperlinks to Pega documentation, including user guides and release notes, were not updated properly for the 4.8 release. This issue has been resolved and all documentation is now accessible from within Deployment Manager.
- Users without permissions to manage aged updates were not prompted with an error or manual intervention request during deployment. If a rule or data instance in an application package is older than an instance on a system to which you want to deploy, this is considered an aged update. If this is encountered by a user without permissions to manage aged updates, the user will be notified during the deployment process.
- If a draft flow was withdrawn or marked as "not draft" in a previous ruleset version, this caused an error on all subsequent deployments using a higher version of that ruleset. Draft flows have the ability to cause unintended failures if deployed to a production environment, and any ruleset containing draft flows (even if archived) would result in this error. Draft flows now marked as not available, blocked, or withdrawn are ignored during deployment.
- Changing the assigned resource of a task would overwrite the task name in the Pipeline model UI Task resources, names, and descriptions can now be edited as intended directly in the pipeline model.
- People landing page only showed 50 usersPagination restricting the amount of shown records has been disabled, and all users can now be viewed.
- Unable to create a pipeline if a previous version had failedResubmitting a modified, resolved version of a previously failed pipeline would result in a stage duplication error due to a caching issue with the case life cycle properties. This has been resolved and pipelines that fail can be modified and recreated as necessary.
- No indication of URL redirects in diagnostics or logs A new category has been added to the Verifying intersystem connections page, which identifies URL redirections when connecting to development environments.
- Deployment Manager configured with Jenkins resulted in a JSON parsing error when trying to run a jobInvalid data field values were provided due to an incorrect data transform script. The activity has been modified to resolve this issue.
- Logs provided incorrect user information regarding publishing and approving artifacts All log actions throughout the deployment process were previously associated to the operator who started the deployment. Now, all actions are properly associated to the users who performed them.
- Application version field only allowed numeric valuesApplications can now be versioned alphanumerically.
- Schema changes did not properly update in the target environment.Deploying an artifact with schema changes now properly applies the updates in the target environment as requested.