Callouts Vs Workflows?
Following guidelines can help you decide when to use a callout versus a workflow assembly:
- To alter data prior to submission to the platform.
- To take action after an update to an entity. (Workflow does not provide an easy trigger mechanism for the update event.).
- When you need a synchronous transaction and an immediate response.
- To take action before or after the merging of two records or the deletion of a record.
- When accessing custom entities that are organization-owned. Workflow can be used only on entities that have user ownership.
- For all asynchronous actions—transactions that can be completed without having the user wait for their completion. A typical asynchronous action might be to send an e-mail message after some condition is met. The user usually wouldn’t have to wait until the system created and sent the message.
- For simple common tasks. The Workflow Manager has a list of actions, already built and available for use, that requires no custom application development. Available actions include creating new records (such as Activities or Notes), sending e-mail messages, and updating values on related entities.
- To allow more configuration options to the user who is creating the workflow logic. Because the user builds the workflow rule with the rule editor, he or she can also alter it without necessarily requiring programmatic interaction.
- When you need a user to manually execute the necessary logic.