Title 1

LABEL

Fill in some text

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

LABEL

Fill in some text

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

LABEL

Fill in some text

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

Title 1

LABEL

Fill in some text

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

Title 1

LABEL

Fill in some text

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

Title 1

LABEL

Fill in some text

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

Title 1

LABEL

Fill in some text

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

Title 1

LABEL

Fill in some text

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

Title 1

LABEL

Fill in some text

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

LABEL

Fill in some text

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

LABEL

Fill in some text

Thank You

Salesforce Inspector

Fill in some text