Thank you to everyone who participated in our recent webinar on Mastering Pega Deployment Manager Pipelines! The session generated excellent questions that provided deeper insights into pipeline configurations, best practices, and upcoming features. Below is a compilation of the most valuable Q&A exchanges from the session.

Watch the Complete Webinar

If you missed the webinar or would like to revisit the content, you can watch the recording here: Mastering Pega Deployment Manager Pipelines

Authentication & Access

Q: Does Deployment Manager as a service support SSO now?

A: Yes, Deployment Manager supports federated authentication login in addition to Pega community credentials. The federated authentication feature replaces the custom SSO authentication previously provided. Once enabled, this authentication method applies to all Pega applications including Deployment Manager, PDC, MSP, etc. To opt into this feature, contact [email protected].

Q: Is there Dev Studio access for Deployment Manager as a service?

A: No, similar to PDC, there is no Dev Studio access for Deployment Manager as a service. Modern implementations use prescriptive, generic, auto-generated, auto-registered configurations that don't require manual Dev Studio adjustments. Deployment Manager as a service uses secure one-way communication with your environments, providing full control on your candidate side without needing Dev Studio access.

Pipeline Configuration & Functionality

Q: In the merge template, can we configure or provide options to reuse existing ruleset versions instead of creating new ones upon every merge?

A: Currently, we have two options when creating a merge pipeline: merge to the highest ruleset version or create a new version. While there have been requests for more granular ruleset version control, implementation has been challenging due to potential implications for CI/CD processes and best practices. This remains an area of consideration for future enhancements.

Q: Can one product rule be deployed from DEV to SIT, then subsequently from SIT to UAT, then from UAT to Production?

A: The recommended approach is to use one product rule and follow the path from left to right (DEV → SIT → UAT → Production) using the same package throughout. Creating different packages at different stages can lead to loss of control and consistency. Development should always be up-to-date with the latest changes, with consistent environments across your route-to-live path.

Q: Can we deploy React JS applications with Deployment Manager?

A: No, Deployment Manager is not designed to deploy React JS applications, as these follow a completely different development process outside of Pega. For JavaScript applications (React, Angular, etc.), it's better to use specialized tools designed for JavaScript application deployment. Any components eventually integrated with Pega can be packaged as a ruleset inside Pega and deployed as part of the Pega product.

Testing & Performance

Q: When doing deployment or merge, the run Pega Unit Test task execution takes considerable time to execute the unit tests. Is there any way to improve the speed of Unit Test execution?

A: With Infinity 25, there's an enhancement to the unit testing framework that introduces parallelized execution. This significantly improves testing speed when running all tests in the context of your application. This enhancement will soon be integrated with Deployment Manager. Additionally, you can configure specific test suites to run instead of all unit tests to reduce execution time.

Q: Can we configure PDM to run regression automation suite every day off-working hours?

A: Currently, there's a capability to schedule pipeline deployments on a daily basis, but specifically scheduling just the automation test suite task is not yet available. This has been noted as feedback for consideration. In the meantime, you could use the Deployment Manager API in conjunction with Jenkins or Azure DevOps to schedule test executions.

Integration & GenAI Features

Q: Apart from Jenkins, will there be any new OOTB automations coming in future PDM?

A: Yes, there are plans to expand integration capabilities. GitHub Actions integration is expected in H1 2026. Azure DevOps integration is already available, including for on-premise versions.

Q: How does Pega GenAI tie into Deployment Manager?

A: Several GenAI features are already available in Deployment Manager service:

1. A deployment assistant that answers contextual queries around the product
2. Error analysis with suggestions that point toward root cause and next steps
3. Coming soon: Deployment summary that highlights manual interventions, approvals, and other key elements of a deployment

Roadmap & Support

Q: Is Deployment Manager 5 on Marketplace being deprecated for client-managed setups?

A: Deployment Manager 5 is in extended support for Pega Cloud clients. For on-premise or client-managed setups, it will continue to be supported for the foreseeable future, but with focus on critical fixes rather than major enhancements. Support will align with supported platform versions - if you're using an older platform version, newer versions of DM5 may not be supported.

Q: What is the roadmap for standalone Deployment Manager? Will that product still evolve?

A: The standalone version will continue to be supported for currently supported platform versions, but major feature development is focused on Deployment Manager as a service. The on-premise version already provides comprehensive capabilities with 30-40 out-of-the-box tasks and a robust API for automation, meeting most needs of on-premise implementations.

Complex Scenarios & Advanced Topics

Q: How do we handle a setup with multiple versions of the same applications with different ruleset stacks to allow parallel development?

A: This scenario typically requires separating structures based on production readiness (current production, mid-term releases, and long-term pilots). Multiple pipelines may be needed to support different releases, with proper orchestration and alignment across teams. This topic will be covered in more detail in part two of this webinar series.

Q: Is there anything on the roadmap to support deploying constellation components?

A: Currently, Constellation components that generate standard rules can be packaged as a product itself, but specific React components deployment is not part of Deployment Manager service. The React components development process is handled separately, while any rules generated can be packaged and deployed through Deployment Manager.

We received many more excellent questions than we could address in detail during the webinar. We'll be covering advanced topics including custom tasks, migration paths, and complex deployment scenarios in part two and three of this webinar series, scheduled for December 2025 and January 2026.

Have additional questions? Please post them in the comments below or join our next webinar session!