Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Analyzing a compliance score

Updated on April 5, 2022

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.

Before you begin: Encourage your team to check in their work so that you have complete data.
  1. Find your compliance score.
    1. In the header of Dev Studio, click ConfigureApplicationQualityGuardrailsCompliance Score.
    2. In the Compliance score section, review your weighted score.
  2. Optional: To broaden the scope of your compliance data, include built-on applications.
    1. Click application, and then select one or more built-on applications.
    2. Click Apply.
  3. Identify the highest priority issues that affect your score.
    1. Click the Compliance Details tab.
    2. In the Warning impact section, click the values in the Resolve now column.
    3. Review the list of rules with severe warnings.
    4. In the Application risk introduced by operator section, take note of the user with the highest risk percentage.
    5. Click the percentage, and then review the list of rules with warnings that the user added to your application.
  4. Identify the types of rules with the most warnings.
    1. Click the Warning Summary tab.
    2. In the # Rules with warnings column, review the distribution of warnings across the different types of rules.
    3. Expand the row for the rule type with the highest number of warnings.
    4. Optional: For more information about a specific rule, click a rule name in the Rule column.
  5. Review how your compliance score has changed over time.
    1. Click the Compliance Score tab.
    2. In the Rules modified on or after field, enter a date, and then click Apply date filter.
What to do next: Use the findings from your analysis to focus your improvements on specific rules and warnings, and coach individuals on development best practices.

    Have a question? Get answers now.

    Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

    Did you find this content helpful?

    Want to help us improve this content?

    We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

    Close Deprecation Notice
    Contact us