Manage Incidents
  • 10 Jan 2025
  • 3 Minutes to read
  • PDF

Manage Incidents

  • PDF

Article summary

Managed Service Provider (MSP) customers can manage incidents logged by them based on tenant-specific configurations.

With the ability to view all incident details on a single page, users can efficiently manage and resolve issues. The "Manage Incident Details" page in Apex provides analysts with comprehensive information about specific incidents, including their status, requester details, history, and more, enabling faster and more effective resolution.

General

The General tab of the "Manage Incident" page displays essential details about the incident, such as the tenant it belongs to, the requestor's name, the medium, the source, and more. Users can view or edit these details as the incident progresses.

The table below provides an overview of the fields available in the General tab:

FieldDescription
Classification 
TenantSelect the name of the Tenant. For example, MSP-Company 1, MSP-Company 2 etc. A Tenant is similar to a department within an organization that provides support related to an IT or a facility. 
RequestorSpecify the name of the requestor who raised the Incident is displayed.  It is displayed from the logged in  username.
Note

Values in the Requestor field are displayed as per the selected Tenant.

Logged ByChoose the name of the user who is logs the Incident. 
Classification
Select the appropriate option from the classification Pop-up window which provides various categories.
classificaytion
Source Select the origin of the Incident being logged. Options available are: User, Event, Incident, Change, Problem, Others.
CategoryFind and select the appropriate category to which the Incident belongs to from the category list. Refer to the screenshot below.
category(1)
SiteSpecify the location or facility associated with the incident.
Pending ReasonProvides additional context as to why the Incident is in pending status. 
TerritorySpecify the field that represents the geographical or business region associated with an incident.
LocationChoose the location from which the requestor has raised the Incident is displayed.
Club/StoreSelect the Club or Store to which incidents can be organized and tracked depending on the tenant’s operational structure.
Sent to ProcurementChoose the option to forward the incident to procurement team for further action. 
Type of TicketChoose the type of ticket for easy resolution. 
AttachmentUpload an attachment for additional information. 
Major IncidentEnable the button if the Incident needs to be proposed as a Major Incident. When the incident is proposed as a Major Incident, it is transferred to the Approver for the approval process.
When enabled, the following window is displayed. For more information on the details to be input, refer the table below in Major Incident.


CustomerSpecify the Customer for the Incident. 
Prioritization
ImpactImpact defines the enormity of the situation and the extent of consequence related to the incident. The options available are critical, high, low, and medium.
UrgencyThis field represents the urgency-based factor for Incident. Options available are:
Critical, High, Low, Medium.
PriorityPriority defines the precedence in which a particular Incident should be addressed. The options available are P1, P2, P3, P4, and P5.


Major Incident

FieldDescription
General
TopicSpecify the topic for initiating the major incident. 
MIM Team MembersSelect the team members of the Major Incident Team. 
Create Problem Record on Incident resolutionEnable this feature if a problem record needs to be created for this incident resolution. 
Generate MeetingClick the button to generate a meeting with the MIM team members. 
Root Cause
What is the nature of the Incident?Select the nature of the incident from the dropdown menu. 
What specific symptoms or issues are being observed?Provide details of the symptoms or issues that are observed as part of this incident. 
What are the cause of the Incident?Specify the observed cause of the incident. 
Type of OccurrenceSpecify if it is a first time or repeated occurrence. 
Is there a workaround in place, and is it effective?Choose yes or no if there is a workaround for the issue. 
What is the criticality of the affected systems or services?Specify the criticality of the incident as low, medium, high etc. 
What actions have been taken so far?Provide details of the actions taken for resolution of the issue. 
Preventive Action
ActionProvide details of the action taken for prevention of the issue. 
OwnerProvide the owner details for the issue. 
Due DateEnter the due date for resolution of the issue. 
Status Select the status of the major incident. 



Was this article helpful?

Changing your password will log you out immediately. Use the new password to log back in.
First name must have atleast 2 characters. Numbers and special characters are not allowed.
Last name must have atleast 1 characters. Numbers and special characters are not allowed.
Enter a valid email
Enter a valid password
Your profile has been successfully updated.