See how Quality Center changes your DevOps quality game → Click HERE 

Quality Center is a centralized workspace that enables developers to improve code quality directly from Salesforce. It brings together QC Livecheck, Feature Branch Scans and Peer Review in a single interface, allowing users to review scan results, track issues, request write-offs, and monitor code quality throughout the development lifecycle.

Authentication via Admin Portal #

You can now authenticate securely through the Quality Clouds Admin Portal, simplifying environment linking from tools.

Step-by-step: #

1. Admin: Create Developer Users

   • Go to Admin Portal > Account > Users

   • Click “Add” or edit an existing user. You can create users in bulk following the CSV template

   • Assign the Developer role

   • Save the user

2. Developer: Activate Your Account

   • The developer will receive an email to set their password

   • Once the password is set, the account is ready to use

      

Connecting Quality Center to Quality Clouds #

All the users must have at least, on of these permission sets to use the application:

• QCLivecheck – This is intended for Developers to use the Quality center. Users with this permission set, will only be able to see their own changes.
• QCLivecheckAdmin – This is intended for users to visualize and track any changes made in the SF Org.
• QCFBScans – This is intented for users to view and track changes made in Feature Branches

 

Step 1: Create an Auth Provider #

• Go to Setup.
• Search for and open “Auth Provider“.

 

Step 2: In the Auth Provider section, click “New” to create a new Auth Provider: #

• Provider Type: QualityCloudsAuthProvider
• Name: QualityClouds
• URL Suffix: QualityClouds
• Execute As: Select a User with QC Admin Permission Set and Manage Users Permission
• Click Save the Auth Provider.
  
  

 

Connect from Quality Center #

• • During integration setup, click Connect to Quality Clouds

    
    
    

  • Log in with your Quality Clouds credentials

  • Select the desired Project from the dropdown

  • Confirm your selection

Your environment is now linked to the selected Quality Clouds project. Once the connection is established, the Quality Center displays two main sections:

• Livecheck – Monitor changes made directly in your Salesforce org, launch QC Livechecks, review issues,, create rules and follow best practices.
• Feature Branch Scans – Review Feature Branch scan results, analyze Quality Gate status, investigate issues, and manage Write-Off requests.

 

These sections provide developers with a centralized workspace to monitor and improve code quality throughout the development lifecycle.

 

Livecheck Section #

The Livecheck section helps developers monitor and improve the quality of configuration changes made directly in the Salesforce org.

It provides visibility into recently modified elements, highlights quality issues identified by QC Livechecks, and enables developers to launch new scans, review active issues, request write-offs, and follow best practices without leaving Salesforce.

The section is organized into four views in the sidebar: All Changes, My Changes, Best Practices, and Pending Approval Rules.

 

All Changes tab #

This tab is only visible for those users who has assigned the permission set: QCLiveChecksAdmin 

Within this tab, user will be able to visualize and track any changes made in the org. 

My Changes tab #

The My Changes screen allows you to track and manage all configuration elements the logged-in user has modified after a selected date. The date filter, set by default to the last month, can be customized to any date range as needed. This enables users to focus on changes made within a specific time frame.

The screen displays key performance indicators (KPIs) related to the modified elements, helping you assess the quality and impact of the changes:

Key Metrics:

• • QC Livecheck Coverage: Displays the percentage of modified elements that have undergone a QC Livecheck scan (launched after the last modification date).
    Example: 28.57% → 20 of 70 modified elements have a valid QC LiveCheck.

• • Blockers: Indicates the number of blocking issues (i.e., issues that failed to pass the quality gate) among all active issues within your modified elements.
    Example: 17 blockers → 17 of 34 issues are blocking.

• • Time to Fix: Estimates the total time required to resolve blocking issues across all active issues.
    Example: 11h 50m → Time required to fix blocking issues, out of 17h 40m for all active issues.

The My Changes tab includes three sub-tabs, each providing a different filtered view of the modified elements:

• • My Changes: Shows all modified elements, scanned or not, for a complete view of your recent changes.

