{"id":2943,"date":"2012-04-11T09:51:09","date_gmt":"2012-04-11T07:51:09","guid":{"rendered":"http:\/\/contoso.se\/blog\/?p=2943"},"modified":"2012-04-11T09:51:09","modified_gmt":"2012-04-11T07:51:09","slug":"convert-a-incident-to-a-service-request-with-a-bit-of-orchestrator-magic","status":"publish","type":"post","link":"http:\/\/contoso.se\/blog\/?p=2943","title":{"rendered":"Convert a incident to a service request, with a bit of Orchestrator magic"},"content":{"rendered":"

A couple of days ago there was a question about converting a incident in Service Manager to a service request. The scenario was around a support call first register as an incident, but later the operator finds out it should be a service request. Out of the box in Service Manager there is no tool to move the data we have already input in the incident over to a new service request. But of course we could use Orchestrator to do it \ud83d\ude42 We could also build this workflow as an internal workflow in Service Manager… but that would take me a lot of hours; this runbook only took two cups of coffee. In this post I will show a idea how to build a task that you can run against a incident in Service Manager to “convert” it into a service request. The incident is not really converted, we copy the info we have in the incident over to a new service request, link them together and close the incident.<\/p>\n

The runbook is trigger by a task in Service Manager, input parameter is only the incident ID.<\/p>\n

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

 <\/p>\n

 <\/p>\n

 <\/p>\n

    \n
  1. Initialize Data. Input parameter is IncidentID. ID of the incident we want to “convert” to a service request<\/li>\n
  2. Get Object. Gets the incident from Service Manager. This step also verify that the incident\u00c2\u00a0don’t\u00c2\u00a0have Closed as status<\/li>\n
  3. Send Platform Event. If the incident is closed or cant be found a platform event is generated. For example if you trigger the runbook with a incorrect incident ID from the Orchestrator console it will not run<\/li>\n
  4. Get Relationship. Gets related Active Directory User to the incident<\/li>\n
  5. Get Object. Gets the user that step 4 found<\/li>\n
  6. Create Object. Creates a new service request and writes info to it from the incident<\/li>\n
  7. Create Relationship. Create a\u00c2\u00a0relationship\u00c2\u00a0between between the service request and the affected user (relationship type = user)<\/li>\n
  8. Create Relationship. Create a relationship between the service request and the incident (relationship class = is related to work item)<\/li>\n
  9. Format Date\/Time. Gets the current time stamp in a correct format, will be used when creating comments on the incident and the service request<\/li>\n
  10. Run .NET Script. A small PowerShell script that generates a GUID. The GUID will be used as ID for the incident comment<\/li>\n
  11. Create Related Object. Creates a Trouble Ticket Action Log (action log comment) on and relates it to the incident. The runbook writes a comment saying the incident has been\u00c2\u00a0converted\u00c2\u00a0to a service request (relationship type = Trouble Ticket Has Action Log)<\/li>\n
  12. Update Object. Resolve the incident, change status to Resolved<\/li>\n
  13. Run .NET Script. A small PowerShell script that generates a GUID. The GUID will be used as ID for the service request comment<\/li>\n
  14. Create Related Object. Creates a Trouble Ticket Analyst Comments (log comment) and relates it to the service request. The runbook writes a comment saying the service request was based on the incident<\/li>\n
  15. Send Platform Event. Writes a platform event with service request ID and incident ID<\/li>\n<\/ol>\n

    That is the runbook, the next component is the task in Service Manager. We could trigger the runbook from Orchestrator console and input the incident ID manually, but it is easier with a task in Service Manager. In the Service Manager console, in the Library workspace you can create a new task with the following settings.<\/p>\n