⌘ K

ServiceDesk Plus · Admin Guide

Problem Templates

Problem templates are used to create forms with pre-populated data for logging problem requests in ServiceDesk Plus. Templates save time and effort by allowing users to create problem requests quickly.

 

Benefits:

  • Raise problem requests instantly for frequently occurring problems.
  • Configure different templates to collect relevant data based on the type of problem request.
  • Pre-fill field values in problem template to automatically populate details while raising problem request.
  • Divide the work involved into tasks.

 

Role Required: SDAdmin

 

Links:

Create Problem Template 

  1. Go to Admin > Templates & Forms (Problem/Change Management in old UI) > Problem Templates.
  2. Click New Problem Template.

Configure Template Details 

The template form consists of three sections: header, details (left pane), and canvas.

Header

Provide basic details of the template.

  • Template Name - Enter a unique name for the template.
  • Description - Briefly describe the usage of the template.

Details (Left Pane)

Contains default and additional fields configured in the application that are not used in the canvas. Drag fields to add them to the canvas.

Click Illustration 1: Problem Templates to create new additional fields or add sections to the template.

Canvas

Contains fields to capture necessary problem information. Some of the fields are system-defined and cannot be removed. All other fields can be added/deleted.

Further, you can define the field/section properties in the canvas.

  • Edit Field/Section - Hover over a field/section and click Illustration 2: Problem Templates to modify its properties.
  • Provide Default Field Values - Enter values in the template fields. These values will be auto-populated when the template is used to create a problem request.
  • Move Fields or Sections - Rearrange the fields and sections by using a simple drag-and-drop method. When a section is moved, the fields in the section will be moved as well.
  • Delete Field/Section - Click Illustration 3: Problem Templates to remove a field/section from the template. Deleted fields (including fields in deleted sections) will be moved back to the left pane.
You cannot delete sections containing system-defined fields such as Status, Technician, Site, Created Date, Completed Date, Title, and Description. However, you can delete a section after moving these fields to another section.

 

Illustration 4: Problem Templates

 

Add Field/Section to Template

Fields are used to store information and organize the data displayed in a form.

  • In the left pane, click Illustration 5: Problem Templates.
  • Drag a field type to the template canvas.
    • Based on the selected field type, the field properties vary. Click here to know how to configure different field types.
    • Provide Help Text to explain the field purpose to users while they create a problem using the template.
    • Mark the field as mandatory if needed.
    • You can customize the look and feel of a field from the Customization tab.
    • Click Save.
You can also create additional fields under Admin > Customization > Additional Fields > Problems [Old UI: Admin > Problem/Change Management > Problem Additional Fields]. Learn more.

 

Illustration 6: Problem Templates

 

Sections group fields logically making it easier for users to find problem details.

  • Drag a section type to the template canvas. You can add sections of type single column, double column, three columns, four columns, and flexible column.
    • Click Illustration 7: Problem Templates to add section details.
    • Provide a unique name to the section.
    • Add Help Text to explain the section purpose to users while they create a problem using the template.
    • You can modify the section type using the header drop-down.
    • You can customize the look and feel of a section if needed.
    • Click Save.

 

Illustration 8: Problem Templates

 

Flexible columns: Add different column layouts within a single section. When a field is added, the existing fields auto-align to fit the flexible column's width. Hover over a field in flexible column to perform the following actions:

  • Adjust field width: Click Illustration 9: Problem Templates or Illustration 10: Problem Templates to adjust the field width in the corresponding direction.
  • Justify field width: Click Illustration 11: Problem Templates to justify the width of all fields in the corresponding row.
  • Add relative fields: Click Illustration 12: Problem Templates and select the direction in which the field should be added. A field placeholder appears where you can drag and drop the required field.
  • Remove fields: Click Illustration 13: Problem Templates to remove a field from the canvas. The remaining fields will auto-align to fit the flexible section's width.
 You can add up to 12 fields in a flexible column row. 

 

Illustration 14: Problem Templates

 

Form Customization

Problem templates can be customized using different fonts, font sizes, font colors, background colors, and label orientation. Form customization can be used to highlight important fields/sections and to improve the overall aesthetic.

Templates can be customized at three levels:

  • Template - Click Customization Illustration 15: Problem Templates on the top right corner of the template. Template customizations will be applied to all sections and fields.
  • Section - Hover over a section and click Illustration 16: Problem Templates. Go to the Customization tab to customize the section.
  • Field - Hover over a field and click Illustration 17: Problem Templates. Go to the Customization tab to customize the field.

In the customization edit form for templates/sections/fields, you can configure:

  • Sections (not applicable to field customization) - Change font, font size, and color, and the background color. You can also bold the titles.
  • Labels - Change label placements to appear on the left, right, or top of the field box. You can also change the font, font size, color, and background color. Also bold the label if needed.
  • Background Color - You can choose a background color for the template by clicking the Illustration 18: Problem Templatesicon.

 

Illustration 19: Problem Templates

 

Template customizations are overwritten by section and field customizations. 

After adding fields/sections and customizing the template, click Save. The form will reload as Edit Template form and the Tasks tab will be displayed.

Associate Task Templates

You can associate task templates with a problem template to:

  • Standardize problem resolution process
  • Reduce time taken to understand the problem and decide on the resolution strategy.