• • Changes with Issues: Lists only modified elements with associated issues to help focus on problem areas.

• • Changes with Blocking Issues: Highlights modified elements with at least one blocking issue, enabling you to address critical problems first.

The table of changes provides key details of the Element such as the date of the last QC Livecheck, along with the count of issues and blockers identified since the scan. Filters are also available to help tailor the view to your needs.

All three tabs allow you to run QC Livechecks, either individually or in bulk, to scan selected elements for issues. This flexibility helps you evaluate the quality of your modifications and take appropriate action as needed.

Active QC Livecheck Issues related list #

In the My Changes tab, for each element that has a valid QC Livecheck and, has issues associated with it, a Related List is displayed. This list contains all the Active QC Livecheck issues found for the element, sorted by their Quality Gate status (“blocker” first). Each issue in the list includes key information such as:

• • Severity: Defines the criticality of the issue and its potential impact on the system.
    
    • • Categories: High, Medium, Low, Warning

• • Impact Area: Indicates the domain within the application that is affected by the issue.
    
    • • Categories: Security, Manageability, Scalability, Performance

• • Line: Identifies the exact line of code where the issue is located, helping developers quickly navigate and resolve the problem.

• • Quality Gate: Classifies the issue based on its severity and impact area to block code promotion or deployment.
    
    • • Categories: Blockers, Minors, Legacy
        
        • • Blocker: issues blocking the Quality Gate. 
        • • Minor: issues not blocking the Quality Gate.
        • • Legacy: issues introduced before the QG activation date.

• • Write-Off Status: Tracks the approval status of any write-off requests associated with the issue.
    
    • • Categories: Requested, Not Requested, Approved, Solved, Expired, Declined

• • Link to Best Practice Documentation: Provides direct access to the documentation that describes the best practices for resolving the issue.

When you click on an issue in the related list, a pop-up window displays detailed information about the specific issue. The pop-up is organized into several sections:

Issue Details #

This section provides a thorough explanation of the issue, including its impact on the element and the associated quality gate. 

The following fields are displayed:

• • Issue Type

• • Org Issue Type Count (Total number of issues of this type across the org)

• • Estimated Fix Time (Time required to fix the issue, in minutes)

• • Severity

• • Impact Area

• • Quality Gate Categorization

• • Line Number (Location in the code where the issue was found)

• • Documentation (Link to relevant best practice guidelines)

QC Livecheck #

This section provides information about the QC Livecheck triggered on the element, including details on the scan and its results:

• • Quality Gate Status: Indicates whether the quality gates for the element passed or failed during the QC Livecheck.

• • Issues: Number of issues found in the QC Livecheck related to the element where the opened issue was detected.

• • Date: The date when the QC Livecheck was launched.

Affected Element Information #

This section provides key details about the element where the identified issue was found, helping users quickly understand the context of the issue and where it needs to be resolved. 

The following information is displayed:

• • Element Name: The name of the element where the issue was detected.

• • Element Type: The type of element related to the issue.

• • Created On: The date when the element was created.

• • Created By: The user who initially created the element.

• • Updated On: The date when the element was last modified.

• • Updated By: The user who last updated the element.

If needed, you can Run a New QC Livecheck to trigger a new QC Livecheck scan on the element, ensuring that any changes are validated and the element complies with the latest quality standards.

QC Copilot (add-on) #

This section allows the user to request an AI-recommended fix for the issue. By clicking the QC Copilot action button, the AI provides a solution to resolve the problem. 

When QC Copilot generates a fix, the following fields are displayed:

• • Generated By: The user who requested the fix recommendation.

• • Description: A detailed explanation of the issue, including its cause and how it will be resolved. This section provides clear guidance on understanding the problem and the steps to fix it.

• • Recommendation: The AI-generated code changes that address the identified issue.

Users can provide feedback by rating the recommended fix.

Additionally, there is a Compare Code feature. Clicking this button allows the user to compare the original code with the new code recommended by QC Copilot, displaying the exact changes made by the AI.

