Prior to the Wave 1 2020 release, the allocation of charges capability was available only on the Purchasing side of F&O processes. In this blog, we’ll review the Current State process and share some exciting news about Future State process.
As Microsoft has continued to develop and enhance CRM for Dynamics 365, a few of the areas that they have continuously improved through the years are processes, workflows, and dialogs. In today's blog, we will be taking a closer look at how CRM processes, workflows, and dialogs changed from 2011-2015. Get your time machine ready! We are about to throw things way back!
When Microsoft rolled out Microsoft Dynamics CRM 2011, it only came with workflows and dialogs. In CRM 2011, workflows operated in the background and were not real time. Additionally, CRM 2011 featured dialogs, which are interactive or simultaneous processes that provide the user an interface that presents step-by-step options in order to guide the user through a specific process.
A Workflow in CRM 2011
For Microsoft Dynamics CRM 2013, Microsoft expanded processes to include workflows, actions, business process flows, and dialogs. In CRM 2013, some things like dialogs were left the same, while workflows were enhanced to be able to run in the background or in real-time and could require the user to provide input in order for the workflow to operate. New additions for CRM 2013 included actions and business process flows. In CRM 2011, merging operations could only be done by writing code. CRM 2013, however, introduced actions, which can be used to create a new operation that can be used to merge multiple operations into a single operation. Actions include operations such as create, update, assign, or delete. For example, an action could be written to merge the update and assign operations. Business process flows were also introduced as a way for the user to be able to visualize a business process flow as well as guide a user through the steps of a process, like a Support Case or Lead Generation.
A Workflow in CRM 2013
A Business Process Flow in CRM 2013
A Business Process Flow within a Case in CRM 2013
For Microsoft Dynamics CRM 2015, some things stayed the same including actions and dialogs. Other items were improved including workflows. Workflows were made to start manually or automatically based on specific conditions such as if a customer sends an email that goes into a CRM queue. That email going into the queue can automatically trigger the creation of a Case. Another big improvement in CRM 2015 was that business process flows include branching logic, which allows the user to drive the business process based on how the user answers questions or fields. For example, the user has a yes/no question in the first step of the business process flow. The user answers "yes," the business process flow will take them down path A. If the user answers "no," the business process flow will lead the user down path B, which includes different questions and business process steps.
A Business Process Flow in CRM 2015
A Business Process Flow within a Case in CRM 2015 - Need to Escalate? Yes, the process flow displays Additional Information
A Business Process Flow within a Case in CRM 2015 - Need to Escalate? No, the process flow displays Complete
We hope you enjoyed our time travelling adventure today! It's fun to look back, right? Well, it's even more fun to look forward! Stay in the loop as Microsoft continues to refine and improve processes, workflows, dialogs, and so much MORE by subscribing to our daily blog and checking out the PowerObjects Dynamics 365 page.