Clayton

Detect types of automation, such as workflows, record-triggered Flows, and Apex triggers, that are used on the same object

Multiple automation on the same object

Detect multiple record-triggered Flows on the same object.

Multiple record-triggered flows on the same object

Detects any call to a method that is part of a block list.

Call to blocklisted method

Detect Flows that don't use Fault Paths on every step

Missing fault path in Flows

Detects methods that can be referenced from outside a managed package.

Identify methods with global visibility

Prevent the use of asynchronous Apex methods (@future) inside loops, to help your application cope with larger volumes of data properly.

Asynchronous methods in loops

Ensure all SOQL statements are either bound by either a LIMIT or by a WHERE clause.

Boundaries on SOQL statements

Ensure your Apex triggers can process data in bulks and properly deal with larger volumes.

Bulkification of triggers

Detect the presence of non-trivial business logic inside Apex triggers.

Business logic in triggers

Ensure your components are up to date with a recent enough version of the Salesforce API.

Metadata API recency

Detect multiple triggers on the same object, and prevent non-deterministic behaviours.

Multiple triggers per object

Keep your code easy to read and test by containing the use of nested conditional structures.

Nested IFs

Limit the number of arguments allowed for each method to keep your code easy to read and maintain.

Number of arguments per method

Limit the number of methods allow per each Apex class, to encourage good design.

Number of methods per class

Prevent uses of Messaging.sendEmail inside loops, to reduce the risk of running into governor limits.

Send email in loops

Detect calls to Schema.getGlobalDescribe that are inefficient and could be optimized, in order to reduce resource consumption and latency.

Inefficient calls to Schema.getGlobalDescribe

Starting Spring ’25, Salesforce no longer renders extra spaces between classes or empty class="" or style="" attributes

Use of spaces in attribute class selectors

Lorenzo Frattini

Gabriele Gallo Stampino

David Martin

Coding best practices

Home

Find answers and get help from Intercom Support and Community Experts

Link, Press control-option-right-arrow to exit

Empty Help Center

Uh oh. That page doesn’t exist.

Disappointed

Neutral

Smiley

Thinking...

Searching through sources...

Analyzing...

Title

Track the progress of all tickets related to your company.

Tickets portal.

{assigneeName} needs more information from you