CRM 2016 - When to use an Action process vs a Workflow

(4) Share

Report

Posted on by awalters

3,079

I'm experimenting with Actions and Workflows for some processes we need to run in CRM. And I have to admit, I'm having a tricky time figuring out when to use an Action - I haven't yet seen what they can do that a Workflow can't. Does anyone have any examples of what an Action can do that can't be done elsewhere, and/or any other circumstances where one would specifically want to use Actions instead of Workflows?

One page that I saw had an example of Creating a Contact from an Account, but that seems to be fully able to be done in a Workflow as well. I wonder if there used to be more of a difference, say in 2013, before features were added more recently?

Thanks!

*This post is locked for comments

I have the same question (0)

All responses (12)

Answers (1)

IslamAbdelhakiim 5 on at

Like (0)

Report

RE: CRM 2016 - When to use an Action process vs a Workflow

if I got you, you would have the same action implemented in both workflows, which means you would have 2 emails sent and 2 new tasks created...

Was this reply helpful? Yes No
gdas 50,091 Moderator on at

Like (0)

Report

RE: CRM 2016 - When to use an Action process vs a Workflow

Please check my video-

m.youtube.com/watch

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

RE: CRM 2016 - When to use an Action process vs a Workflow

Hi

I too had a similar confusion and we used actions to reduce the amount of duplicate and similar code to be used across many entities

In my case we had to do Cloning functionality and many custom entities need to have this feature at that time we wrote a generic cloning action code and on each entity which required cloning put up a button and called this Cloning action

in that way we used

Was this reply helpful? Yes No
PriyaP 15 on at

Like (0)

Report

RE: CRM 2016 - When to use an Action process vs a Workflow

You can say you don't need to write code for the logic you have set in action. For example, you want to update case on the condition you want and not on any record creation or updation, then you simply go and create action which will update case. Now go to your code(plugin,java script), and instead of writing logic to update case, YOU CALL YOUR ACTION.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

RE: CRM 2016 - When to use an Action process vs a Workflow

Hi Sonali,

Refer this: msdn.microsoft.com/.../dn481600.aspx

Was this reply helpful? Yes No
Priya1 30 on at

Like (0)

Report

RE: CRM 2016 - When to use an Action process vs a Workflow

Is there any difference between action and custom action?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

RE: CRM 2016 - When to use an Action process vs a Workflow

from my view, most of the business logic can be written in action and can be called from Plugin or workflow or from java script

so that in future if business logic has to be changed , we can do changes directly from action and it will get reflected in all the other triggering processes

Was this reply helpful? Yes No
awalters 3,079 on at

Like (0)

Report

RE: CRM 2016 - When to use an Action process vs a Workflow

Ah - that makes perfect sense. Thank you!!

Was this reply helpful? Yes No
Verified answer

Guido Preite 54,084 Moderator on at

Like (8)

Report

RE: CRM 2016 - When to use an Action process vs a Workflow

a workflow requires always a record as starting point (created, updated, deleted or on-demand), an action no.

Let's say you create an action that create an email to the manager, the action is not binded to a crm record, can be included or not inside a workflow, can be called by c# code, can be edited by the crm built-in editor. It's a piece of server side code with a designer.

Was this reply helpful? Yes No
Jason M. Cosman 5,234 Moderator on at

Like (0)

Report

RE: CRM 2016 - When to use an Action process vs a Workflow

Well there are differences in terms of the custom actions that can take parameters in like entities or entity collections etc... This is where I see some of this main stream value for the Actions.

Your correct that actions can be called from Workflows and that makes sense but actions cant be triggered like on an account creation like a normal workflow would be able to.

Was this reply helpful? Yes No