Processes: Types of Processes in Microsoft Dynamics 365

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:

1. 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.
2. Business Process Flow - Business Process Flows allow you to create the ribbon across the top of a record that helps walk a user through a process
• 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
3. Workflows - Workflows are automated processes that fire behind the scenes
• 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)
4. Dialog - a Dialog is basically a wizard that will walk the user through a series of questions and then acts on the entered data
• Manually triggered on only one record at a time
• Relies on manual intervention
• Deprecated in v9 so don't get too attached

Business Rules are similar to processes in that they allow more complex logic to be achieved without code. These are configured within the entity or form that you want to work on. Business Rules ask for a condition and then allow actions based on that condition. The actions can be show/hiding a field, setting the value of a field, setting a field to required, etc. In 8.2 a "Recommendation" option was also added which allows you to suggest an action for a user and they can choose whether to implement or not.

Hopefully this gives you a high-level overview of the types of automation you can implement in Microsoft Dynamics 365!

May 21 Blog Review

It seemed to be a quiet week in the CRM world. Let’s jump right in!

CRM in the Field posted Customers’ choices… The most popular “Dynamics CRM in the Field” technical blog posted from Premier Field Engineering! This reviews the top posts over the last few years. These are full of great information so make sure you check them out.

Leon Tribe discussed Tools for an Awesome CRM Demo. This gives tips to make sure that your demo wows! This includes setting up a portal demo and using a workflow to make emails appear to have been sent.

Jukka Niiranen has been working through a series on customizing 2015 sales processes. This week he talks about Using CRM 2015 Calculated Fields for Opportunity Estimated Revenue. This gives a basic overview and how-to for calculated fields and also talks about some limitations to be aware of.

CRM Tip of the Day posted an interesting tip on creating Mandatory Fields in Dialogs. Although this is not technically possible you can use conditions and logic to force the user to enter a value before proceeding.

CRM Tip of the Day was also busy instructing everyone on SLAs. Check out all 3 parts – Part 1: Fields, Part 2: SLA, and Part 3: FAQ.

That’s all I have for this week!