Salesforce Executive

 See the high-level details of your org, including the Quality of Cloud, your best practices, org inventory and your team. 

Ways to use the view

With the executive view, you can immediately and continuously monitor the quality of your platform. Here are a few of the ways you might use the executive view:

  • checking the headline KPIs for your platform
  • check what's in your platform and stay up to date with its applications in Inventory
  • managing all creators on the platform
  • checking for training needs (shows strengths and weaknesses)
  • checking vendor transparency
  • reviewing the best practices, and rules that apply to your platform and check what issues they are resulting in
  • exporting detected issues and sharing with your testers, developers and architects to save you time and money

What data is shown

The (Beta) Executive view shows the relevant information across the following tabs:

Overview tab

Here you can check your high-level quality metrics:

Quality of Cloud

Widget

The Quality of Cloud shows indication of the overall health of your instance or org. Healthy instances range between 80% and 100%. Those between 70% and 80% need a close monitoring about further developments. A percentage below the 70% figure means that the cloud needs remediation work. See more in Quality of Cloud indicator.

Issues

In the Issues section, you can see the information on issues detected on the platform, its breakdown, evolution and details.

Widget

The widget shows the following details:

  • total number of issues of all severities detected in the last scan (each issue is a single non-compliance with best practice)
  • the percentage variation which is the main metric difference in percentage between the current and the previous scan
  • the issue information from the previous scan
  • the information without issues that have been written off
  • the issue number according to the baseline ruleset. See more about baseline.


In this section you can filter the information displayed in the graphs, trend and on the grid by the following elements:

  • Severity
  • Impact Area
  • Issue Type
  • CE Type
  • Application
  • Developer
  • Show written off

Note, once you have applied your filter, it stays applied when you change to another view.


Graphs

The graphs show you the following information:

Hover over the pie selection to see how many issues make up each severity.

Issues by Severity

Here you can compare which issue severity is the most common.

Issues by Impact Area

Here you can check which area is most impacted by issues. 


Trend - Issues over time

See the Issues over time and issues open at scan date. 


Grid

See the list of all the issues detected by a given scan. You can sort the table columns to see, for example, the High (Severity) issues for Security (Impact Area).

Back to top


Technical debt

The Technical debt section shows you information on the implied cost in hours of development effort needed to solve the issues/violations detected in the platform due to non-adherence to best practices and changes to the out-of-the-box functionality. 

Widget

The widget shows the following details:

  • the current technical debt
  • the percentage variation which is the main metric difference in percentage between the current and the previous scan
  • the technical debt information from the previous scan
  • the Global technical debt (TD) which shows the technical debt including all non-coding activities, such as analysis, project management, testing and release management
  • the technical debt according to the baseline ruleset. See more about baseline.


In this section you can filter the information displayed in the graphs, trend and on the grid by the following elements:

  • Severity
  • Impact Area
  • Issue Type
  • Application
  • Developer

Note, once you have applied your filter, it stays applied when you change to another view.


Graph - Issues and technical debt by issue type

The graph shows you the the top 10 issues and their impact on issues and technical debt.

Hover over each line to see the exact number of issues and the technical debt in hours for each issue, as well as it's impact and remediation you can do.


Trend - Issues and technical debt over time

See the relation between issues and technical debt as progressing over time.


Grid

See the list of all the issue types detected by a given scan together with the number of hours of technical debt, exact number of issues, its impact and remediation. 

Back to top

Lines of code scanned

In the Lines of code scanned section you can see the information about total number of lines of code analyzed in the last scan. 

Widget

The widget shows the following details:

  • the number of lines of code scanned in the given scan
  • the percentage variation which is the main metric difference in percentage between the current and the previous scan


In this section you can filter the information displayed in the graphs, trend and on the grid by the following elements:

  • CE Type

Note, once you have applied your filter, it stays applied when you change to another view.


Trend - Lines of code scanned over time

See the progression of lines of code scanned over time. 


Grid

Here you can see the lines of code scanned for each scan. 

