Page Comparison

...

• Adding Filenize actions to your flow does not make it final. At the end of the flow, you need to run the Filenize commit action. This is to build a queueable chain of actions. Ensuring that the next action only runs if the previous has finished. This needs to be done explicitly due to the asynchronous design of the actions.

  • The chain also skips all consecutive actions if an error has been found. To prevent certain scenarios, i.e. where a subfolder needs to be created if the parent folder does not exist due to an error

• TODO: All actions in the flow are executed First In First Out. But when using the Diagnose Flow utility that comes with Filenize, there might be some differences.

  • When running a flow for one specific record, you just see the actions related to the record in the UI. Pending actions in the past

  • When running a flow where multiple records are in one DML call, each action is executed n times per record before continuing to the next action

    • This is standard Salesforce flow and bulkily behavior

    • We stop all consecutive actions after an error occurred which are linked to the same record. The other actions continue

  • When running a flow where multiple records are saved, but each in their DML call, all the actions are

Pro

• Easy to setup for admins and developers

• Includes in-depth diagnose tooling for spotting incorrect behavior

  • Also includes rerunning certain actions for trial-and-error testing

• Provides out-of-the-box user feedback about its progress in the Filenize component

...