Establishing quality standards in your team
Defects discovered in production environments cost significantly more to resolve than those identified during development. Introducing low-quality features into production creates technical debt, which shifts resources from innovation to remediation. To reduce this risk, all changes must undergo rigorous review and testing before advancing through the CI/CD pipeline. Pega Platform™ reinforces this principle by embedding automation, AI-driven governance, and proactive compliance checks throughout the development lifecycle.
Traditional methods depend on manual reviews and static documentation, which often result in delays and inconsistencies. Pega Platform transforms quality assurance into a predictable, automated process by using generative AI and integrated CI/CD guardrails to enforce standards seamlessly.
Establishing standard practices for your development team can help you prevent issues and focus on delivering new features to your users. Some practices to consider include:
- Using Branch reviews.
- Establishing a Rule check-in approval process.
- Addressing guardrail warnings.
- Creating custom guardrail warnings.
- Monitoring alerts and exceptions.
These practices help your team ensure that the application meets the highest quality standards before promoting it to other environments or including changes in the continuous integration pipeline. By implementing these practices, your team can detect bugs early, confirm that changes do not break existing functionality, and deliver high-quality features to users. This approach minimizes technical debt and reduces the risk of issues in production environments, resulting in a better user experience and greater business value.
Using Branch reviews
To improve application quality, conduct Branch reviews before merging code into the main codebase. This practice helps detect bugs early, maintain scalability, and share knowledge across the team. Reviews also enforce adherence to best practices and coding standards.
Tools and best practices:
- Use the Branch Quality landing page to monitor guardrail warnings, merge conflicts, and unit test results.
- Maintain a high compliance score and ensure thorough testing before merging.
- Collaborate by using Pulse for review assignments and closure notifications.
Pega Platform extends quality assurance beyond manual reviews by embedding automated checks and reporting into your pipeline. These features help enforce compliance, accelerate testing, and support audit readiness:
- Automate compliance checks in your CI/CD pipeline using pxCheckForGuardrails to block unsafe merges.
- Enable parallel testing for faster validation during pipeline runs.
- Generate compliance reports as part of pipeline artifacts for audit readiness.
By combining manual reviews with automated CI/CD guardrails, your team ensures that code changes are thoroughly reviewed, tested, and compliant, which results in higher-quality applications and improved user experiences.
For more information, see Branch reviews.
Establishing check-in approval
The check-in approval process is essential for maintaining application quality and preventing defects from entering the main codebase. Without proper governance, unchecked changes can introduce errors, increase technical debt, and compromise system stability. Pega Platform elevates this process from a manual checkpoint to an intelligent, automated quality gate that accelerates delivery while maintaining compliance.
Key practices for effective check-in approval:
- Configure dynamic approval workflows by using the Check-In Approval Process tool.
- Integrate guardrail compliance and automated quality gates into CI/CD pipelines.
- Apply shift-left testing with unit, UI, and security validations before approval.
- Use intelligent review assistance for risk analysis and reviewer recommendations.
Addressing guardrail warnings
Guardrails are essential for maintaining application quality and preventing technical debt. They ensure that applications follow best practices and remain stable as they evolve. The Application Guardrails dashboard provides a centralized view of compliance scores, warnings, and key indicators that help teams identify issues early and take corrective action.
To prevent violations from impacting delivery, guardrail compliance must be part of the development workflow, not a one-time activity. Modern practices embed automated guardrail validation into CI/CD pipelines by using Deployment Manager. These validations enforce compliance thresholds and block deployments that fail standards. Automated quality gates also run unit tests, UI tests, and security scans before promotion to ensure that functional and non-functional requirements are met.
Teams should review and resolve warnings regularly to avoid delays. Intelligent tools highlight critical issues and suggest corrective actions, while custom guardrail warnings allow organizations to enforce policies for high-risk scenarios. This proactive approach ensures governance without slowing delivery.
For more information about the reporting metrics and key indicators that are available on the landing page, see Application Guardrails landing page.
For more information about managine warnings, see Improving your compliance score.
Creating custom guardrail warnings
Custom guardrail warnings help organizations enforce specific development standards and prevent high-risk practices. These warnings allow teams to identify and address violations that go beyond standard guardrails, ensuring compliance with internal policies.
By using Dev Studio, you can configure custom guardrail warnings for Rules that require special attention. For example, if your organization wants to flag any Activity Rule by using the Obj-Delete method, you can create a warning that requires justification before the rule is promoted to another environment. This ensures that potentially destructive operations are reviewed and approved.
Modern practices enhance this feature by integrating Custom Guardrail checks into CI/CD pipelines by using Deployment Manager. Automated validation ensures that Rules that trigger custom warnings cannot move forward without proper justification, reducing risk and improving governance. Intelligent tools also assist by highlighting these warnings and suggesting corrective actions, making compliance faster and more accurate.
Monitoring alerts and exceptions
Promoting applications that contain unresolved alerts and exceptions can cause production issues and reduce user experience. To maintain stability and performance, proactive monitoring is essential.
Pega Diagnostic Center (PDC) provides real-time visibility into application health. It monitors performance, identifies essential issues, and sends alerts before problems affect users. PDC supports Pega Cloud® deployments and on-premises environments, so that teams can identify and resolve issues quickly. Modern practices integrate PDC insights into CI/CD pipelines by using automated checks to stop deployments when essential alerts are detected. This approach helps ensure that only stable, high-quality applications move forward.
In addition to PDC, use PegaRULES Log Analyzer (PLA) to download and analyze application and exception logs. PLA helps identify patterns and root causes of errors, which supports continuous improvement and reducing technical debt.
By combining real-time monitoring, automated governance, and intelligent analysis, organizations maintain application stability, prevent production failures, and deliver a consistent, high-quality user experience.
For more information, see Pega Diagnostic Center.
Apart from PDC, use the PegaRULES Log Analyzer (PLA) to download and analyze the contents of the application and exception logs. For more information, see PegaRULES Log Analyzer (PLA).
Check your knowledge with the following interaction: