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.
Business Process Flows in Microsoft Dynamics CRM help guide users through their work while they are using CRM records. Organizations standardize processes across teams to provide consistency and visibility to process steps and stages. In this blog, we will at the new features of Business Process Flow (BPF) in CRM 2015, including branching and programmatically branching process flows.
Let's say you are working for a car insurance company. Customers or policy holders call your company to file claims or to inquire about existing claims, to update their account, etc. So, we need to build a standard business process to handle those phone calls and assist customers with their claims or inquiries. Here is the simple flow chart:
As a business user this can easily be set up using BPF. What will be needed: Entities to work with, Stages and Steps? The main Entities are going to be "Case" and "Claim" because Case is required for any call that is received and Claim is the custom Entity that stores Customer Claims data. In addition to these two Entities, we created another custom Entity called "Call Process" just to handle different type of calls. For a phone call regarding a Claim we will have the following Stages:
Pretty straight forward:
Branching Process Flows
In the insurance claim example, what happens when calls are merely for just an inquiry? The users do not need to access the claim; they only need to make sure to capture the details in the Case.
In CRM 2015, you can handle this situation by adding one or more branches in our design. In the example below, you have one field in our "Identify" stage called "Type of Call" and its values are simply "About Claim" and "About Inquiry." Depending on which one is selected by the user you would want to follow different processes. So, you can easily create one branch that will check for the selection and route to an appropriate stage in the business process flow.
Keep in mind even though you have this flexibility, you want to limit the number of branches within a single business process because it can get tough to maintain. It will clutter your design.
Programmatically Branching Process Flows
You could achieve the same behavior by writing client scripts on the form. Now, in 2015 you have additional methods added to the "Xrm.Page.data" and "Xrm.Page.ui" namespaces. Please refer to SDK for available methods. The script would look something like this:
This is just an example of what you can do using client scripts. This code will switch to the right process based on "Type of Call" value selected.
Scripts can be even more powerful when you need to pull data from another system. For example, you may need to verify some information entered, and based on that, route users to the correct stage or entirely whole new process.
Let's try to understand the methods used in the script. The object model looks something like this:
After all the required steps are completed in our "Identify" stage, users will click on "Next Stage" button to move forward. At this point you want to check for "Type of Call" and re-route the user to a different process if selected value is "About Inquiry". A few points:
That's all! This is a great new feature since it provides the user with more control over Business Process Flow. You can now more easily find out where the user is at in the process flow in real time. This opens up many possibilities.