{"id":3179,"date":"2012-07-30T22:45:40","date_gmt":"2012-07-30T20:45:40","guid":{"rendered":"http:\/\/contoso.se\/blog\/?p=3179"},"modified":"2012-07-30T22:45:40","modified_gmt":"2012-07-30T20:45:40","slug":"add-a-new-activity-to-a-existing-service-request","status":"publish","type":"post","link":"http:\/\/contoso.se\/blog\/?p=3179","title":{"rendered":"Add a new activity to a existing service request"},"content":{"rendered":"

A couple of weeks ago I was working on a scenario were we needed to add a review activity to a service request with Orchestrator. Part of the solution for that scenario were a couple of runbooks that I want to share in this blog post. These runbooks adds a new review activity to a existing service request.\u00c2\u00a0All runbooks\u00c2\u00a0require\u00c2\u00a0a input parameter when it starts, the service request ID. These runbooks set the domain admins group as reviewers in the new review activity.<\/p>\n

When adding a new activity to for example a service request it is always added as the first activity. If there are already two activities the new activity is added before them, in other words the new activity is the one that will run first. You can control this by working with the sequence ID parameter. The first activity have value 0 and the second have value 1 and so on. If two activities have the same value they will run at the same time. You can update activities already existing in the service request and insert the new activity in any order you need, as the 70.2 runbook do.<\/p>\n

This example is built on three runbooks.<\/p>\n