-1

I'm looking to consolidate some of our flows so we don't have 10 different account fast field update flows, but just one per object. This is mainly to make it easier to maintain between a group of admins.

Ideally, I would have one flow with the first decision determining the trigger context - e.g. a record is created or updated, a record is created etc...

enter image description here

I'm not sure how to accomplish this in a decision node. E.G. if I start with isnew decision, then how would I also have the decision if it's new or updated? Any advice would be appreciated.

6
  • Salesforce used to recommend a single flow per object, but now recommend multiple flows with targeted (and clear) single roles and responsibilities. You can control order of flow executions, handy if there are dependencies.
    – Phil W
    May 25 at 15:42
  • Phil, can you provide some references? Genuinely curious as I'm looking for best practices on managing a lot of flows.
    – jameskbw
    May 25 at 15:51
  • 1
    The order of execution was added in Spring 22. It was covered briefly on medium.com and is touched on in this admin blog (though this predates ordering).
    – Phil W
    May 25 at 16:11
  • (That admin blog was refreshed Spring 23, so the text can be read in context of having order of execution control, I guess)
    – Phil W
    May 25 at 16:12
  • Thanks, I still see value in trying to consolidate flows by object and trigger. I don't see how the trigger explorer prevent an admin team from using the same criteria in multiple flows which seems inefficient.
    – jameskbw
    May 25 at 17:47

1 Answer 1

0

You can create a formula varaible for ISNEW(). Use that variable in decision critierion and combine that with an ISCHANGED() criterion in custom logic.

Example:

  1. MyField__c is not null
  2. IsNew variable is true
  3. MyField__c IsChanged = true

1 AND (2 OR 3)

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .