Checking Your Code With Live Check Quality extension

1 min read

Once installed and configured, your Live Check Quality extension lets you check and improve your code with best practices from our rulesets. 

You can check the following types of CEs: Classes, Triggers, Pages, Components, Objects, Reports, Workflows, Flows and JavaScript.

These are the steps you need to follow to check your code:

 

    1. Run a LiveCheck.

    1. Check your code.

    1. Fix the issues or request a write off.

Run a LiveCheck #

After installing Live Check Quality for Salesforce v2.1, the developers need to click on ‘Validate Api Key‘ (even if it is already validated when installing the new version) and run a LiveCheck.

These two actions will generate a new local data structure that accommodates the new data needed to show the different tabs inside the ‘Quality Center‘.

Every time you wish, you can run a Live Check on the file you are working on. This runs a check against all our rules.

Prerequisites: The API key need to be successfully validated so that the Quality Clouds can be connected.

→ How to run a LiveCheck?

 

    1. Go to the Explorer section and select a file.

    1. Click on the ‘LiveCheck‘ button which is situated on the bottom part of the screen.

    1. The LiveCheck will take some time to run.

Checking on demand #

After launching a LiveCheck you will be able to check the code and the issues found in the ‘Problems‘ section in the editor.

For all the issues found in the check you can consult the following:

  • Issue type
  • Issue severity (low, medium, high, warning)
  • Quality Gate: Blocker, Minor and Legacy. If it shows NA, it’s because there are no Quality Gates or the write-off requested for the issue has been approved.
  • Line and character number 
  • Link to Best Practice documentation

→ How to check your code #

  1. Go to ‘View‘.
  2. Click on ‘Problems‘.
  3. A panel will appear with all the issues detected on the LiveCheck.

 

Working on issues #

→ How to work on issues #

  1. For each of the issue, you can highlight it in the code by clicking on it from the Problems section.
  2. Check issue severity and open up the best practice link included in the description.
  3. Once you have finished fixing the issue, you can save the file or check again that it does not come up by running the check. 

If fixing an issue, is not an option, you have the option to request a write-off of that issue.

→ How to request a write-off

  1. Click on the ‘Write off‘.
  2. A new window will open.
  3. Complete the form to request a write off.
  4. Click on ‘Request WriteOff‘.

If the write-off has been automatically approved:

  1. A message will pop up saying it has been approved.
  2. In the Problem section, you will see that the write-off of that issue has been approved.

If the write-off its pending:

 

 

Updated on March 21, 2025