Business Process Flows are a fantastic way to guide users through the various steps required in a process such as closing a deal, qualifying a lead, or working on a case. Sometimes, however, the process that needs to be followed itself must change. In this blog, we will cover how you can now build a workflow that will allow you to switch between Business Process Flows automatically so that users don’t have to make the switch manually in Microsoft Dynamics CRM 2016.
Think of Business Process Flows like a railroad. Once you are on them, they get you where you need to go quickly and efficiently. They even support branching and conditional logic so that within one flow, an agent can go down several paths.
There may be situations in which the applicable Business Process Flow must automatically change. This can be done by using the SetProcess action in a workflow.
Here’s what you need:
1. More than one Business Process Flow.
2. A Workflow with a triggering condition.
That’s it. All the best practices for creating a Workflow apply. In the screenshot below:
Number 1 indicates that we are watching for a specific field change.
Number 2 indicates what field we are watching for specifically.
Number 3 is the SetProcess action.
Let’s take a look at the steps inside the SetProcess action. There are two fields to fill out for every process, the NewProcess (Number 1 above) and the Target (Number 2). Note that SetProcess is not limited to one entity – one could set the trigger on an Opportunity and have it change the process to a related Account if so desired.
To finish, save and close, activate the Workflow, and voila! Users can now switch between Business Process Flows silently and seamlessly. Check out The CRM Book for the best practices around managing processes, and until next time. Happy CRM’ing!