Skip to main content
All CollectionsUsing Rattle
One Flow per Object Strategy
One Flow per Object Strategy

Lower the number of Flows created by Rattle on Salesforce by switching to the One Flow per Object strategy.

Nayan Kumar avatar
Written by Nayan Kumar
Updated over 7 months ago

With the One Flow per Object strategy, Rattle will utilize only a single Flow per object on Salesforce (instead of one Flow per Rattle workflow). This will help you reduce the number of Flows that Rattle creates on Salesforce by 60-70%.

Currently, this strategy will only convert the following workflow types into a single Flow per object:

  1. Create/update (under General Workflows)

  2. Deal Room workflows
    ​

How can it be used?

  1. This option will be visible only to Super Admins. If you are a Super Admin and don't see the option below, please contact your CSM.

  2. Navigate to Team > Advanced and click on 'Configure' under the SFDC Flow Creation Strategy setting. You will notice a list of Objects on which workflows have been created. Choose the object(s) for which you want to enable this strategy.

  3. After changing the setting (and confirming), Rattle will begin an asynchronous migration process. Admins will not be able to modify this setting until the migration process is complete.

  4. Once completed, the status of the migration process will be communicated to the Super Admin as a Rattle alert.

Notes/pointers:

  1. For a given object, only one strategy between ‘One Flow’ and ‘Multiple Flows’ strategy can be chosen and not both.

  2. Create/Update/Delete/Inactivating workflows will not be possible when migration is in progress.

  3. For workflow types that are not supported, they will continue to function as expected, just that separate Flows (for each workflow) would be created for those workflows.

  4. Limit of ‘Maximum CPU time on Salesforce servers’ (10,000 milliseconds) exists. Admin will likely receive alerts from SFDC when the number of workflows in a single Flow exceeds 100.

  5. Migration will fail in the following cases:

    1. If the SFDC fields referenced in any active workflow are deleted/deactivated.

    2. If any of the conditions are unsupported by the ‘Formula’ resource on Flows.

    3. While creating/updating workflows where conditions are unsupported in Flows (but were previously supported in workflow rules). E.g. If the formula field limit of 4K hits (conditions are too long), users might not be able to create/update workflows.

Did this answer your question?