Request a Write-Off #

This section allows the user to request or cancel a write-off for the issue. 

Once requested, the following fields are displayed related to the write-off request:

• • Write Off Status: The current status of the write off request.

• • Peer Review ID: If the request triggers a peer review workflow, the associated ID will be shown.

• • Write-Off Reason: The selected reason for the write off.

• • Write-Off Request Description: A description provided by the user explaining the reason for the write off request.

• • Write-Off Requester: The user who requested the write off.

• • Write-Off Requested Date: The date when the write off request was made.

• • Write-Off Validator: The user who validated or approved the request (if approved).

• • Write-Off Validation Date: The date when the request was validated or approved.

These features allow developers to effectively manage and resolve issues directly within the Quality Center, streamlining the process of maintaining code quality.

Best Practices Tab #

The Best Practices screen provides a comprehensive list of all active best practices (rulesets) within the org. It helps developers proactively avoid common issues by applying optimal configurations.

The list is ranked by the frequency of associated issues, offering valuable insights into which practices are most frequently violated. This feature serves as both a proactive guide and a learning tool, empowering developers to anticipate potential problems and configure elements more effectively.

By default, the screen displays only “My Issues,” enabling users to focus on their own challenges. Users can adjust this filter to view issues across the entire org, gaining a broader perspective on frequent practices and identifying trends in the overall codebase.

Each best practice includes a count of associated issues (detected by QC Livechecks) and a separate column to highlight how many of these issues are classified as blockers.

Fields visible in the Best Practices table: Best Practice, Link to Documentation, Element Type, Issues, Blockers, Severity, Impact Area, Time to Fix, Last Modification Date of the Rule.

Additionally, users can view the Active QC Livecheck Issues related list for each best practice, showing Element Name, Owner, Quality Gate Categorization, Last Modification Date, and Write-off Status.

This setup allows users to quickly navigate to the elements where the issues were found, facilitating faster resolution and better adherence to best practices.

 

The Best Practices tab includes a Create New Rule button, which opens Rule Builder. See Rule Builder for Salesforce for the full step-by-step. Once a rule is submitted, it appears in the Pending Approval Rules list, shown in the Quality Center sidebar alongside Best Practices, until it is reviewed and approved.

For the full step-by-step, including how rules are tested and activated, see Rule Builder for Salesforce.

 

Feature Branch Scans #

The Feature Branch Scans section provides developers with direct access to Feature Branch scan results from Github, GitLab, etc.

It allows users to review scan outcomes, track Quality Gate status, analyze detected issues, and manage write-off requests. This gives developers complete visibility into the quality of their feature branches during the development lifecycle.

The landing page displays all Feature Branch scans available to the logged-in user.

Each scan includes key information to quickly identify its status and quality:

• Repository
• Branch Name
• Scan Date
• Scan Status
• Quality Gate Result
• Total Issues
• Blocking Issues

 

Users can filter and sort the list to quickly locate specific scans. Selecting a scan opens the detailed analysis for that execution

Scan Details View #

Selecting a Feature Branch scan opens the detailed view, providing a complete summary of the scan results.

The page includes:

• Overall scan information
• Quality Gate result
• Number of issues by category
• Estimated remediation time
• Complete list of detected issues

 

Issues can be filtered by Quality Gate status, severity, impact area, write-off status and other available filters, allowing developers to focus on the most relevant findings first.

Issue View #

Selecting an issue opens a detailed panel containing all the information required to understand and remediate the finding.

The issue details include:

• Rule name
• Description
• Severity
• Impact Area
• Quality Gate categorization
• Estimated Fix Time
• Affected file
• Line number
• Link to the corresponding Best Practice documentation

 

Request a Write-Off
#

Feature Branch Scans also support single or bulk Write-Off requests.

Users can select one or multiple issues and submit a Write-Off request, providing the appropriate justification for all selected findings.

This streamlines the review process by reducing repetitive actions while maintaining the existing approval workflow and audit trail.