Ok, so this feature took me a little while to get my head around. I felt there was a fair gap between the conceptual description of the feature from Microsoft and the reality of how and when you would use it. Hopefully this post speeds up the learning process for others.
The common scenario for this I think will be for Approval processes. Imagine we want an Approve button added to the CRM form and when that button is clicked we want stuff to happen.
Here’s the steps (in completely the wrong order):
Thirdly, configure your Action. Here, you use the same GUI that you have used in the past for Workflows and Dialogs:
You define your Input and Output arguments:
And then you write your business logic using the normal Conditions and Actions you will be used to from your Workflow configuration days:
You can do some Check Conditions to perform different actions based on the input arguments:
You can create, update and assign records and send emails, etc. And you can assign values to those Output arguments:
Going back to the Approval scenario I could see the following working nicely:
- – The user changes an Approval field to Approved
- – The Approval Action runs those Input arguments through a series of Conditions assigning values to an Approver field and a Approval Due Date field
- – The user has immediate visibility of who has been assigned as Approver and is happy
I hope this helps others understand Actions a little better. I do wonder what they have to offer over a real time workflow. I think the choice between the 2 will take some careful consideration. More learning required 🙂