...
TODO: Topics to work out
One queueable per actionThe impact of queueables on sandboxes
Pro
Easy to setup for admins
Includes in depth diagnose tooling for spotting errors
Provides out-of-the-box user feedback about it’s progress in the Filenize component
Con
By design each Filenize action is a Queueable, this is slower than running the api’s directly in Apex. This is to prevent hitting DML/Callout limitations.
Queueables are slower on sandboxes than on production orgs. This is Salesforce’s way to limit resources.
Since each action initiates an asynchronous process. The result of that process is not usable in the next consecutive process. For folder creation actions we do provide a direct output. As the new relative url is already known prior to the execution.