For this recipe, we will focus on a different entity. Let's have a look at Opportunity. The Opportunity is the result of a qualified lead in many cases, but Dynamics CRM allows you to also add opportunities directly.
With opportunities, one of the fields we will focus on is the pipeline phase. For specific scenarios, a pipeline phase is tracked, customized, and enforced. Business rules can define the stages that define each pipeline phase, and specific rules that have to be met for an opportunity to progress to the next pipeline phase.
We can start by either reusing one of the previously created solutions or creating a new one. If you do not have a solution created, start by creating one.
We assume the following business rules
- An Opportunity begins at 10 percent
- An Opportunity progresses to 25 percent if the Rating field is set to Hot
- An Opportunity progresses to 50 percent if a currency and price list are defined
- An Opportunity progresses to 75 percent if a freight amount is defined
We will achieve this by using a combination of scripting and workflows. So let's get to it.
- Open your solution and add the Opportunity entity if not already added.
- Go to processes and add a new process. Configure it as described in the following screenshot:
- Once you click on OK, the process information window opens up. Set the following items on this window:
- Set the Scope to Organization
- Set the Start when to Record is created
- Add an Update Record step
- In the Update make sure Opportunity is selected
- Click on Set Properties
- In the new form that opens find the Pipeline Phase field, and type in 10%, as shown in the following screenshot:
- Click on Save and Close.
- Your form now should look similar to the following screenshot:
- Click on Save and then Activate to activate your process.
- Click on Close.
- Now your processes window will show you the newly added process along with other processes previously added. Make sure that the Status shows Activated.
- Once we have this process, let's open a new Opportunity, fill in the required fields, and click on Save and Close. Give it a moment for the workflow to execute.
- Reopening the opportunity you just created should show you the customized 10% value added in the footer of the page, as seen in the following screenshot:
- Add a new workflow that updates the pipeline phase to 25 percent. Configure it to kick off when the rating field changes value. We check if the rating value is Hot, and then we update the pipeline phase to 25 percent.
- Now we have to check if the
CurrencyandPrice Listare defined. We will perform this check in JScript, and update a temporary field with atrue/falsevalue. Add a two-options field to the form, namednew_progressto50. - Insert the following script in a JScript resource, and associate it to the
OnChangeevent of both the Currency (transactioncurrencyid) and Price List (pricelevelid) fields:function HasCurrencyAndPriceList() { var _currency = false; var _priceList = false; var currency = new Array(); currency = Xrm.Page.getAttribute("transactioncurrencyid").getValue(); if(currency != null) { _currency = true; } var priceList = new Array(); priceList = Xrm.Page.getAttribute("").getValue(); if(priceList != null) { _priceList = true; } if(_currency == true && _priceList == true) { // set temp field to true Xrm.Page.getAttribute("new_progressto50").setValue(true); } } - Create a new workflow similar to the previous one, that starts when the Progress to 50% field is changed, checks the field value, and if set to
True, updates the pipeline phase to 50%. - Finally, add a new workflow that starts when the Freight Amount field is changed, checks if the pipeline phase is at 50% and if the amount contains a value greater or equal to 0.00, and updates the pipeline phase to 75%.
- Save and Publish your solution.
- Test your solution by filling in progressively the required fields and follow how the pipeline phase updates automatically.
The solution presented here enforces business rules through the use of workflows, and shows an example where working with JScript in conjunction with workflows can achieve the expected result.
For the sake of simplicity, I have demonstrated the creation of four different workflows, one for each phase progression. In real life, you would build all these rules in a single workflow. Additionally, you would probably build a reversed process that would downgrade the pipeline phase if a system value is changed to a value that does not allow the opportunity to pass a lower threshold.