Analyzing a compliance score
Version:
Analyze your compliance data to find the root cause of a low compliance score. By taking action when your application's score is less than 80, you can improve application quality more quickly.
-
Find your compliance score.
-
In the header of Dev Studio, click
. -
In the Compliance score section, review your weighted score.
-
- Optional:
To broaden the scope of your compliance data, include built-on applications.
-
Click application, and then select one or more built-on applications.
-
Click Apply.
-
-
Identify the highest priority issues that affect your score.
-
Click the Compliance Details tab.
-
In the Warning impact section, click the values in the Resolve now column.
-
Review the list of rules with severe warnings.
-
In the Application risk introduced by operator section, take note of the user with the highest risk percentage.
-
Click the percentage, and then review the list of rules with warnings that the user added to your application.
-
-
Identify the types of rules with the most warnings.
-
Click the Warning Summary tab.
-
In the # Rules with warnings column, review the distribution of warnings across the different types of rules.
-
Expand the row for the rule type with the highest number of warnings.
- Optional:
For more information about a specific rule, click a rule name in the Rule column.
-
-
Review how your compliance score has changed over time.
-
Click the Compliance Score tab.
-
In the Rules modified on or after field, enter a date, and then click Apply date filter.
-
Related Content
Article
Compliance score logic