2 thoughts on “Tip #523: Tipster guide to invoking custom actions without code”

1. ElliottH says:

   November 20, 2015 at 4:19 pm

   Great explanation of actions, thanks!
   But why would I do this over just using the check conditions in a workflow? Can you give a more complicated example where workflows alone wouldn’t work and Actions would be needed?

   Reply
   • George Doubinski says:

     November 21, 2015 at 12:36 am

     Hi Elliott,

     there is only so much we can do in the video and scenario is, indeed, a simplified one. I think we all agree that using child labor is the way to engineer your workflows. Calling custom actions instead of the child workflows has the following benefits:

     • Workflows have only one “parameter” – record they run against, while custom actions, in addition to that, can have multiple input and output parameters. Or none at all – your choice.
     • Actions are exposed via CRM API and can be called from external code, e.g. javascript on the client, C# on the server, etc.
     • Actions can have plugins allowing change in behavior without rewiring or disabling anything.
     • There must be something else but it’s eluding me right now.

     Hope it explains it better.

     Reply