This blog describes an example solution to demonstrated the customization capabilities of System Center Service Manager – a customization show case. The creation of the described solution started with a request of a customer and feedback on the out-of-the-box functionality I have received. The following functionality request and feedback was the start point for the creation of the SCSM Intake task:
- - Cascading dependencies should be available for the intake of an Incident or Request.
- - It should be possible to display knowledge article information while service desk is completing the intake of a request.
- - It must be possible to directly resolve the work item.
These functionalities can really have an added value for the intake of a request. In my solution and answer on the desired functionality I enable the following capabilities in the Service Manager console via a custom task:
- - Service/Incident managers can enforce their process; impact and urgency can be set based on the selections made in the cascading dependencies dropdown list boxes.
- - Service desk analyst does not always know the Incident routing information. The routing configuration can be set for the selections and based on the selections made in the form the correct support group is set.
- - Intake configuration of the cascading dependencies is made in the Library workspace. Customers can apply their own settings for the intake of the requests.
An overview of my solution:
- I have created a custom task for the intake of an Incident. The default Incident form is not replaced, after the intake of the request the analyst make use of the default forms in Service Manager. Service, Component and Symptom are custom configuration item classes. Views and forms are there to create and configure the intake settings in the Library workspace. Below a screenshot of the “symptom” form. Some explanation around this configuration:
- - Display name: displayed selection in the form
- - ID’s: currently the cascading dependencies configuration is based on ID’s. This will be changed to relationships to ease up the configuration of the functionality.
- - Impact, Urgency and support group are set on the work item when selected
- - Knowledge article that is presented when selected.
- In the solution that I have build there is a four level selection, as you can see in figure below. The selection to create an Incident or request can be made in the two checkboxes. Classification Category, Service, Component and Symptom displayed items are depended on the selection you make in the list box above. For example, you will only see components from the service you have selected.
- 1. Items in the drop down are enumerated from the custom classes that are created and configured in the library workspace. List boxes with cascading dependencies : each selection defines what will be presented in the next drop down.
- 2. Last selection sets the support group, Impact and Urgency on the work item.
- 3. Each drop down item can have a related knowledge article. This is presented to the analyst. Can be a questionnaire or simply input for resolution…
The complete intake task I have build includes:
- - User pickers to specify Affected user and reporting user.
- - Affected user his devices (primary owner & User uses device) are listed in the “Affected configurations items” drop down. Other can be searched via the buttons next to the list view.
- - Via the “Assistance” button a remote assistance session can be started to the specified computer.
- - Files can be added…
- - Incidents can be submitted and also directly resolved.
This is an example solution that is created for a customer. As you can see, if it’s not in the product you can build it your self
Have fun customizing SCSM on AuthoringFriday!
Kurt Van Hoecke