Creating and configuring Change Request Templates

Change Request Templates can be used to pre-fill information in the Change Request form. These can be for instance a predefined Title, Description, Impact, Risk, and Priority.

This recipe will describe the steps to create a new Change Request Template.

Getting ready

In the SCSM 2016 console, navigate to Library | Templates.

How to do it...

To create a Change Request Template, follow these steps:

  1. Click on Create Template in the Tasks pane.
  2. Enter a name. In this recipe, we use Change Request Service Pack Installation Template.
  3. Enter a description. For instance, This template can be used for Change Requests regarding deployment of Service Packs.
  4. Choose the Change Request class by clicking on Browse next to the Class field, and then click on OK.
  5. Choose an existing management pack or create a new one to store the Change Request Template (the Creating Management Packs to save your SCSM personalization recipe in Chapter 2, Personalizing SCSM 2016 Administration describes how to store your customizations in management packs as well as the best practice for naming conventions of the XML files).
  6. Click on OK.

    How to do it...

  7. Fill in the information in the related fields of the form. In this recipe, we pre-fill the fields Title, Description, Reason, Area (select Software from the drop-down box), and Priority (select Medium from the drop-down box), in the General tab of the Change Request Template.

    How to do it...

  8. Pre-fill all fields you need in the Planning tab of the Change Request Template. In this recipe, we use Implementation Plan, Risk Assessment Plan, Test Plan, and Back out Plan.

    How to do it...

  9. Click on OK to save and close the Change Request Template.

How it works...

Basically a pre-filled template in SCSM 2016 can be used to create new Work Items (for instance Incident Records, Change Requests, and Service Requests). Using templates keeps the content and information of forms consistent. Using pre-filled templates will also reduce the time each individual spends initiating the relevant Work Item.

There's more...

Change Management reporting is important due to the visibility and tracking provided, which is key to continually improving the process.

Reporting scheduled and actual date information

Providing the Scheduled Start and End Time of change requests is very helpful for reporting on the progress of the Change Management process. These key performance indicators offer a good overview on how many change requests are completed within the planned time.

To get more information about reporting please look at the recipes in Chapter 10, Working with the Data Warehouse and Reporting of this cookbook.

See also

Microsoft TechNet Library: Managing Changes and Activities in System Center - Service Manager: https://technet.microsoft.com/en-us/system-center-docs/sm/manage/ops-managing-changes-and-activities-in-system-center-2016-service-manager.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset