Title 1

LABEL Learn more at stories.salesforcecodex.com

Title 1

LABEL Learn more at stories.salesforcecodex.com Fill in some text

Title 1

LABEL Learn more at stories.salesforcecodex.com Fill in some text

Title 1

LABEL Learn more at stories.salesforcecodex.com Fill in some text

Title 1

LABEL Learn more at stories.salesforcecodex.com Fill in some text

Title 1

LABEL Learn more at stories.salesforcecodex.com Fill in some text

Title 1

LABEL Learn more at stories.salesforcecodex.com Fill in some text

Title 1

LABEL Learn more at stories.salesforcecodex.com Fill in some text

Title 1

LABEL Learn more at stories.salesforcecodex.com Fill in some text

Title 1

LABEL Learn more at stories.salesforcecodex.com Fill in some text

Title 1

LABEL Learn more at stories.salesforcecodex.com Fill in some text

Title 1

LABEL Check out post for more detail. Fill in some text Salesforce Inspector Fill in some text Learn more at stories.salesforcecodex.com

Title 1

Top 10 Best Practice for Lightning Flow

salesforcecodex.com

Title 1

1.Naming Guidelines

salesforcecodex.com

We should use proper name of flow and its element. As now we have unlocked package as well so we should name our flow based on module being developed so that it can be used easily in module package.

Title 1

2. Flow and Sub-flow

salesforcecodex.com

Lightning Flow is now more powerful then process builder, workflow and trigger. To manage flow we can create one main flow and based on decision elements we can call other sub flows.

Title 1

3. Multiple trigger Flow

salesforcecodex.com

create two trigger flow for each object, one for before save operation and one for after save operation.

Title 1

4. Bulkification

salesforcecodex.com

we should always use bulkification wherever we can apply that otherwise we will get SOQL limit exception error

Title 1

5. Error Logging

salesforcecodex.com

We should log error for each failure. Try to log each error in custom object using Platform Event.

Title 1

6. Null handling and Branching

salesforcecodex.com

While retrieving records using Get Records operation, if data not found then return null and use decision element on that variable

Title 1

7. Test Flow with business user

salesforcecodex.com

If you are not getting proper result while testing flow then try to debug flow with user who will use it.

Title 1

8. Test Performance of flow

salesforcecodex.com

Always get flow tested for multiple users simultaneously, specially if flow is working for multiple records at a time.

Title 1

9. Never hardcode variables

salesforcecodex.com

Always pass data at runtime to flow. Don’t hardcode in flow variable like if we need to pass current record id then pass it from other flow or from app builder page.

Title 1

10. Create document's Flow

salesforcecodex.com

Document each flow use case to maintain it properly. As number of flows will increase so it will be difficult to know which flow will do what.

Title 1

salesforcecodex.com

Thank You