With the introduction of MS CRM 2015, came many new features. The one we are going to discuss here is advancement of Business Process Flow and especially the Scripting part, which came as boon.
Before CRM 2015, the Business Process Flow exist, but no API availability made it impossible for the developers to interact with the BPF via programming.
CRM 2015 gave it a new look, while creating a Business Process Flow, we have the option of creating Branched stages, which in simple terms is we can conditionally decide which stage to be shown after the current stage. The branching decisions can be made on the basis of the value of any step used for the current stage.
Previously we were not allowed to visit an entity more than once before, now we can visit an entity more than once.
Above are the few highlights of features added for BPF, let
s delve into the Programmability enhancement.
The most important part is, How to hook to the Stage change or Stage Select events of BPF? This is indeed the simplest part.
If you want to hook to the Stage change event, you can do this by writing the below code. And, you have the freedom to place this code either onLoad or onSave of the form or else on change of any field.
//Register a function on change of the stage
stageChange - It is the function to be called when the stage is changed.
Similarly, you can hook onto the Stage select event.
//Register a function on select of a stage
stageSelected - It is the function to be called when the stage is selected.
We have the options to unhook the events as well.
//Unbind a function on change of the stage
//Unbind a function on select of a stage
By hooking onto either stage change or stage select events, we have plethora of options to use.
Like we mentioned above, that we can Branch the entities conditionally. We can leverage this functionality by showing different fields for an entity depending on the value selected for the step on the previous stage.
Let us explain you few of the available methods in this part of the Blog, and the rest in this.
- Collapse or Expand the Business Process Flow:
We have the option to collapse the Business Process Flow by default, on load of the form.
string: "expanded" or "collapsed" are the two variables that can be passed.
- Show/Hide the Business Process Flow:
We can show or hide the business flow. It can be useful when we dont need few of the Security Roles to see the BPF.
bool: “true” to show and “false” to hide.
- Active Process:
We can get the Current Active Process and we can set the Current Active Process. This is useful if you want different security profiles to see different processes.
This will give you the object of the current Active Process. Object will have,
Process Name, Process Id(GUID), Render State(Visible/Hidden) & Collection of Stage Objects.
var procObj = Xrm.Page.data.process.getActiveProcess();
This will allow you to set the Active Process.
procGUID: Id of the process to be set.
callbackFunction: Function that will be called in order we have any necessary actions to be performed on setting the process.
- Active Stage:
We can get the Current Active Stage and we can also set the Current Active Stage. This is useful if you want a user to move back to previous stage, when he selects “x” value for a step on current Active stage.
This will give you the object of current Active Stage. Object will have, Stage Name, Stage ID(GUID), Base Entity, Stage Status(active/inactive) & Collection of Step objects.
var actStg = Xrm.Page.data.process.getActiveStage();
This will allow you to set an Active Stage.
Note: Only completed stage for the current entity can be set using this method.
stgGUID: ID of the stage to be set.
callbackFunction: If in case any actions are to be performed after setting the Active Stage.