Home > CRM Development > Callouts Vs Workflows?

Callouts Vs Workflows?

Following guidelines can help you decide when to use a callout versus a workflow assembly:

Use callouts

  •  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.

Use workflow

  • 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.

  1. Amol Gholap
    June 30, 2007 at 2:39 pm

    Hi Ayaz,

    hope you are doing well.

    can you tell me what is the difference between organization-owned & user owned entity.

    Amol Gholap

  2. July 2, 2007 at 5:52 pm

    Organization-owned entities typically contain data involving something that belongs to the organization such as products. Organization-owned entities do not support the operation Assign.

    User-owned entities are associated with a user. User-owned entities typically contain data that relates to customers, such as accounts. The user is the primary owner of the relationship between these customers and the organization.

  3. July 7, 2007 at 10:03 am

    Got it thanks.

    Amol G

  4. October 5, 2011 at 3:19 pm

    Usually I do not read article on blogs, but I would like to say that this write-up very forced me to try and do so! Your writing style has been amazed me. Thanks, quite nice article.

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: