This lesson introduces the core capabilities of Quality Clouds that help organizations monitor platform health, enforce governance, and maintain high development standards across Salesforce environments.
Quality Clouds combines automated analysis, development validation, and governance workflows to support teams throughout the entire development lifecycle.
The following capabilities form the foundation of the platform.
Platform Scan
Platform Scans provide a comprehensive analysis of the entire platform environment, allowing organizations to assess overall quality, technical debt, and potential risks across their Salesforce Orgs or Git repositories.
Platform Scans evaluate the full codebase and configuration of the platform. This allows teams to obtain a complete picture of platform health and identify issues that may affect maintainability, security, performance, or governance.
Platform Scans generate detailed findings that feed into QC Views, analytics dashboards, and governance workflows, enabling teams to monitor trends, track remediation progress, and prioritize improvement efforts.
By running Platform Scans regularly, organizations can maintain continuous visibility into their platform quality and ensure that their environments remain stable, secure, and aligned with best practices.
QC Views for Reporting, Analytics and Metrics
Quality Clouds provides a wide range of QC Views that allow teams to monitor platform health, analyze trends, and track technical debt over time. These dashboards offer visibility into key metrics such as:
- Technical debt evolution
- Code quality trends
- Development activity
- Risk areas across the platform
- AI readiness and governance insights
By transforming technical findings into clear visual reports, QC Views help architects, platform owners, and leadership teams understand platform quality and prioritize improvement efforts.
QC Livecheck
QC Livecheck enables teams to validate quality during development by running automated checks against platform best practices.
It allows developers to detect issues early and ensure that changes comply with governance policies before progressing through the development lifecycle.
Livechecks can be executed at different levels depending on the scope of the changes being validated.
Livecheck on Configuration Elements
Livechecks can be executed on individual configuration elements, allowing developers to validate specific components while they are being developed.
This provides immediate feedback on code quality and best-practice compliance. In Salesforce, configuration elements may include:
- Apex Classes
- Apex Triggers
- Flows
- Lightning Web Components (LWC)
- Custom Objects
- Custom Fields
- Validation Rules
- Profiles and Permission Sets
Running Livechecks at this level helps developers identify issues such as performance risks, security vulnerabilities, or coding standard violations before committing their changes.
Feature Branches Scans
Scans can also be executed on Feature Branches, allowing teams to analyze all the changes included in a development branch before merging them into the main codebase.
A Feature Branch Scan evaluates all modified components within the branch, providing a comprehensive view of the quality impact of the feature being developed. This capability helps teams:
- Validate the quality of a complete feature before merge
- Detect issues across multiple related components
- Ensure that development changes meet governance standards
By analyzing the full scope of a feature, teams can ensure that only compliant and high-quality changes are integrated into the main branch.
Quality Gates
Quality Gates provide an automated governance mechanism that ensures development changes meet the organization’s defined quality standards before they progress through the development lifecycle.
Quality Clouds analyzes detected issues and classifies them based on severity and impact area. When a change includes issues that violate these policies, the Quality Gate will fail, preventing the change from progressing until the issues are resolved or properly reviewed.
Quality Gates can be applied to both Salesforce org environments and Git repositories, ensuring that development quality is validated regardless of whether teams are working directly in the platform or through a Git-based development workflow.
Configuring Quality Gates
Quality Gates are configured by Customer administrators within the Quality Clouds platform.
Administrators define which types of issues should be considered blocking issues based on the organization’s governance policies. These rules determine which findings must be resolved or reviewed before development changes can be promoted. For example, administrators can configure Quality Gates to block issues such as:
- Security vulnerabilities
- Performance risks
- Scalability problems
- Manageability issues
By defining these policies, organizations can ensure that the most critical issues are always addressed before deployment.
Enforcing Governance
When a scan detects blocking issues, the Quality Gate will fail, indicating that the change does not meet the required quality standards.
This automated validation ensures that non-compliant changes cannot progress through the development pipeline, helping organizations maintain consistent governance, reduce technical debt, and protect production environments.
By embedding Quality Gates into both platform development workflows and repository-based pipelines, Quality Clouds ensures that quality validation is enforced consistently across the entire development lifecycle.
Peer Review process
Peer Review provides a governance mechanism that allows teams to review and validate decisions related to quality issues before changes are promoted across environments.
In Quality Clouds, Peer Review is commonly used as part of the Write-Off process. When a developer identifies an issue that cannot or should not be fixed immediately, they can request to write off the issue, providing a justification for why the issue should be accepted.
The Peer Review process ensures that these requests are properly evaluated by another team member or technical lead before they are approved.
Write-Off Approval Process
When requesting a write-off, the developer provides:
- A write-off reason
- A description explaining the justification
- The affected configuration element or code component
Once submitted, the request enters the Peer Review workflow, where a reviewer can:
- Approve the write-off, accepting the issue as an exception
- Reject the request, requiring the issue to be resolved before the change progresses
This controlled approval mechanism ensures that quality standards remain enforced while still allowing flexibility for justified exceptions.
Governance and Accountability
By introducing Peer Review into the write-off process, organizations ensure that exceptions are reviewed, documented, and approved transparently.
This helps maintain strong governance practices, prevents misuse of issue write-offs, and ensures that quality standards are consistently applied across development teams.
QC Copilot
QC Copilot is an AI-powered assistant designed to help developers resolve quality issues more efficiently. When an issue is detected, QC Copilot can generate recommendations explaining:
- The root cause of the problem
- Best-practice guidance
- Suggested code changes to resolve the issue
By accelerating problem resolution, QC Copilot helps developers maintain high quality standards while improving productivity.
Teams Assignation Rules
The Teams capability allows organizations to automatically assign issues detected during scans to the appropriate development or platform team. This ensures that the right team is responsible for addressing the findings and helps streamline remediation efforts across large organizations or multi-team environments.
Automatic assignment is configured through Team Assignment Rules, within the Quality Clouds Portal, which allow administrators to define how issues should be routed based on specific criteria.
Team Assignment Rules
Administrators can create rules that automatically assign issues to a team when a scan detects findings that match defined filters. These rules can use different filter criteria, including:
- Application – Assign issues related to a specific application or module to the responsible team.
- Configuration Element Name – Route issues based on specific components or elements name.
- Configuration Element Type – Assign issues based on element types such as Apex Classes, Flows, or Business Rules.
- Impact Area – Route issues based on categories such as Security, Performance, or Scalability.
- Rule – Assign issues triggered by specific best practices.
- Severity – Assign issues based on severity levels such as High, Medium, or Low.
By combining these filters, administrators can create flexible assignment rules that ensure issues are automatically routed to the most appropriate team.
Improving Accountability
Automatic issue assignment helps organizations:
- Clearly define ownership of quality issues
- Accelerate remediation workflows
- Improve collaboration between development teams
- Maintain accountability across large platform environments
This capability is especially valuable during Full Platform Scans, where a large number of issues may be detected and need to be distributed efficiently across multiple teams.
Quality Center
Quality Center provides a centralized workspace where Salesforce developers can monitor their work, validate quality, and manage issues during the development process.
For Salesforce environments, Quality Center can be accessed directly within the Salesforce org or through the Quality Clouds extension in Visual Studio Code, allowing developers to integrate quality validation into their daily development workflow.
By bringing quality insights closer to the development environment, Quality Center enables developers to review their changes, run validations, and address issues without switching between multiple tools
Key Capabilities
Quality Center provides several capabilities designed to help developers maintain high-quality development standards, including:
- Running QC Livechecks on configuration elements during development
- Reviewing detected issues and understanding their impact
- Accessing Best Practice documentation to guide issue resolution
- Tracking configuration elements that have been modified
- Managing write-off requests and Peer Review approvals
These capabilities allow developers to validate their work continuously and ensure that changes comply with the organization’s quality standards.
