Incident Template

Incident templates are used to build forms with pre-populated data that can be utilized to log incidents quickly. Templates save time and effort by effectively capturing necessary information.

Role Required: SDAdmin

Benefits:

 

This document contains the following topics that explain incident template creation and management:

Create Incident Template    

  1. Go to Setup > Templates & Forms > Incident Template.
  2. Click New Incident Template.

By default, the Technician View is loaded. The displayed form consists of three main sections: Header, Field List, and Canvas.

Header

Provide basic details of the template. 

  • Icon: Add an icon to the template. You can choose from the available library, upload a new icon, or attach an icon from the Cloud.
  • Template Name * - Enter a unique name for the template.
  • Comments - Briefly describe the usage of the template.
  • Workflow/Life cycle: Select the workflow or life cycle to be associated with the template.

Field List

The field list in the right pane contains two tabs: Available Fields and New Fields.

  • Available Fields - Contains default and additional fields configured in the application that are not used in the canvas. Drag any field from this list to the canvas.
  • New Fields - Contains various field types that you can use to create additional fields instantly for the incident template. To create a new field, drag a field type to the template canvas and add the required details.
    • Based on the selected field type, the field properties vary. Refer to this admin page to know how to configure different field types.
    • You can also create additional fields under Setup > Customization > Additional Fields > Request. Learn more.

You can also add sections to the template from the right pane. Use the New Section element to add sections to the template and group the fields within the section.

To understand the usage of default fields, refer to incident creation page

Canvas

The canvas contains various fields that are vital in capturing information about the incident. Some fields are system-defined.

To customize sections added to the canvas,

  • By default, sections are untitled. Click on the left corner of the section header to name the section.
  • Hover over a section and click to set the following section properties:
    • Number of Columns - Choose if you want the section to have one or two columns.
    • Label Orientation - Choose if you want the field labels to be aligned on the left, top, or right to the input boxes.
    • Collapsed State - You can choose to collapse sections automatically while loading the form. This property can be defined only if the section is named.
    • Click Delete Section to remove the section from the template. The fields in the section will be moved to the field list on the right pane.
  • Click on the section header to drag the section anywhere in the canvas.

To customize fields added to the canvas,

  • Hover over a field to define the field properties.
    • Click to mandate the field and allow requesters to view/set the field value.
    • Click to remove a field from the template.
    • Click or on the either sides of the field to adjust the field width.
  • Use to move the field within or across sections.
  • Specify values in the field to set default values.
Mandating Item field will also mandate Sub-category and Category fields.
Mandating Impact Details field will mandate Impact field as well.
For the Requester Name field, you can configure sub-fields as field properties. Hover over the field and click . Select the sub-fields to be displayed beneath the field. When a requester is selected, the details will be auto-populated in the sub-fields.
Hard-coded fields  or sections containing hard-coded fields cannot be removed from the template. However, you can move these fields to other sections before deleting a section.

 

You can see how the template is displayed to technicians using the Preview button on the top of the template.

 

The form will reload as Edit Incident Template form and the Requester View, Tasks, Checklist, and Form Rules tabs will be displayed.

Configure Requester View 

If the template is enabled for requesters, go to the Requester View tab to configure the template layout for requesters by adding fields and sections as explained above.

Use the Preview button at the top of the template to see how the template is displayed to requesters.

Add Tasks

The work involved in resolving the request can be broken down into tasks. You can assign technicians to the tasks and set the tasks to be triggered when needed.

Define Task Settings

Requester Permissions - Enable permissions to allow requesters to track tasks in a request as follows:

Trigger Options - The tasks that are marked to technicians/groups can be triggered manually or set to auto-trigger when the incident request is created or approved.

 

Add Tasks to Incident

 

 

You can add tasks from templates by clicking Add Tasks from Template.


 

Select the tasks to be associated with the template and click Add Tasks.


Quick Add Tasks

You can add task instantly by clicking Quick Add and typing the task name and clicking enter.

 

 

After adding tasks to the incident template, you can perform the following actions on the tasks:

 

Add Help Cards

In help cards, you can add instructions and offer contextual guidance to users for filling out form fields accurately. When added to request templates, they appear as a collapsible section in the corresponding request forms and details pages.

Within a template, you can configure separate help cards for technicians and requesters.

 Help cards configured in request templates will also appear when users create a maintenance request via those templates.  

Role Required: SDAdmin or HelpDeskConfig

Help Card in the Request Form

Help Card on the Request Details Page

To add help card to a request template,

Note:

Edit/Delete Help Cards

To edit a help card, go to the required template, click Form Customization, and make changes to the instructions. To delete a help card, remove the content and reference files, and save the template.

Associate Checklists 

Checklists allow you to add reminders or to-do lists to a template. Technicians can use these checklists to ensure that all required activities are completed before closing a request.

You can associate up to 5 checklists with an incident template.

You can add checklists to the template in one of the following ways:

Manage Checklists

 

See Also: Checklists

Set Up Form Rules 

Form rules allow you to create request forms that load dynamically based on the data provided by users while creating/editing an incident request. You can define field restrictions and execute predefined actions when the user input matches certain conditions. Form rules enable the usage of the same template for different purposes.

Create Form Rules

 

 

After creating form rules for the incident template, you can perform the following actions:

 

 

List View Operations 

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

You cannot delete or disable default templates.