{"id":2652,"date":"2016-04-18T18:23:19","date_gmt":"2016-04-18T12:53:19","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=2652"},"modified":"2016-04-18T18:23:19","modified_gmt":"2016-04-18T12:53:19","slug":"trigger-business-rules-on-change-of-stages-of-business-process-flow","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2016\/04\/trigger-business-rules-on-change-of-stages-of-business-process-flow\/","title":{"rendered":"Trigger Business Rules on change of Stages of Business Process Flow"},"content":{"rendered":"

Introduction:<\/b><\/p>\n

Among many advanced features introduced in Microsoft Dynamics CRM 2016, one would be business rules getting invoked by a business process flow. Earlier with MSCRM 2013, business rules were introduced to provide custom business logic and eliminate the need of writing scripts around this logic. But now with Dynamics CRM 2016, some of the UI based logic whose behaviour depends on Business Process Flow and its stages can be handled easily.<\/p>\n

In this blog we will take a look at how the business rules get invoked.<\/p>\n

Example:<\/b><\/p>\n

Consider a scenario, where the management at a health care unit uses CRM to provide medical services to patients. As per the policy, 50% discount is given to the patients whose age is either equal to or greater than 60 years after they have received treatment. In order to keep a track of their patients, the management at the health care unit adhere to a business process flow. Depending on the age of the patient, the stages of the Business Process Flow can be changed. Now, based on the various stages, if we want to show \/ hide the discount field, which is by default disabled (hidden)<\/b> on the Patient form then follow the business process flow as shown in the screenshots below.<\/p>\n

\"Trigger<\/a><\/p>\n

Now we will use this Business Process Flow and its stage as a condition set in Business Rules. When the stage \u2018Is A Senior Citizen\u2019<\/b> is selected or active the hidden field i.e. \u2018Senior Citizen Discount %\u2019<\/b> field can be displayed using Business Rules as follows.<\/p>\n

\"Trigger<\/a><\/p>\n

As you can see we have selected Business Process in the \u2018Field\u2019<\/b> section of the Condition, and have selected the second option i.e. \u2018Value With Stage\u2019<\/b> among the two options provided in the \u2018Type\u2019<\/b> field. Once \u2018Value With Stage\u2019<\/b> is selected another line is added to filter out our condition depending on the Stage of the Business Process Flow. So, we get the values as shown in the screenshot below.<\/p>\n

\"Trigger<\/a><\/p>\n

The CRM provides you with two options \u2018Active Stage\u2019<\/b> and \u2018Selected Stage\u2019<\/b> with which we can define whether we want actions to be performed when the stage is either selected or when the stage is active.<\/p>\n

Note: –<\/b> If a Business Process Flow isn\u2019t present regarding an entity then, while creating a Business Rule you would<\/p>\n

Find the Value field to be locked because you won\u2019t have any process to access, as shown below<\/p>\n

\"Trigger<\/a><\/p>\n

\"image\"<\/a><\/p>\n

As per our Business Rule shown above, the field \u2018Senior Citizen Discount %\u2019<\/b> is made visible on the \u2018Patient\u2019<\/b> form which is by default hidden, when we select the stage \u2018Is A Senior Citizen\u2019.<\/b><\/p>\n

Note: –<\/b> There is major difference between \u2018Selected Stage\u2019<\/b> and \u2018Active Stage\u2019<\/b> that one needs to understand.<\/p>\n

– \u2018Selected Stage<\/b> is when you select any stage of the Business Process Flow manually irrespective of it being active or inactive.<\/p>\n

\"Selected<\/a><\/p>\n

– \u2018Active Stage\u2019<\/b> is when the process is currently residing in a particular stage as per its flow that has been pre-defined or preset.<\/p>\n

\"Active<\/a><\/p>\n

Our \u2018Business Rule\u2019<\/b> will work in the following manner, as shown in the image below.<\/p>\n

\"Business<\/a><\/p>\n

As you can see in the above image \u2018Senior Citizen Discount %\u2019<\/b> field is not visible. But as soon as we select the \u2018Is A Senior Citizen\u2019<\/b> stage of the Business Process Flow the \u2018Senior Citizen Discount %\u2019<\/b> field becomes visible, as shown in the image below with red boxes.<\/p>\n

\"Business<\/a><\/p>\n

Then we can enter some information to the field, as shown below<\/p>\n

\"Business<\/a><\/p>\n

Conclusion:<\/b><\/p>\n

It is therefore evident from the screenshots as above that scripts need not be written for performing UI based actions on the form in Dynamics CRM 2016. Instead, rules can be used for the business process flows to streamline the experience and lead the user towards the desired outcome.<\/p>\n

You may like to revisit our last quarter most popular Blogs<\/a> about Dynamics CRM.<\/p>\n","protected":false},"excerpt":{"rendered":"

Introduction: Among many advanced features introduced in Microsoft Dynamics CRM 2016, one would be business rules getting invoked by a business process flow. Earlier with MSCRM 2013, business rules were introduced to provide custom business logic and eliminate the need of writing scripts around this logic. But now with Dynamics CRM 2016, some of the\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":13,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[13,19],"tags":[225,234,1734],"class_list":["post-2652","post","type-post","status-publish","format-standard","hentry","category-customizations","category-dynamics-crm","tag-business-process-flow","tag-business-rules-in-dynamics-crm","tag-trigger-business-rules"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/2652","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/comments?post=2652"}],"version-history":[{"count":0,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/2652\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media?parent=2652"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/categories?post=2652"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/tags?post=2652"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}