Overview
The Help Desk template supports a typical Help Desk
environment in which issues or requests are reported by
end users and the Help Desk team resolves the issues or
processes requests.
Data Record
The data record contains the following fields. Note that
you can customize the database by adding to or removing
fields, or changing any pulldown menu values. Field names
with an asterisk are required by the system and cannot
be removed from the data record.
PRN* |
Numeric record identifier. Assigned
at the time the record is created. |
Title |
A one line text summary of the
problem or request. Set at the time the record is created. |
Product* |
Identifies the product for which the
record has been reported. Set at the time the
record is created. |
Component |
Identifies the component for which the
record has been reported. Values displayed in this field
depend on the value selected for the Product field.
Set at the time the
record is created. |
Platform |
Describes the hardware or
software platform where the problem occurs. Examples
are the operating system (e.g. Windows 2000). Set at the time
the record is created. |
Request Type |
Classifies the record. Some of the
possible values are: Bug / Issue, Enhancement, Equipment
Request, Feedback. Set at the time the record
is created. |
Severity |
Describes how serious the
problem is. Set at the time the record is
created. |
Description |
Full description of the
problem. Ideally describes the nature of the
problem and how to reproduce the behavior.
Set at the time the record is created. |
Reported By* |
Name of the user that
reported the record. Initially set to the
name of the current user logged in. Set at
the time the record is created. |
Date Reported |
The date the record was
created. Automatically initialized, and set
at the time the record is created. |
Workaround |
Describes how to work
around the reported problem. Set at the time
the record is created. |
Pending Issues |
Describes what information or tasks are
needed before a record can continue to be processed.
Set by the Help Desk Engineer if issues arise that keep the record
from being processed. |
Status* |
Current state of the
record. Changes as the record is
processed through the workflow. |
Assigned To* |
User the record is currently
assigned to for processing. Set either manually
or automatically during processing of the
workflow. |
Est. Close Date |
Date when the issue or request
is expected to be resolved. Set by the Help Desk Engineer
when deciding how to process the record.
|
Priority |
Describes the relative importance
of handling this record compared to other records
entered in the system. |
Close Date |
Date when the record
was closed. Set by Help Desk when issue or request has
been resolved. Automatically
initialized to the current date/time. |
Close Detail |
Describes the details about how the
issue or request was resolved.
Set by the Help Desk when the issue or request has been
resolved. |
Deleted* |
Denotes whether the record has been deleted. |
Dependent Pulldowns
The pulldown field Component is dependent on the pulldown
field called Product, allowing the Component field to only
display those values that correspond to the Product selected.
The examples below illustrate the purpose of Dependent Pulldowns.
Example 1
When "Hardware" is selected in the Product field, the Component
field displays the following option menu items:
Computer
Modem
Monitor
Other
Printer
Example 2
When "Software" is selected for the Product field, the Component
field displays the following option menu items:
Our Browser
Our Database
Our Email
Other
Details on setting up dependencies between pulldown fields can be found
in the
Customizing Pulldown
Dependencies section of the Admin Guide.
Workflow
It is assumed that records will be processed and moved through the workflow
process by using the Task operation. The workflow implemented by the
Help Desk template is as follows:
- State 1 - Reported
It is assumed that each Help Desk Engineer is assigned to a particular
product or area of expertise. When a record is created, it is set to the state
Reported, and assigned to a particular Help Desk Engineer
based on the Product selected in the record.
Each Help Desk Engineer
reviews the incoming records and
decides how to process each using a list of possible workflow paths.
The Help Desk Engineer can choose one of the
following:
- Begin processing a record by selecting the transition called
Start Processing Request. The Description field
is presented for the Help Desk Engineer's reference. The
Help Desk Engineer must enter an Estimated Close Date and
can optionally set the Priority of the request. This transition
will keep the record assigned to the Help Desk Engineer and
place the record in the In Process state.
- Close the record by selecting the transition called Close.
The Description field
is presented for the Help Desk Engineer's reference. This
transition will place the record in the Closed state and assign it to TBD
("no one" since this record will not be processed any further).
The Help Desk Engineer
will be required to enter a reason
the record was closed in the Close Detail field. The Close Date will be updated
automatically.
- Delay processing of the request by selecting the Hold Request
transition. The Description field is presented for the Help Desk
Engineer's reference. The Help Desk Engineer is required to enter a reason for the
delay in the Pending Issues field and an Estimated Close Date. It is
optional to set the Priority for the record. This transition will place the
record in the On Hold state, but will still be assigned to the Help Desk
Engineer.
This is implemented by:
Workflow Properties
- Defining Reported as the Default Add
State when a record is added
- Assigning a Help Desk Engineer as the manager for
the Reported and On Hold states for each Product
e.g. Help Desk Engineer One (help_one) is the manager
for the Reported and On Hold states for the Hardware Product
Transitions
- Defining a transition to move a record to the In Process and
On Hold states where the assignee is <Same Assignee>.
- Defining transitions to move a record to the Closed state
where the assignee is TBD.
Task Fields
- Configuring Description (read only), Est. Close Date (required)
and Priority (optional) to be presented during
the task operation for the transition to the In Process state.
- Configuring Description (read only), Close Detail (required) and Close Date (read only and initialized)
to be presented
during the task operation for the transition to the Closed state.
- Configuring Description (read only), Pending Issues (required),
Est. Close Date (required)
and Priority (optional) to be presented during
the task operation for the transition to the On Hold state.
- State 2 - In Process
The Help Desk Engineer assigned to the record
attempts to resolve the issue or request, then chooses
one of the following transitions:
- If the issue is resolved, the Help Desk Engineer
can close the issue by selecting the
transition Close. The Description field is
presented for the Help Desk Engineer's reference. This
transition will place the record in the Closed state and
assign it to TBD ("no one" since this record will not be
processed any further). The Help Desk Engineer
will be required to enter a reason the record was closed
in the Close Detail field. The Close Date will be updated
automatically.
- If the issue has not been resolved and the Help
Desk Engineer needs to escalate the issue to a manager
for troubleshooting assistance, the Escalate
transition will be selected. The Description field is
presented for the Help Desk Engineer's reference.
The Help Desk Engineer is required to enter the reason for
the escalation in the Pending Comments field. This will
place the record in the Escalated state and will assign it
to the Help Desk Manager.
- If the issue cannot be processed until a later (e.g. because
more information is needed or there is a delay to receive equipment
needed to resolve the issue), the Help Desk Engineer can select
the Hold Request transition. The Description field is
presented for the Help Desk Engineer's reference. The
Help Desk Engineer is required to enter a reason for the
delay in the Pending Issues field and an Estimated Close Date. It is
optional to set the Priority for the record. This transition will place the
record in the On Hold state, but will still be assigned to the Help Desk
Engineer.
This is implemented by:
Workflow Properties
- Defining Help Desk Manager (help_mgr)
as the manager for the Escalated state
Transitions
- Defining a transition to move a record to the Closed state
where the assignee is TBD.
- Defining a transition to move a record to the On Hold state
where the assignee is <Same Assignee>.
- Defining a transition to move a record to the
Escalated state where the assignee is the manager of that state
Task Fields
- Configuring Description (read only), Close Detail (required) and Close Date (read only and initialized)
to be presented
during the task operation for the transition to the Closed state.
- Configuring Description (read only), Pending Issues (required),
Est. Close Date (required)
and Priority (optional) to be presented during
the task operation for the transition to the On Hold state.
- Configuring Description (read only) and Pending Issues (required)
to be presented during the task operation for the transition to
the Escalated state.
- State 3 - Escalated
The Help Desk Manager (help_mgr) decides how to proceed with the
issue:
- The issue can be sent back to the Help Desk Engineer
by using the De-escalate transition. The Description
field will be provided for help_mgr's reference. Comments to
aid the Help Desk Engineer to resolve the issue must be
entered into the Pending Issues field. Optionally, the Priority
of the record can be updated. This will place the record back
into the In Process state and assign it to the Help Desk Engineer
who worked on the record when it was previously in that state.
- The issue can be closed by using the Close
transition. The Description field is
presented for reference purposes. This
transition will place the record in the Closed state and
assign it to TBD ("no one" since this record will not be
processed any further). help_mgr
will be required to enter a reason the record was closed
in the Close Detail field. The Close Date will be updated
automatically.
This is implemented by:
Transitions
- Defining a transition to move a record to the
In Process state where the assignee is
<Last Assignee for New State>
- Defining a transition to move a record
to the Closed state where the assignee is TBD
Task Fields
- Configuring the Description (read only), Pending Issues (required), Priority (optional)
to be presented during the Task operation for the transition to the
In Process state.
- Configuring the Description (read only), Close Date (read only, initialized),
and Close Detail (required) fields to be presented for the transition to the
Closed state.
- State 5 - On Hold
Processing was stopped for the records in this state. The Help Desk Engineer
can resume processing of a record using the Resume Processing
transition. The Description field will be provided for reference purposes and
the Help Desk Engineer will have the option to update the Estimated
Close Date and Priority fields. This will place the record in the In Process
state and will remain assigned to the Help Desk Engineer.
The Help Desk Engineer can close the issue by using the Close
transition. The Description field is
presented for reference purposes. This
transition will place the record in the Closed state and
assign it to TBD ("no one" since this record will not be
processed any further). The Help Desk Engineer
will be required to enter a reason the record was closed
in the Close Detail field. The Close Date will be updated
automatically.
This is implemented by:
Transitions
- Defining a transition to move a record to the
In Process state with New Assignee set to
<Same Assignee>
- Defining a transition to move a record to the
Closed state and assigned to TBD
Task Fields
- Configuring the Description (read only), Est. Close Date (optional), Priority (optional)
to be presented during the Task operation for the transition to the
In Process state.
- Configuring the Description (read only), Close Date (read only, initialized),
and Close Detail (required) fields to be presented for the transition to the
Closed state.
- State 6 - Closed
Processing on these records has been completed.
Sample Saved Charts
A set of sample saved charts are included in this template.
Click here
to see details of these sample metrics.
Email Notification
The Help Desk template is set up to notify users as
follows:
On Add or Delete of a Record
The current assignee, the manager for
the current state, and the reporter of the record are notified
On Change of State to Inactive
The user who reported the record is notified when a record is moved to
a state where processing has stopped (any state included in the
Inactive state group: Closed or On Hold)
On Change of Assignment
Both the current assignee and the manager of
the current state of the record are notified
Security
The Help Desk template assumes a very simple security
model reflecting a workgroup situation where all users are able
to see any record. This is implemented by setting
Enable Record Visibility option under General
Preferences in the Administration Task page to
No.
In addition, the privileges related to editing the field of the records have
been removed from users that are not managers or Admin.
With this configuration, users can rely on the Task operation to move records
through the workflow. This can be changed within the
User Administration section of the Admin page.