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:
The template form consists of three sections: header, details (left pane), and canvas.
|
Header |
Provide basic details 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 |
|
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.
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.
|

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

Sections group fields logically making it easier for users to find problem details.
to add section 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:
or
to adjust the field width in the corresponding direction.
to justify the width of all fields in the corresponding row.
and select the direction in which the field should be added. A field placeholder appears where you can drag and drop the required field.
to remove a field from the canvas. The remaining fields will auto-align to fit the flexible section's width.

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:
on the top right corner of the template. Template customizations will be applied to all sections and fields.
. Go to the Customization tab to customize the section.
. Go to the Customization tab to customize the field.In the customization edit form for templates/sections/fields, you can configure:
icon.

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

After adding task templates to a problem template, you can perform the following actions on the tasks:
.
to perform a column search on the listed tasks.
to modify the columns present in the task list view.Use the Preview button to see how the template would appear to technicians.

You can copy saved templates to reuse them.

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:
to edit or delete a template. To delete templates in bulk, select the required templates and click
.
.
to search through templates.
beside a template and select Mark as active.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 |
|
|
Impacted Areas |
|
Edit the section details and under Customization tab, add background colors to the Criticality and Impacted Areas sections.

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