Here’s your grand chance to set the calendar of Topics for our Ask the Expert sessions for 2020!! Let us know the Topics you would like to see discussed. We could also repeat of the Topics we had in 2019. ...

For a more complete list of questions and troubleshooting tips for Deployment Manager, please reference: Deployment Manager FAQ and Troubleshooting tips. ...

All users who are using the Deployment Manager portal should be logging in using the PegaDeploymentManager:Administrators access group. All users who interact with pipelines via merge requests, or One Click Deployment should exist on the system with an ap ...

For on prem customer, our recommendation is to always have a separate environment to the Deployment Manager orchestrator. This is how it is deployed for our Pega cloud customers and it provides the following benefits ...

There are two key requirements in order to make Deployment Manager work across VPCs ...

The ideal configuration for Deployment Manager to be installed on a separate Pega environment, referred to as an orchestrator. The reasons to install the Deployment Manager application in a separate environment is Ensure that the orchestrator environment ...

No, the defaultstore represents the temporary folder associated with the Pega node. It is a system (platform) managed repository and should not be relied to store or persist artifacts. Many of the challenges associated with the use of the Pega repository ...

No, Deployment Manager does not support using the Pega repository type to store application artifacts as part of the pipeline deployment. The Pega repository type currently is only supported the Rebase feature in the platform, and in the future the Rebase ...

There really is no need for two different repository instances to be used, you can use the exact same repository for a pipeline. Deployment Manager will automatically create two folders, <repository location> /devops/dev and <repository location& ...