investigation and analysis of a problem
An unresolved problem can cause different system malfunctions that users register as incidents.
To create new caused incidents directly from the problem form, follow the steps below:
The filter condition of the Related Lists tab defines the current problem as an incident parent.
You can also assign a problem as parent to registered Incidents with the steps below:
When logging the problem, it is important to assess the time spent by users on resolving it.
To register the time you spent on a particular problem, create new Time Card with the steps below:
Users can add Time Cards on their own right from the problem form.
Field | Description |
---|---|
Number | Automatically filled with the unique identificator of the TMCXXXXXXX format. |
Employee | Automatically filled with the user's name. |
Company | Automatically filled with the users' company name. |
Time Spent Category | Specifies the time category that user spent on resolving the problem. It is necessary when analysing working time and schedules. (?) |
Related Task | Automatically filled with the issue from where the Time Card has been created. |
Comment | Add an additional information if it is needed. |
Date | Determine the date when a user worked on the problem. Automatically filled with the current date. |
Time Spent, hours | Specify the duration of user's time spent. |
To Invoice | Turn this checkbox active to mark the need for billing. |
When investigating the issue, in case of detection relations or dependencies with other problems register these relationships with the following features:
The system records every change on the Problem record with the Activities available on the Notes tab of the related information area. These activities collect all information about record changes, such as date, time, changed field and its previous value, and a user's name who apllied these changes.
A good practice is to record an additional information when working on the problem. Users can make notes and comments with
All saved notes and comments are available as Activities on the Notes tab and have colored marks:
In case you cannot resolve a problem, create a Known Error record in the KEDB (Known Error Database) and define with it a workaround suited for problem.
To create a Known Error follow the steps below:
Fill in the Known Error form;
On the problem form, a created Known Error is available (records) in the Known Error field on the Related Records tab.
A created Known Error automatically specifies the Known Error field with its number on the Related Records tab of the problem form. (?)
Field | Description |
---|---|
Number | Automatically filled with the unique identificator of the KEXXXXXXX format. |
Name | Enter the Known Error name. |
Service | Select a Service from the list. Automatically filled when creating a KE from the particular problem. |
Content DB | Defines a content type of the Knowledge Database. Automatically filled with the KEDB value. |
Content Category | Automatically filled with the Known Error value. |
Content Item Class | Automatically filled with the Known Error value. |
Workaround | Describe a workaround to the existing and impossible to resolving problem. |
State | Specify the Known Error current state selecting one of the possible values:
|
Problem | Automatically filled with the problem number and subject when creating a KE from the particular Problem. |
Incidents | Assign related Incidents to a new Known Error. Automatically filled wih the Incident records when creating a KE from the particular Problem. |
Created by | Automatically filled with the User who has created this Known Error record. |
Updated by | Automatically filled with the User who has updated this Known Error record. |
Description | |
Metainfo | Type here an additional information |
investigation and analysis of a problem