Naming Conventions and Best Practices in Salesforce Development

-

Classes-                                   UpperCamel Case

Methods and variables -         lowerCamelCase

Constants-                               CONSTANT CASE

HTML-                                       lower_snake_case

When in doubt, be consistent


Triggers

1) Begin with a logic to allow bypassing(Can use a Class/Custom Setting) of the trigger when necessary.

2) Use trigger helper and handler patterns.

3) Keep as much logic as possible out of the trigger and trigger handler.

4) Limit logic used in trigger helper as much as possible; break functionality down into smaller classes to keep helper manageable as this class will be used by the entire wing.



Async Apex

1) Run all asynchronous apex under the user the Admin User.

Future

1) Avoid using future in triggers - salesforce does not allow asynchronous calls to be made while a synchronous process is running.

Batch

1) Keep logic out of batch class as much as possible.

2) Increased governor limits help with more complex operations.

3) Helps avoid mixed DML operations.

Schedule

1) Similar use cases to batch, but used when a job needs to be run regularly.


Unit tests

1) Test class names should always end in "_Test".

    Ex: Sample Class will have a test class named SampleClass_Test.

2) Use a @TestSetup method to set up any test data - best practice and speeds up runtime significantly.

3) Use Test.startTest() and Test.stop Test() to make sure all asynchronous apex finishes before asserts.

4) Use asserts to validate code behavior.

5) Test each public method - positive and negative cases.

6) Aim for 90% test coverage.

7) Should pass in regardless of what environment it is in with the same code coverage amount.

8) Should be able to be run at any time.


Profile considerations when adding a new field or other item requiring permissions

1) When adding a new required field, do not include any permissions as they are meant to be visible to all users

2) Admin - Read/Edit.

• Set to Read Only if the field is an Auto Number, Summary, or Formula.

3) Analytics Cloud Integration User - Read Only.

4) Read Only Admin - Read Only.

5) All other profiles that do not need access should be added with Read and Edit set to false.

Comments

Post a Comment

Popular posts from this blog

What are Duplicate Rules and Matching Rules? How to Invoke Duplicate and Matching Rules in Salesforce without performing DML operations?

-
Image
  Definition: 1.        Duplicate rules are configurations that define the conditions under which a record is considered a duplicate. These rules are applied to standard and custom objects in Salesforce. 2.        Matching rules determine how Salesforce identifies duplicate records when new records are created or existing records are updated. They define which fields to compare and the criteria for matching. 3.        Duplicate rules use matching criteria to determine if a new or updated record matches existing records in the Salesforce organization. Matching criteria can include exact matching or more flexible fuzzy matching based on specific fields. Please note that we can only invoke these while performing DML operations like Insert or Update . Duplicate Rule: It’s Corresponding Matching Rule: The Standard Contact Matching Rule criteria:   Blocking or Alerting: Duplicate rul...
Read more

Apex Best Practices

-
Image
Apex Best Practices: 1. All constants should have uppercase names, with logical sections of the name separated by  underscores. 2. Always check the returned values from Database.delete(), Database.emptyRecycleBin(),                    Database.insert(), Database.undelete(), Database.update() and Database.upsert() calls. If a list is passed to any of these methods, the call will return an array[] of results; the apex code must check all the return values in the returned array of results.  3. Classes that contain methods or variables defined with the webService keyword must be declared as global. 4. Declare instance variable as private or protected. 5. Declare only one variable per line of code. 6. Define meaningful numbers using clearly named constants (static final). 7. Do not instantiate any object before you actually need them. Specifically outside a try-catch block. 8. Each method name should have meaningful names start...
Read more

LWC Best Practices

-
1. Use the Lightning Data Service or cache data whenever possible 2. Before making a call to the server, make sure there's no other option to obtain the data 3. Consider passing data between components using attributes, events, or methods rather than retrieving the same data in different components 4. If multiple components on a given page retrieve the same data, consider creating a service component that has no UI elements and can query data once so that it can pass data on to other components. 5. Only SELECT the fields you need. 6. Set a LIMIT on the query, don't return huge numbers of rows at once 7. Implement pagination when queries may have large result sets. 8. Don't preload data that the user may never need 9. Put the least accessed components in a secondary tab that the user may not click. 10. Don't make a call to the server to filter or sort data you already have at the client side. JavaScript Arrays have built-in functions to do things like sort, filter, and f...
Read more