Similarly, if a user reactivates a case and changes its status from “Resolved” back to “Active”, the user is free to choose any one of the “Active” status reasons: “In Progress”, “On Hold”, “Waiting For Details”, or “Researching”. The record becomes read-only and can only be set to one of the following OOB status reasons: On the other hand, if a user deactivates a case, under the hood, the case’s status changes from “Active” to “Resolved”. For example, out of the box case record can have an “Active” status where its status reason (one of the following) provides a more granulate explanation of its stage in the service process: The status and status reason of a case record in Dynamics CRM represent the current stage that a case record is at in a business, e.g. In Dynamics CRM most system entities (as well as custom entities) have 2 tightly coupled option sets known as “status” (schema name “statecode”) and “status reason” (schema name “statuscode”) that define the status and status reason of an entity record at a given time. What is all the fuss about case status reason transition? Why is it that planning is important before enabling this new functionality in CRM 2013 Service Pack 1?
0 Comments
Leave a Reply. |