- \n
- Strictly Linear Process: Business processes are designed to work only in linear manner, no branching is allowed.<\/li>\n
- Cannot Revisit The Entity More Than Once: Cannot visit the same entity again in flow single business process flow.<\/li>\n
- No programmability support<\/li>\n<\/ul>\n
New improvements in VEGA:<\/strong><\/p>\n
- \n
- Here, you have the ability to define branches as well as branching rules. You can create and update branching rules through UI and it can be evaluated in real time. Branching rules must be based on the steps involved in stages.<\/li>\n
- Steps and stages can be configured easily where branching rules are defined.<\/li>\n
- Selection of entity relationships \u2013 It can be optionale. previously in CRM 2013 if you wanted to add an entity in business process flow, then it was necessary for the entity to be in 1:N\u00a0relationship with another entity but now, if there is no 1:N relation between the two entities, you can still add that entity in process flow, the only requirement is that the entity must be enabled to create BPF.<\/li>\n
- Branching supports \u2013 Single entity, cross entity and also supports multiple entity loops.<\/li>\n
- Entity used in BPF can be revisited multiple times.<\/li>\n
- Programmability through client API: Programmatically updates process state and hooks on to process events.<\/li>\n<\/ul>\n
To elaborate this further, we can consider a scenario where you sell \u2018Software\u2019 as a product in your organization. The requests you receive on daily basis get classified as leads, some of them get Qualified if they are further interested in evaluating the trial of the software, if not, then the lead get disqualified.<\/p>\n
Once a lead is interested in trial, the lead gets Qualified and an Opportunity gets created. Once the trial is completed, we ask if a Quote is required. If no, we close the Opportunity but if it is a yes, we create a quote and deliver the quote. After that, we offer maintenance for the product, if the Opportunity is interested in maintenance, we update the Quote, otherwise we create Invoice and at the end close Opportunity.<\/p>\n
Now, we have created a Business process as follows. This shows the updated UI for designing the Business process flow.<\/p>\n
![\"Business](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2014\/10\/15.jpg\")
<\/a><\/p>\nThis provides UI to edit \u2018Stage Name\u2019, \u2018Entity\u2019 to be selected, \u2018Stage Category\u2019, then \u2018Step Name\u2019 and their Value which includes the fields required to show on BPF followed by the \u2018Required\u2019 status of the steps.<\/p>\n
Further, you can see the \u2018Insert stage\u2019 button and the \u2018Add branch\u2019 button at the bottom of the stage as shown below:<\/p>\n
![\"Stage](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2014\/10\/21.jpg\")
<\/a><\/p>\nInsert stage:<\/strong> Adds a new stage in the process.<\/p>\n
Add Branch:<\/strong> Adds branching in flow. When you click on \u2018Add branch\u2019 button, it will allow to check some specific conditions and on that basis the branching will be done as shown below:<\/p>\n
![\"Check](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2014\/10\/31.jpg\")
<\/a><\/p>\nAs you can see above, it will apply \u2018if\u2019 criteria to check condition, where we can specify field criteria and save the condition. Once it is saved, it will allow you to insert stage on that basis as shown below. It also allows to add else condition if the criteria to flow the process in another direction is not fulfilled. You can combine multiple conditions using And\/or branching techniques.<\/p>\n
![\"Insert](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2014\/10\/41.jpg\")
<\/a><\/p>\nHere, it will also allow you to set relationship with another entity. If no relationships exist, then you can set it to none. Likewise, you can create complete BPF and it can be used as shown below:<\/p>\n
![\"Select](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2014\/10\/51.jpg\")
<\/a><\/p>\nLikewise, you can create a complete BPF and it can be used as shown below:<\/p>\n
As you can see below, it currently shows only two stages \u2018Qualify\u2019 and \u2018Close\u2019 and the step \u2018Is Interested In Trial\u2019 shows value as No.<\/p>\n
![\"Lead](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2014\/10\/61.jpg\")
<\/a><\/p>\nIf you select \u2018Is Interested In Trial\u2019 as yes it will change the flow with additional stages as shown below:<\/p>\n
![\"Lead](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2014\/10\/71.jpg\")
<\/a><\/p>\nSimilarly, after qualifying the lead, it will go to another stage where if you select \u2018Is Require Quotation\u2019 as yes, it will show some additional stages as \u2018Deliver Quote\u2019, \u2018Offer Maintenance\u2019 etc. as shown below:<\/p>\n
![\"Lead](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2014\/10\/81.jpg\")
<\/a><\/p>\nThis is how you can include business process flow in CRM using advanced features.<\/p>\n
Note:<\/strong><\/p>\n
- \n
- The process can span across maximum 5 unique entities<\/li>\n
- It can include maximum of 30 stages per process and 30 steps per stage<\/li>\n
- Each branch can be no more than 5 levels deep<\/li>\n<\/ul>\n
Hope this helps!<\/p>\n","protected":false},"excerpt":{"rendered":"
As you may be aware, Microsoft has come up with Business process flow feature in CRM 2013 which provides assistance to users in CRM using stages to be followed in order to complete the whole process. Earlier Limitations: Strictly Linear Process: Business processes are designed to work only in linear manner, no branching is allowed.\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":[6,22,24],"tags":[218,225,597,740,1668],"class_list":["post-1037","post","type-post","status-publish","format-standard","hentry","category-business-process-flows","category-dynamics-crm-2015","category-dynamics-crm-2016","tag-branch","tag-business-process-flow","tag-dynamics-crm-2015","tag-entity","tag-stage"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/1037","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=1037"}],"version-history":[{"count":0,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/1037\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media?parent=1037"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/categories?post=1037"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/tags?post=1037"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}