Over the next months I will write some articles to explain new features and possibilities of Service Manager 2012. Some information is already public, some is not. I will take care that only allowed public information will be published here.
Today, I want to show how users can request IT offerings by using the self service portal. These Screenshots have been extracted from an MMS 2011 Session that has ben recorded – so this is public stuff. Thanks to Anders for the “extraction” work!
Step 1 – Preparation
First, we need to build the Service Catalog with our Offerings. To do that, one or more Service Offering needs to be created and filled up with detailed information, icons, help articles and more.
Within the Service Offering we now need to create the detailed Request Offerings. Most of the Service Offerings will require the user to input date when requesting the offering. Therefore we can add several questions that are either marked as required or optional. Based on these questions, a dynamically generated form will be presented to the users that are requesting offerings.
Now we can map the user questions to attributes of a Runbook Activity (Runbooks can be imported to the CMDB from System Center Orchestrator by using a connector). This is important because the user input will be needed to trigger the Runbook.
Step 2 – User Request for an IT Service
Now as everything is prepared for the consumers, let’s check the Self Service Portal. The configured Service Offerings are visible to the users, based on their User Roles.
After choosing the needed Service Offering – in this case “Cloud Services”, the different Requests Offerings are presented to the User. If needed, the user can open help articles that are published to help them with their request.
Now based on the chosen Request Offering, the user has to answer some questions. In this case a VM Template, a VM Name and some more. It is very important to capture structured and complete data from the user if we later want to successfully execute runbooks in System Center Orchestrator.
Step 3 – Check Service Request and automate execution
After the user completed the wizard, a new Service request is automatically generated that holds all the details that the user provided.
The Service Request has one or more Activities, based on the Service Request Template that was chosen earlier. In this case we only have 2 Activities. The Approval Activity allows a defined Person (e.g. a Team Leader) or a Line Manager to approve the Request. If the approval is done, the next Activity will start. Because the second Activity is a Runbook Activity, a runbook in System Center Orchestrator is triggered.
The input from the User is now translated to Attributes that the runbook needs as input. When the runbook completes, Orchestrator reports back that the execution was successful so that Service Manager can mark the Activity as complete. Because this is the last Activity, the Change Request status will also change to completed and work is …