It can be overwhelming when getting started using workflows and other processes in Dynamics 365. So let’s start by breaking down the types of processes that are available and how you might use these.
When creating a Process from the Settings -> Processes area you have 4 options:
- Action – An Action is a set of steps configured by a CRM Administrator and then called through code (such as a plugin). This allows you to have an Administrator control the business logic but the developer could determine when that logic is used
- This is something to consider when you have limited access to a developer so you can minimize your dependence on them
- For example – You could have a Plugin firing when a task is added to a queue and it calls an Action to assign it to the manager. The Plugin could determine when it needs to fire, but the Action could control how the manager was set.
- The most common example is the sales process where a salesperson is guided through the Lead to Opportunity to Account process and encouraged to enter all the appropriate data along the way
- This can span multiple entities and include conditional branching logic based on input data
- These can fire automatically or be manually triggered by a user (on demand)
- Workflows do not allow for any user interaction in the process. It will not pop up and ask the user for more information to direct the process. It can wait on a specific action to occur.
- These can fire in the background (asynchronous) or in real time (synchronous)
- Manually triggered on only one record at a time
- Relies on manual intervention
- Deprecated in v9 so don’t get too attached