User Orchestrator with Service Manager to Disable User Accounts – Part 3

In Post 1 I showed you how to create a runbook to disable a user account with the only input being the Activity Guid of the runbook in Service Manager. In Post 2 I showed you how to create a new management pack and class in the Authoring Tool. In this post we will create a runbook template in Service Manager 2012 using the runbook from Post 1 and then create a Service Request template based on the custom class from Post 2 containing the new runbook activity template.

1. If you have configured the Orchestrator connector in Service Manager 2012 then after a synchronization you should see the runbook create from Post 1. Go to Library and then Runbooks to see all runbooks that have been imported.

   

2. Click on the DisableUser runbook and then in the Tasks pane click on Create Runbook Automation Activity.
3. In the next window give your template a descriptive name such as Disable User Runbook Template, leave the class as Runbook Automation Activity and choose the management pack that was created in Post 2. Click OK.

   

4. Next the template will pop up. Give it a descriptive title, choose an Area such as Directory\Account Management and a State such as Release. Also it is very important to check the “Is Ready For Automation” checkbox as this will allow the runbook to run automatically without an administrator needing to manually check the box later.

   

5. Next click the Runbook tab at the top. You can either edit the mapping for the ActiveGuid on this template or on the Service Request template later. I will go ahead and map it here by clicking Edit Mapping, expand Object and click ID. I cannot map the PortalUser mapping here because it depend on data from the Service Request. Therefore it will be mapped later in the Service Request Template.

   

6. Click Close and then OK. At this point your runbook template is complete.
7. Next we need to create the Service Request template. In the Library section go to Template and click Create Template. Give the template a name such as Disable User Service Request Template. Choose the class from Post 2, when you browse for this class you will need to change the filter to All Basic Classes in order to see the custom class. Be sure to save the template in the new management pack created in Post 2

   

8. Next, fill out the fields on the General tab of the template the way you want then to be when new service requests of this class are created.

   

9. Next click the Activities tab and add a new activity. Choose the template created earlier in this post. This will bring up the template as shown below.

   

10. Click on the Runbook tab of the template. You can now map the PortalUser property mapping because the DisableUserClass is now available to map to. Be sure to map this property to whatever field that you are going to map it to later when creating the request offering. For example, later I will map the portal user to the Notes field of the Service Request so as shown below, I will also map the runbook property to the Notes field of the DisableUserClass.

    

11. Click Close and then click OK twice to complete the creation of the template.

In the next post we will create a request offering based off of this service request template. We can then add the request offering to a service offering and publish both to the portal.