Workflow Best Practices

Oomnitza's workflow engine is a powerful tool that offers the ability to create robust automations to modify assets and users, alert users of changes, and even push changes to external systems. However, to quote Spider-Man, "With great power comes great responsibility." It's important to take considerations while making 

Create your begin blocks carefully

Whether you're notifying users of certain changes or modifying large swaths of assets, it's important to make sure that you're only targeting the assets that you intend to change, or the users you intend to notify.

Preventing unwanted actions starts with the begin block.

Target only the Objects you want to change. 

Workflows are often meant to make sweeping changes across a wide set of assets based off of the criteria established in the begin block. Because the assets being changed are based on the parameters specified at the time of the change, it can be difficult to identify objects that were changed unintentionally if those parameters are incorrect. Carefully review the Rule Criteria of your begin blocks before launching them to avod these situations. 

Target the fewest possible number of Objects

Going hand-in-hand with the above step, it's important to make sure you're targeting the fewest number of objects to achieve the changes or updates you want.

Because workflows may affect large numbers of assets, they can take time to run. Limiting changes to just objects where an actual change will be made helps limit the number of objects affected, and improves workflow performance.

Have more questions? Submit a request


Please sign in to leave a comment.
Powered by Zendesk