Back to top

Ratio of CEs with issues

The Ratio of CEs with issues is the ratio of Configuration Elements (CEs) affected by one or more issues, and it shows how easy it would be to do remediation. High ratio means that the issues are all over the code which means it will be difficult to remediate. Low ratio means that issues are concentrated, which, in turn, makes them easy to rework.

The Ratio of CEs with issues section shows the information about the ratio.

Widget

The widget shows the following details:

  • the ratio in the given scan
  • the percentage variation which is the main metric difference in percentage between the current and the previous scan


In this section you can filter the information displayed in the graphs, trend and on the grid by the following elements:

  • CE Type

Note, once you have applied your filter, it stays applied when you change to another view.


Trend - issues and ratio of CEs with issues over time

See the relation between issues and the ratio as progressing over time. 

Grid

Here you can see the ratio and issues for each scan. 


Back to top

Configuration elements

Configuration elements are any object or component which Quality Clouds scans, such as an 'Apex class' or 'custom object' in Salesforce.

The Configuration elements section shows all the CE information.

Widget

The widget shows the following details:

  • the number of all configuration elements in the given scan
  • the percentage variation which is the main metric difference in percentage between the current and the previous scan


In this section you can filter the information displayed in the graphs, trend and on the grid by the following elements:

  • CE Type

Note, once you have applied your filter, it stays applied when you change to another view.


Trend - configuration elements over time

See the progression of the number of configuration elements scanned over time. 


Grid

Here you can see the exact number of configuration elements scanned for each scan. 


Back to top


Best Practices tab

Here you can check the best practices and rules that apply to your instance and the resulting issues.

Best practice

A standard to follow for optimal platform quality.

Rule

A Quality Clouds definition of best practice which contains the resulting issue severity, the area it is impacting, associated technical debt and the remediation.

Issue

Non-compliance with a best practice/rule.


Number of best practices

Here you can see the total number of rules that are applied to the last platform scan.

Widget

The widget shows the following details:

  • the total number of rules that are applied to the last platform scan
  • the percentage variation which is the main metric difference in percentage between the current and the previous scan
  • the number of ignored rules
  • the number of customized rules
  • the number of added rules
  • the total number of rules in the baseline ruleset. See more about baseline.


In this section you can filter the information displayed in the graphs, trend and on the grid by the following elements:

  • Severity
  • Impact Area
  • Issue Type
  • CE Type
  • Application
  • Developer

Note, once you have applied your filter, it stays applied when you change to another view.


Graph - number of issues by issue type

Here you can check which rules generate most issues.


Grid

Here you can see the exact list of issues for each scan. 

Back to top

Data privacy

Shows you the information related to your data privacy. All the issues detected here are impacting Security.

A data privacy (or GDPR) issues are raised whenever a matching PII keyword is found in code or field or table names. See more in GDPR - General Data Protection Regulation and GDPR (General Data Protection Regulation) best practices.

Widget

The widget shows the following details:

  • the number of all issues detected for data privacy
  • the percentage variation which is the main metric difference in percentage between the current and the previous scan
  • the number of issues with sensitive data (such as home address or email address) 
  • the number of issues with extra-sensitive data (such as race, religion, gender or credit card number)
  • the number of issues with private data


In this section you can filter the information displayed in the graphs, trend and on the grid by the following elements:

  • Severity
  • Issue Type
  • Application
  • Developer

Note, once you have applied your filter, it stays applied when you change to another view.


Trend - data privacy issues over time

See the progression of the number of GDPR issues detected over time. 


Grid

Here you can see the exact list of GDPR issues detected for each scan. 

Back to top

Issue breakdown

The Issue breakdown section is an informative section that shows you the details of all issues distributed into three main categories: Apex , Java script and org config issues. 

This is not an interactive section.

Widget

The widget shows the following details for each breakdown category:

  • the number of all issues detected for in the current scan
  • the percentage variation which is the main metric difference in percentage between the current and the previous scan
  • the issue information from the previous scan
  • the visual trend showing the progress over time

