Intentional

Documenting code through comments can quickly help others understand the functionality of different classes and methods.

Using field descriptions helps keeping your application well documented and easy to maintain.

Naming conventions help drive consistency across the application, which makes source code easier to read and understand.

Using the latest (or a sufficiently recent) version of the Salesforce API is generally a best practice to leverage the most recent features and reduce the risk of bugs.

Naming conventions help drive consistency across the application, which makes source code easier to read and understand.

Assertions let you test the behaviour of your application, increasing your confidence that your logic works as expected. Adding precise assertions to your tests is one of the most effective ways to detect and correct bugs. Using comments to describe the rationale of each assertion has the added benefit of documenting the inner working of the application logic, enhancing maintainability.

Naming conventions help drive consistency across the application, which makes source code easier to read and understand.

Naming conventions help drive consistency across the application, which makes source code easier to read and understand.

Using descriptions helps keep your application well-documented and easy to maintain.

Using descriptions helps keep your Flows well documented and easy to maintain.

Naming conventions help drive consistency across the application, which makes source code easier to read and understand.

Removing unnecessary code makes your app cleaner, more efficient and easier to understand.

Naming conventions help drive consistency across the application, which makes source code easier to read and understand.

Naming conventions help drive consistency across the application, which makes source code easier to read and understand.

Naming conventions help drive consistency across the application, which makes source code easier to read and understand.

Malicious code injected through inline JavaScript can exploit vulnerabilities, allowing injection attacks like cross-site scripting (XSS), which can lead to site defacement, unauthorized access, and data theft.

Most core Visualforce components function normally within Salesforce1. Unfortunately, that doesn't mean they're optimised for mobile, or that every feature works with Salesforce1.

Naming conventions help drive consistency across the application, which makes source code easier to read and understand.

As a best practice, teams should remove any logic that is no longer required to keep the application cleaner, more efficient and easier to understand and maintain.

Named credentials make callouts much easier to maintain. For example, if an endpoint URL changes, named credentials allow updating it without any code changes. Furthermore, named credentials don’t need remote site settings, otherwise required for callouts to external sites via Apex.

Nesting many conditional statements makes code generally harder to read, test and more prone to bugs.

When using CSS style tags and attributes, the HTML parser switches to CDATA or raw text context, which is prone to code injection. For this reason, using inline CSS is considered unsafe and should be avoided.

As a best practice, teams should remove any logic that is no longer required to keep the application cleaner, more efficient and easier to understand and maintain.

In API version 59.0 and later, the getSalesforceBaseUrl() method is deprecated and versioned out.

As a best practice, teams should remove any logic that is no longer required to keep the application cleaner, more efficient and easier to understand and maintain.

As a best practice, teams should remove any logic that is no longer required to keep the application cleaner, more efficient and easier to understand and maintain.

Versions 21.0 through 30.0 of the Salesforce Platform SOAP, REST, and Bulk APIs will be deprecated and no longer supported in the Summer '23 release. Applications should be modified to consume the latest available API version.

The enableExperienceFriendlyUrls field on the SiteSettings metadata type has been deprecated.

Streaming API versions 23.0 through 36.0 are scheduled for retirement in Winter '25.

On January 31, 2025, Salesforce is retiring Salesforce Functions, also known as Salesforce Elastic Services.

The “AccountInsightsSettings” and “OpportunityInsightsSettings” metadata types have been deprecated as of API version 59.0.

With Spring '24 regardless of API version, Salesforce will enforce all REST response headers defined in Apex via the RestResponse.addHeader(name, value) method to have valid names in accordance with RFC 7230.

Naming conventions help drive consistency across the application, which makes source code easier to read and understand.

To improve org security, an updated enforced with Summer '23 update prevents flows from accessing the $Api.Session_ID variable.