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:

 

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 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 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 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.

 

 

Add Field/Section to Template

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

You can also create additional fields under Admin > Customization > Additional Fields > Problems [Old UI: Admin > Problem/Change Management > Problem Additional Fields]. Learn more.

 

 

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

 

 

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:

 You can add up to 12 fields in a flexible column row. 

 

 

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:

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

 

 

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:

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 TemplateRefer to this page to learn how to configure a task template.

 

 

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

Preview Template

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

 

 

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.

 

 

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.

 

 

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

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:

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:

Section

Fields grouped in the Section

Criticality

  • Priority
  • Impact
  • Urgency
  • Dueby Date

Impacted Areas

  • Assets Involved
  • Department
  • Services Affected.

 

 

 

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:

 

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