After saving the problem details, go to the Tasks tab to associate tasks to the problem template.

  1. Click Associate to add a task from task templates.
  2. From the list of task templates displayed, select the tasks to be associated.
  3. Click Associate.

You can design task templates for the problem template by clicking Create Task Template. Refer to this page to learn how to configure a task template.

 

Illustration 20: Problem Templates

 

After adding task templates to a problem template, you can perform the following actions on the tasks:

  • Delete Tasks - Select the tasks to be dissociated and click Illustration 21: Problem Templates.
  • Search Tasks - Click Illustration 22: Problem Templates to perform a column search on the listed tasks.
  • Add/Remove Columns - Click Illustration 23: Problem Templates to modify the columns present in the task list view.
  • Mark Dependency - Click Dependencies to go to the task dependency map where you can mark the parent and child tasks.
  • Organize Tasks - Organize the order of task execution using the Organize button.

Preview Template

Use the Preview button to see how the template would appear to technicians.

 

Illustration 24: Problem Templates

 

Copy Template 

You can copy saved templates to reuse them.

  1. Open the required template from the problem template list view.
  2. Click Copy Template on the template header.
  3. Enter a new name of the template and click Copy.
  4. Open the copied template from the list view and make the necessary changes.
While copying a problem template, the associated task templates will also be copied.

 

Illustration 25: Problem Templates

 

List View Actions 

Problem templates created are itemized on the list view page. Use the filter drop-down on the page header to view the active/inactive problem templates in the list view.

 

Illustration 26: Problem Templates

 

You can manage them from the list view page and perform the following actions:

  • Edit/delete template - Click Illustration 27: Problem Templates to edit or delete a template. To delete templates in bulk, select the required templates and click Illustration 28: Problem Templates.
  • Set template as default - Set the frequently used template as default template by clicking Illustration 29: Problem Templates.
  • Search templates - Click Illustration 30: Problem Templates to search through templates.
  • Limit records displayed - Limit the number of records displayed in the list view by invoking the corresponding drop-down.
  • Reactivate template - In the Inactive Templates filter, click Illustration 31: Problem Templates beside a template and select Mark as active.
If you delete a template that is associated with an existing problem request, the template will be marked as inactive. 
You cannot delete the default template. 

Use Cases  

Scenario: Create problem requests for the following frequently occurring problems by capturing relevant details in the problem form:

  • Network outage
  • Storage Issues
  • Applications crash
  • Print server connectivity
  • Internet issue (Wifi / LAN)
  • Barcode machine failure
  • Network files accessibility

Configuration: Create problem templates for each server problem and configure additional fields specific to the problem in the relevant template.

Problem Template

Additional Fields Added

Network outage

Network Name - Picklist

Storage Issues

Space required (in GB) - Number

Application crash

Application Crashed - Drop-down

Error displayed (if any) - Single line

Criticality - Picklist

Issue faced - Multi-line

Potential crisis - Multi-line

Print server connectivity

Printer Name - Picklist

Internet issue (Wifi / LAN)

Network Name - Picklist

Barcode machine failure

Machine Serial Number - Number

Network files accessibility

IP range - Single line

Subnet details - Number

 

Scenario: Ensure storage-related problem requests are updated as high-priority and assigned to Technician A in Network support group. Highlight fields relating to the problem priority and impact.

Configuration:

  • Create a problem template named Storage Issue.
  • In the problem template, pre-select the following fields with default values.
  • Priority - High
  • Group - Storage
  • Technician - Technician A
  • Create the following sections and group fields as below:

Section

Fields grouped in the Section

Criticality

  • Priority
  • Impact
  • Urgency
  • Dueby Date

Impacted Areas

  • Assets Involved
  • Department
  • Services Affected.

 

  • Edit the section details and under Customization tab, add background colors to the Criticality and Impacted Areas sections.

 

Illustration 32: Problem Templates

 

Scenario: Trigger repetitive tasks involved in RCA analysis automatically when a application crash problem is logged. Mark related tasks so that they are executed sequentially. 

Configuration:

  • Create the following task templates under Admin > Templates & Forms > Task Templates:
    • Check server connectivity and health
    • Check for corrupt third-party PDBs in server
    • Analyze logs
    • Identify server/application processes that consume high computing power
    • Identify threads in server/application processes with increased computing power
    • Capture thread dumps
    • Analyze thread dump to identify code causing spike in CPU
    • Check impacted assets configuration records
    • Document RCA details in problem request
    • Create a report of issue behavior vs the expected behavior
    • Email engineering team and other stakeholders
  • In the Application crash problem template, go to Tasks tab and associate the task templates mentioned above with the problem template.
  • Click Dependencies. Link parent and child tasks as follows:

 

Parent Tasks

Child Tasks

Check server connectivity and health

Check for corrupt third-party PDBs in server

-

Analyze logs

Identify server/application processes that consume high computing power

Check impacted assets configuration records

 

Identify threads in server/application processes with increased computing power

Capture thread dumps  

Analyze thread dump to identify code causing spike in CPU

Document RCA details in problem request

 

Email engineering team and other stakeholders

-

Create a report of issue behavior vs the expected behavior

 

Illustration 33: Problem Templates