Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  • This Flow would be in a larger flow of your “Always Flow”. Just about every object is going to have an Always Flow…

  • But if you only want it to run if the record is Active, then we are now released from the stupid shackles of One Process Builder per Object and can now build our Flows in a more granular approach as we would do with Workflows. So I would build flows like this”this:

    • MyObject-BeforeCreateUpdate-Always

    • MyObject-BeforeCreateUpdate-IsActive

  • See my Formulas in Flow Triggers post for more details.

  • Remember that there is STILL no guarantee of order of flows, so if you need an order it needs to be in the same Flow.

  • At first glance it seems that comparing the {!$Record.MyRate__c} with {!$Record__Prior.MyRate__c} rather than a simple Is Changed is a bit of extra work, but I think the payoff is in the ease of setting up different conditions and opposite conditions if there is only one, like the example.

  • And the Assignments are easy to set up also.