{"id":590,"date":"2014-06-12T11:49:17","date_gmt":"2014-06-12T06:19:17","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=590"},"modified":"2014-06-12T11:49:17","modified_gmt":"2014-06-12T06:19:17","slug":"custom-state-model-transitions-in-spring-release-for-dynamics-crm-2013","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2014\/06\/custom-state-model-transitions-in-spring-release-for-dynamics-crm-2013\/","title":{"rendered":"Custom State Model Transitions in Spring Release for Dynamics CRM 2013"},"content":{"rendered":"<p>There is a completely new and useful feature of Status Reason Transitions introduced in the Spring Release for Dynamics CRM 2013 Leo. This blog would walk you through the brief explanation of <b>Custom State Model Transitions<\/b> and how to implement them in CRM using real life example.<\/p>\n<p><span style=\"line-height: 1.5em;\">This feature is only applicable to <\/span><b style=\"line-height: 1.5em;\">Case <\/b>(<b style=\"line-height: 1.5em;\">Incident<\/b>)<span style=\"line-height: 1.5em;\"> and <\/span><b style=\"line-height: 1.5em;\">Custom entities<\/b><span style=\"line-height: 1.5em;\">. As there is no capability to play around with the statecode i.e. Status, we can achieve the desired requirement through status code i.e. Status Reason instead.<\/span><\/p>\n<p>We have illustrated this feature below\u00a0by applying it to a custom entity called \u201cProjects\u201d:<\/p>\n<p><span style=\"line-height: 1.5em;\">Customize the project entity, navigate to fields and locate \u201c<\/span><b style=\"line-height: 1.5em;\">Status Reason<\/b><span style=\"line-height: 1.5em;\">\u201d field. Open Field properties where you will find a new button \u201c<\/span><b style=\"line-height: 1.5em;\">Edit Status Reason Transitions<\/b><span style=\"line-height: 1.5em;\">\u201d has been introduced. This same button can also be found in Case entity as well as other custom entities in their respective \u201c<\/span><b style=\"line-height: 1.5em;\">Status Reason<\/b><span style=\"line-height: 1.5em;\">\u201d field.<\/span><\/p>\n<p><a href=\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2014\/06\/img115.jpg\"><img decoding=\"async\" class=\"alignnone size-full wp-image-618\" alt=\"img1\" src=\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2014\/06\/img115.jpg\" width=\"749\" height=\"652\" \/><\/a><\/p>\n<p>Here, the project entity being a custom entity will only have two Status i.e. Active and Inactive. We have added status reasons in both these status. Above screenshot shows the status reasons added for Active state. Refer to the below screenshot for status reasons added for Inactive state.<\/p>\n<p><img decoding=\"async\" class=\"alignnone size-full wp-image-592\" alt=\"img2\" src=\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2014\/06\/img24.jpg\" width=\"521\" height=\"142\" \/><\/p>\n<p>With this setup, if you click on <b>Edit Status Reason Transitions, <\/b>a new window will be open for defining the dependent transitions. On that window you can notice a checkbox \u201c<b>Enable Status Reason Transitions<\/b>\u201d and checking that would apply the status transition functionality for that particular entity.<\/p>\n<p>Apart from that, you can see the list of <b>Status Reason<\/b> for different State and<b> <\/b>each Status Reason is associated with an image as explained below:<\/p>\n<p><strong><span style=\"line-height: 1.5em;\"><span style=\"text-decoration: underline;\">For custom entity<\/span>:<\/span><\/strong><\/p>\n<p><a href=\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2014\/06\/11.jpg\"><img decoding=\"async\" class=\"alignnone size-full wp-image-614\" alt=\"1\" src=\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2014\/06\/11.jpg\" width=\"402\" height=\"41\" \/><\/a><\/p>\n<p><strong><span style=\"text-decoration: underline;\">For Case entity<\/span>:<\/strong><\/p>\n<p><a href=\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2014\/06\/25.jpg\"><img decoding=\"async\" class=\"alignnone size-full wp-image-615\" alt=\"2\" src=\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2014\/06\/25.jpg\" width=\"416\" height=\"57\" \/><\/a><\/p>\n<p><span style=\"line-height: 1.5em;\">Now you can go ahead to provide new <\/span><b style=\"line-height: 1.5em;\">Status Reasons Transition<\/b><span style=\"line-height: 1.5em;\"> for a particular Status Reason. Below we have setup the transition for project entity:<\/span><\/p>\n<p><a style=\"line-height: 1.5em;\" href=\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2014\/06\/img34.jpg\"><img decoding=\"async\" class=\"alignnone size-full wp-image-593\" alt=\"img3\" src=\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2014\/06\/img34.jpg\" width=\"733\" height=\"488\" \/><\/a><\/p>\n<p>Now suppose, you create a new project then it will be in Active state \u2013 Analyze In-Progress status reason. And the status reason option will show only \u201cAnalyze In-Progress\u201d, \u201cAnalyze Complete\u201d and \u201cQuote Sent\u201d as the only options from the list of various options because we have defined such that when \u201cAnalyze In-Progress\u201d is selected then only \u201cAnalyze Complete\u201d and \u201cQuote Sent\u201d are the ones to be displayed for user to select further.<\/p>\n<p><a href=\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2014\/06\/img44.jpg\"><img decoding=\"async\" alt=\"img4\" src=\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2014\/06\/img44.jpg\" width=\"269\" height=\"109\" \/><\/a><\/p>\n<p>You will notice that in the transitions, for Analyze In-progress, we have also mentioned \u201cProject Cancelled\u201d with its symbol indicating that it is for Inactive state. Hence, being in Analyze In-progress, if you deactivate the record, then status reason will be \u201cProject Cancelled\u201d.<\/p>\n<p>Then, being in \u201cProject Cancelled\u201d status reason, if this project needs to be activated again, then on Activation, it will ask for the status reason you want that to be on as we have mentioned many status reasons when project cancelled is selected.<\/p>\n<p><a style=\"line-height: 1.5em;\" href=\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2014\/06\/img54.jpg\"><img decoding=\"async\" class=\"alignnone size-full wp-image-595\" alt=\"img5\" src=\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2014\/06\/img54.jpg\" width=\"485\" height=\"244\" \/><\/a><\/p>\n<p>&nbsp;<\/p>\n<p>Note\u00a0that if you are in \u201cAnalyze In-progress\u201d and then select \u201cAnalyze Complete\u201d you will need to \u201cSAVE\u201d the record for the dependent transitions to take effect. Only after saving the record, the status reason will show \u201cQuote Sent\u201d as the other option.<\/p>\n<p><strong><span style=\"text-decoration: underline;\">Conclusion<\/span>:<\/strong><\/p>\n<p><strong><\/strong><span style=\"line-height: 1.5em;\">This provides ability to the administrators to define the transitions so that sales persons, service people could select appropriate reason being in one state. This will ensure that the business process has been followed as expected.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>There is a completely new and useful feature of Status Reason Transitions introduced in the Spring Release for Dynamics CRM 2013 Leo. This blog would walk you through the brief explanation of Custom State Model Transitions and how to implement them in CRM using real life example. This feature is only applicable to Case (Incident)\u2026 <span class=\"read-more\"><a href=\"https:\/\/www.inogic.com\/blog\/2014\/06\/custom-state-model-transitions-in-spring-release-for-dynamics-crm-2013\/\">Read More &raquo;<\/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":[21,22,24],"tags":[392,595,1413,1672,1673],"class_list":["post-590","post","type-post","status-publish","format-standard","hentry","category-dynamics-crm-2013","category-dynamics-crm-2015","category-dynamics-crm-2016","tag-crm-2013","tag-dynamics-crm-2013","tag-reason","tag-state-transition","tag-status"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/590","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=590"}],"version-history":[{"count":0,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/590\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media?parent=590"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/categories?post=590"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/tags?post=590"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}