Incident fields and their behaviour
Field Label | Field Type | Field Behaviour | Purpose |
|---|---|---|---|
Assignee | Reference (User table) |
| This is the individual responsible for the resolution of the incident. |
Assignment group | Reference (Group table) |
| this is the group that is responsible for the completion of the incident. This is the This is often set via the Sofi classifier automatically. |
Attached knowledge | Reference (Knowledge table) |
| This is used to understand what knowledge was used for an incident. |
Change required | Multiple reference (Change table) |
| These are the changes that are related to an incident. Once one of these have been completed, it will automatically resolve the incident and update the incident in various other fields as the process dictates. |
Classification | Reference (Classification table) |
| This is the classification that can be selected from an incident that can help for reporting or otherwise. This is often set via the Sofi classifier automatically. |
Client journal | Journal | | This is the method to communicate with the client or the client to communicate with the service desk via an incident. When a knowledge article is attached from Sofi, it will automatically enter this field. |
Closed at | Date and time |
| This is automatically set based on the date and time that the incident is closed. |
Closed by | Reference (User table) |
| This is automatically set based on the person that closes the incident. |
Collaborator | Multiple reference (User table) |
| These are any users who may be assisting in the completion of the task or want / need to be kept up to date as to the progress of the incident. This is also used to assist with the "incidents I'm following" menu item. |
Description | String | | Extra information that can be provided as part of the incident. |
String |
| This is the email that should be used as a contact mechanism for this incident. This can be different to the one on the user's record, to help cater for situations where the incident is about their email or another mechanism is required to contact the user. | |
First contact resolved | Boolean (Radio button) |
| |
Follower | Multiple reference (User table) | | This is the list of the followers for an incident. This is also used to assist with the "incidents I'm following" menu item. |
Impact | Choice Values:
|
| In combination with urgency, this determines the priority of an incident. |
Location | Reference (Location table) |
| This is the location that the incident is for, which can be different to the requestor's and requested for's location. |
Major incident | Boolean (Radio button) |
| This highlights whether or not the incident is a major incident, which means it will follow the major incident process as detailed in the Incident management automation and functionality |
Major incident follower | Multiple reference (User table) | | These are the users who wish for extra visibility of an incident, although no notifications are set up out of the box in regards to it. This is also used to assist with the "incidents I'm following" menu item. |
Major incident journal | Journal |
| This assists with communicating to all related incidents related to a major incident, as it will assist in updating all related incidents at once. |
Major incident manager | Reference (User table) |
| This is the user that is considered responsible of the resolution of a major incident and helps manage the process. |
Major incident review | HTML | | This field is used as the basis of any major incident knowledge article created from an incident. It should hold the details of the major incident to highlight what is occurring. |
Name of person | String |
| Holds the name of the requested for / requestor if they don't have an account. |
Person has no account | Boolean | | This is if the requestor / requested for does not have an account in the system and the name needs to be tracked |
Phone | String |
| This is the phone number that should be used as a contact mechanism for this incident. This can be different to the one on the user's record, to help cater for situations where the incident is about their phone or another mechanism is required to contact the user. |
Priority | Choice Values:
|
| The priority of an incident used for reporting purposes, conditional logic purposes and SLA purposes. |
Reference Number | Auto sequence (Prefix is INC) |
| Used as a unique reference to an incident and its display value |
Related configuration items | Multiple reference (CMDB table) | | Used to highlight any configuration items related to an incident. |
Related incidents | Multiple reference (Incident table) |
| These are the incidents related to the current incident, which will receive any journal updates and status updates from the focus record. |
Related major incident | Reference (Incident table) |
| This is the parent incident to an Incident. This incident will automatically update the focus incident in various fields as the process dictates. |
Related problem | Multiple reference (Problem table) |
| These are the problems that are related to an incident. Once one of these have been resolved, it will automatically resolve the incident and update the incident in various other fields as the process dictates. |
Requested for | Reference (User table) |
| This holds the person who the incident is requested for. |
Requestor | Reference (User table) |
| This holds the person who is requesting the incident, but does not necessarily mean it has been raised for them. |
Resolution item | Reference (Resolution item table) |
| This runs automation (when desired through script), but helps train sofi to know how to resolve tickets. |
Resolution method | Choice Values:
|
| This is used to assist in training sofi, in assisting in zero contact resolution. |
Resolution notes | String |
| Used to provide information as to how an incident was resolved. Also when creating a non major incident knowledge article from an incident, it will be part of the generated knowledge article. |
Resolved at | Date and time |
| This is automatically set based on the date and time that the incident is resolved. |
Resolved by | Reference (User table) |
| This is automatically set based on the person that resolves the incident. |
Resulting knowledge | Reference (Knowledge table) |
| This is used to hold the knowledge article that was created from the incident. Once this field has been set, users can automatically be redirected to it based on a button on the incident form when this has been populated. |
Service | Reference (CMDB Service table) | | This is the service s that can be selected from an incident that can help for reporting or otherwise. This is often set via the Sofi classifier automatically. |
Short description | String |
| The short description is used as the primary classifier source for Sofi. |
SLA list | Multiple reference (SLA table) | | The list of SLA's that are related to the incident. |
SLA status | String |
| This highlights the status of the primary SLA against a record, to ensure that the incident is being updated in a timely matter. |
Sofi conversation ID | String |
| Used to hold the Sofi conversation ID, which is used by the Sofi continuation point dialog manager element. |
Source | Choice Values:
|
| Automatically set from an interaction or from the method it was created from |
Source interaction | Reference (Interaction table) |
| This holds the interaction record that an incident was created from, assuming it was initially created from an interaction. |
Subtasks | Multiple reference (Incident task table) | | These are the incident tasks that have been created from and are related to an incident. |
Urgency | Choice Values:
|
| In combination with impact, this determines the priority of an incident. |
Work journal | Journal | | This is the method to communicate internally about an incident that should not be visible to the client (unless they have the appropriate roles). |
Other fields hidden from form and un-used
The below are fields that come off one of the tables incident \ extend from, which it does not use or have on the form. Some will have some behaviours tied to them (due to existing on the Work table), but some will have nothing tied to it. As a result, you can use them, but they will likely have no functionality tied to them. Note that there are other fields, but they are not recommended to be used due to the potential impact.
Field Label | Field type | Field behaviour | Purpose |
|---|---|---|---|
Approver | Multiple reference (User table) | | No approval process exists for incidents so this field currently has no functionality tied to it. |
Parent | Reference (Work table) |
| Not used for any purpose at the moment, but can be used in the future. |
Requested by date | Date and time | | Not currently used, but easily added to the form and used. |