Skip to main content

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

Configuring an application

Updated on July 14, 2022

There are a few requirements and recommendations for structuring an application that is being managed using Deployment Manager. See this brief overview to get started with configuration.

Add PegaDevOpsFoundation as a built-on application

The PegaDevOpsFoundation application provides the capabilities to execute pipeline tasks and adds pipeline integration to the Dev Studio and App Studio. Any application that is being managed by Deployment Manager must include it as a built-on application.

Note: Use the major version of the application so patches and minor versions can be taken without updating the application. For example, include PegaDevOpsFoundation:5 as a built-on instead of PegaDevOpsFoundation:5.1.1.

For new applications

New applications only need to be updated on the development environment. Deployment Manager is capable of migrating the whole application to new environments as part of deployment pipelines.

For applications that have already been deployed to all environments

If the application has already been deployed to all environments, it is required to manually update the application record on each environment to be built on PegaDevOpsFoundation. The next deployment will sync up the application changes and will result in an aged update message on Deployment Manager.

Create a development layer

The target application is regularly packaged and promoted to higher environments so it is important to exclude branches and any other work in progress. A development layer consists of:

  • An application that is built on the testing, or target application. Consider following the naming convention: {TargetApp}Dev.
  • An unlocked ruleset for any developer tools, or work that is never intended to be promoted to higher environments.
  • An access group that logs into the development application.

Development layers can be assigned to developers as needed, whether it is one per application, team or developer.

Using a development layer also allows you to keep the target application locked to prevent unintentional changes.

Create a test layer

Testing assets are managed by Deployment Manager pipelines, but they are only deployed to a subset of environments. To manage and run test cases it is necessary to create a test layer. A test layer consists of:

  • A locked application that is built on the target application. Consider following the naming convention {TargetApp}Tests.
  • A ruleset for all test cases and test assets.
  • An access group that logs into the test application.
  • A product rule that defines which assets get promoted by the pipeline.


If you have followed all the recommendations in this article, you should end up with an application that is structured like the one seen below.

Configured application
Configured application

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