{"id":2418,"date":"2016-02-12T17:37:29","date_gmt":"2016-02-12T12:07:29","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=2418"},"modified":"2016-02-12T17:37:29","modified_gmt":"2016-02-12T12:07:29","slug":"set-process-through-workflow-in-dynamics-crm-2016","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2016\/02\/set-process-through-workflow-in-dynamics-crm-2016\/","title":{"rendered":"Set Process through Workflow in Dynamics CRM 2016"},"content":{"rendered":"

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

Since the release of Microsoft Dynamics CRM 2013, the new feature of building and deploying a standard business process flow has become important to organizations. The prime objective was to make CRM users capable to visualize more than one process. Regardless of the nature of the record, building of process flows help towards understanding the lifecycle of the record.<\/p>\n

In CRM 2015, in case automation was desired, it was required to change the business process flow through a script. But, now it\u2019s easy with the OOB workflow in MS Dynamics CRM 2016. Just a few settings will help you do the rest.<\/p>\n

Let\u2019s see how to the process is set:<\/p>\n

Consider 2 Business Process Flows:<\/p>\n

A) Purchase Immediate<\/strong><\/p>\n

B) Next Quarter<\/strong><\/p>\n

    \n
  1. Create a workflow \u2018Change Status<\/strong>\u2019 as shown in the screenshot below:\"set<\/a><\/li>\n<\/ol>\n

    This workflow will trigger when the<\/strong> Lead is created and when the<\/strong> Purchase TimeFrame field is changed.<\/p>\n

    A Condition for checking the Purchase Timeframe <\/strong>field on Lead record is subsequently added.<\/p>\n

    If Purchase Timeframe == Immediate then the Purchase Immediate Process flow would be set.<\/p>\n

    Here are the steps:<\/strong><\/p>\n

    Click \u2018Perform Action<\/strong>\u2019 from Add Step. Select SetProcess<\/strong> and Entity as None (Global)<\/strong>. Then click \u2018Set Properties\u2019<\/strong>. A \u2018Set SETPROCESS input window\u2019<\/strong> as shown below is displayed:\"set<\/a><\/p>\n

    Here the desired process which needs to be set is selected. In this case, set \u2018Purchase Immediate\u2019<\/strong>.<\/p>\n

    In Target select the Entity for which the Business Process flow needs to be set. In our case select the Lead itself.<\/p>\n

    In similar way, check if Purchase TimeFrame<\/strong> == \u2018Next Quarter\u2019<\/strong> then set \u2018Next Quarter<\/strong>\u2019 process.<\/p>\n

    Save the workflow and activate it.<\/p>\n

    Now, test the above workflow.<\/p>\n

    Then quickly create a Lead Record \u2018Test Lead Record for Immediate\u2019<\/strong> with Purchase TimeFrame == \u2018Immediate\u2019<\/strong> as shown below:\"set<\/a><\/p>\n

    Save the record.<\/p>\n

    Navigate to Leads and open the created record.<\/p>\n

    The \u2018Purchase Immediate\u2019<\/strong> Process will be set on this record as shown in the screenshot below:\"set-process-through-workflow\"<\/a><\/p>\n

    Note: Sometimes the user needs to press the Function Key, \u2018F5\u2019 to refresh the record clicking. This helps to view the effect when the workflow fires on the change of field.<\/em><\/strong><\/p>\n

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

    On a concluding note, it\u2019s exciting to know that you no longer need to write codes for changing the process flow. Your CRM user need not get trained in programming language when it easy to set a process through the steps mentioned above.<\/p>\n

    You may also like too see :\u00a0User Adoption Metrics that matter in your Dynamics CRM<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"

    Introduction: Since the release of Microsoft Dynamics CRM 2013, the new feature of building and deploying a standard business process flow has become important to organizations. The prime objective was to make CRM users capable to visualize more than one process. Regardless of the nature of the record, building of process flows help towards understanding\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,16,24,67],"tags":[1593,1594],"class_list":["post-2418","post","type-post","status-publish","format-standard","hentry","category-business-process-flows","category-dynamics-365","category-dynamics-crm-2016","category-workflows","tag-set-process","tag-set-process-through-workflow"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/2418","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=2418"}],"version-history":[{"count":0,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/2418\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media?parent=2418"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/categories?post=2418"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/tags?post=2418"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}