Back to top


Inventory tab

Here you can see the composition of your org.

Use this tab to review your org after the first scan and then monitor the progression of changes to the org.

Total applications

The Total applications sections shows you the information about applications installed or developed in your org.

Widget

The widget shows the following details:

  • the total number of all applications in your org
  • the percentage variation which is the main metric difference in percentage between the current and the previous scan
  • the application information from the previous scan
  • the trend of applications over time


In this section you can filter the information displayed in the graphs, trend and on the grid by the following elements:

  • Application (depending on the applications you have)
  • Package Type (downloaded - for the packages downloaded from AppExchange, developed - for packages developed in house)

Note, once you have applied your filter, it stays applied when you change to another view.


Graphs

The graphs show you the following information:

Hover over the pie selection to see how many CEs make up each application.

CEs by Application

Here you can compare which application has the most CEs.

CEs by Package Type

Here you can check how many CEs have been downloaded and how many developed.


Trend - configuration elements by package type over time

See the progression of the number of configuration elements scanned over time. 


Grid

Here you can see the exact list of all CEs for each of your applications. 

Back to top

Lines of code

In the Lines of code section you can see the information about total number of lines of code in applications in the last scan. 

Widget

The widget shows the following details:

  • the number of lines of code scanned in the given scan
  • the percentage variation which is the main metric difference in percentage between the current and the previous scan
  • the number of lines of code from the previous scan
  • the visual trend of lines of code over time

Graph - lines of code by application

Shows you the division of the number of lines of code between the developed applications.

Grid

Here you can see the exact lines of code scanned for each developed application. 

Back to top


Configuration elements

Configuration elements are any object or component which Quality Clouds scans, such as an 'Apex class' or 'custom object' in Salesforce.

The Configuration elements section shows all the CE information.

Widget

The widget shows the following details:

  • the number of all configuration elements in the given scan
  • the percentage variation which is the main metric difference in percentage between the current and the previous scan
  • the number of configuration elements from the previous scan
  • the visual trend of configuration elements over time


In this section you can filter the information displayed in the graphs, trend and on the grid by the following elements:

  • Application (depending on the applications you have)

Note, once you have applied your filter, it stays applied when you change to another view.


Trend - configuration elements by type

See the progression of the number of configuration elements scanned over time and divided by type.

 


Grid

Here you can see the exact number of configuration elements by type scanned for each scan. 

Back to top

Open source libraries

The Open source libraries shows the open-source JavaScript libraries detected in the instance. Loosing visibility on installed libraries or not updating them properly exposes your instance to risks.

Widget

The widget shows the following details:

  • the number of all open source libraries detected in the scan 


Grid

Here you can see the exact details of the downloaded libraries, including library name and version.


Back to top

Issues

In the Issues section, you can see the information on issues detected on the platform, its breakdown, evolution and details.

Widget

The widget shows the following details:

  • total number of issues of all severities detected in the last scan (each issue is a single non-compliance with best practice)
  • the percentage variation which is the main metric difference in percentage between the current and the previous scan
  • the issue information from the previous scan
  • the visual trend of issues over time


Graphs

The graphs show you the following information:

Hover over the pie selection to see how many issues make up each application and package type.

Issues by Application

Here you can compare which application has the most issues.

Issues by Package Type

Here you can check which package type has the most issues. 


Grid

See the list of all the issues detected by a given scan. You can sort the table columns to see, for example, the High (Severity) issues for Security (Impact Area).

Back to top


Teams tab

Here you can see the information about your teams and team members, check the productivity and code quality.

Team members

In the Team members section, you can see the information on your developer and non-developer team members.

Widget

The widget shows the following details:

  • total number of team members
  • the percentage variation which is the main metric difference in percentage between the current and the previous scan
  • the number of developers on the team
  • the number of end users (non-developers) on the team
  • the number of developers working on the instance in the last 3 months (active)
  • the number of end users working on the instance in the last 3 months (active)


In this section you can filter the information displayed in the graphs, trend and on the grid by the following elements:

  • Severity
  • Impact Area
  • Issue Type
  • Application
  • Developer
  • All CE Types

Note, once you have applied your filter, it stays applied when you change to another view.

Trend - Issues and number of developers over time

The graphs show you the relation between the number of developers and the number of issues detected in the platform.

Grid

See the list of all the team members and their contribution to the platform.

Open each developer to see the details by application and by CE.


Back to top

Productivity

Productivity is defined by Quality Clouds as the number of CEs created by developer.

The Productivity section shows the related information. 

Widget

The widget shows the following details:

  • the average productivity per developer
  • the total number of CEs
  • the visual trend of productivity over time


In this section you can filter the information displayed in the graphs, trend and on the grid by the following elements:

  • Developer
  • All CE Types

Note, once you have applied your filter, it stays applied when you change to another view.

Graph - Number of CEs created by developer (productivity)

See the productivity comparison for all developer users. 

Trend - Issues and number of developers over time

The graphs show you the relation between the number of developers and the number of issues detected in the platform.

Grid

See the list of all the team members and their contribution to the platform.

Open each developer to see the details by application and by CE.


Back to top

Issues and warnings

In the Issues and warnings section, you can see the information on issues and warnings detected on the platform, its breakdown, evolution and details.

Widget

The widget shows the following details:

  • total number of issues and warnings of all severities detected in the last scan (each issue is a single non-compliance with best practice)
  • the percentage variation which is the main metric difference in percentage between the current and the previous scan
  • the issue information from the previous scan
  • the information without issues that have been written off
  • the visual trend of issues and warning over time


In this section you can filter the information displayed in the graphs, trend and on the grid by the following elements:

  • Severity
  • Impact Area
  • Issue Type
  • Application
  • Developer
  • All CE Types

Note, once you have applied your filter, it stays applied when you change to another view.


Graph - Issues and warnings by developer

Here you can compare which developer created the most issues.

Hover over the pie selection to see how many issues were created by each developer.

Trend - Open issues at scan date

See the Issues over time and issues open at scan date. 


Grid

See the list of all the issues and warnings detected by a given scan. You can sort the table columns to see, for example, the High (Severity) issues for Security (Impact Area).

Back to top

Inventory

In the Inventory section you can see the information about total number of lines of code in applications in the last scan. 

Widget

The widget shows the following details:

  • the number of all configuration elements in the given scan
  • the percentage variation which is the main metric difference in percentage between the current and the previous scan
  • the number of configuration elements from the previous scan
  • the visual trend of configuration elements over time


In this section you can filter the information displayed in the graphs, trend and on the grid by the following elements:

  • Application (depending on the applications you have)
  • All CE Types (or Only Customization)

Note, once you have applied your filter, it stays applied when you change to another view.


Graph- configuration elements by developer

See the progression of the number of configuration elements scanned over time and divided by type.

You can filter the graph by developer. 

 


Grid

Here you can see the exact configuration elements by created and updated by a given developer. 

Back to top

Code quality

Code quality is defined in Quality Clouds as the average number of issues to lines of code.

In the Code quality section you can see the relevant information. 

Widget

The widget shows the following details:

  • the average number of issues to lines of code
  • the percentage variation which is the main metric difference in percentage between the current and the previous scan
  • the code quality from the previous scan
  • the visual trend of code quality over time


In this section you can filter the information displayed in the graphs, trend and on the grid by the following elements:

  • Developer
  • All CE Types (or Only Customization)

Note, once you have applied your filter, it stays applied when you change to another view.


Graphs

The graphs show you the following information:

Code quality ratio

Here you can compare the code quality of all/selected developer with an average.

Selected vs total code

Here you can compare the code quality of all vs selected code.  


Grid

Here you can see the exact list of issues and warnings detected in the scan. 


Back to top

What's here


Related content

Find your way around Views




Last modified on Oct 7, 2020