Service Manager
This is the latest version of the help for Ivanti Service Manager 2018. If you cannot find some of the features described in the help, you may be using an older version of the application. To upgrade the application, click here.To view the help for the latest version of Service Manager, click here
Viewing an Incident
1.Log into the Service Desk Console.
2.Open the Incident workspace. The system displays a list of incidents.
Incident Workspace
3.Open an incident to view its details.
Incident Details
The system displays the following information for each incident:
| Field | Description |
|---|---|
|
Customer |
The name of the person who submitted the incident. The system automatically adds the email address, phone number, and location below the customer name. |
|
Status |
The status of the incident. |
|
Team |
The team to work on the incident. |
|
Owner |
The login ID of the Service Desk Analyst who is assigned to work on this incident. |
|
Summary |
A summary of the incident. Click the search icon |
|
Description |
The description of the incident with relevant details.
NOTE: You must include HTTP:// or HTTPS:// when entering a URL in this field. |
|
Service |
The affected service. |
|
Category |
The category. |
|
Source |
Describes how the incident was submitted. |
|
Impact |
Specifies the impact to the organization, group, or individual. The default value is 3. Impact and urgency together define the priority value: High: Has a major impact on the organization. Medium: Has some effect on the organization but generally not considered a large effect. Low: Does not have much effect on the organization. |
|
Urgency |
Specifies the time appropriateness required. The default value is 3. |
| Declare as Master Incident |
Specifies if this is a master incident. See Working with Master Incidents. |
| Update Related Incident | (Only shown if you check Declare as Master Incident.) Specifies if the system should update any incidents linked with this master incident with the information in this incident. |
| Resolution | Contains the resolution information. |
| Cause Code |
The cause of the incident. Choose from the drop-down list. Configuration Documentation Request Hardware Install Request Installation Linked Problem Other Reference Request Session Reset Software Training |
| Actual Service |
The system automatically fills in the value for this field, although you can change it if you need to. |
| Actual Category |
The system automatically fills in the value for this field, although you can change it if you need to. |
| Attachment | Contains attachments. See Working With Attachments and URLs. |
| Asset | Contains links to other business object (such as a configuration item) to this record. See Linking Incidents. |
| Audit Info | Lists the date and time when the incident was created and the date and time when it was last modified. |
| Journal | Contains comments or notes about this incident. See Adding a Journal Entry to a Business Object. |
to find matching incidents, problems, and Knowledge Base articles. The system displays a list of related items under The system also displays the following tabs:
•Task: See Working with Tasks.
•Master Incident: See Working with Master Incidents.
•External Task: See Using External Tasks.
•Journal: See About Activity History.
•Attachment: To attach a file or URL, see Working With Attachments and URLs.
•Cost Item: See Working with Cost Items.
•Problem: To create or link a problem, see Working with Problems.
•Change: To create or link a change, see Creating a Change Request.
•CI: To create or link a configuration item, see About Creating a Configuration Item.
•Knowledge: To create or link a knowledge article, see Home .
•Escalation Watch
•Audit History
•Survey Results: See Viewing Survey Results.
•Workflow Instance: See Working with Workflow Instances.
•Approval: See Working with Approvals.
•Related Posts: See About the Related Posts Tab.
About Creating an Incident
•Creating an Incident Using a Blank Form
•Creating an Incident by Cloning an Existing Incident
•Creating an Incident By Using a Template
•Applying a Template to an Existing Incident
About Creating Incidents
There are several ways to create an incident:
•By using a blank form in the Incident workspace.
•By cloning an existing incident in the Incident workspace.
•By using a template in the Incident workspace. When you use a template, the system automatically fills in certain information, depending on the template that you use. You can do either of the following:
•Create an incident and then apply the template to it.
•Apply a template to an existing incident.
Creating an Incident Using a Blank Form
1.Log into the Service Desk Console.
2.Open the Incident workspace.
3.From the toolbar, click New Incident. The system opens a blank form.
Creating a New Incident Using a Blank Form
4.Enter information into the fields. See Viewing an Incident. Note the following:
•If the customer is not in the database, you must create a new customer.
•If you are creating the incident for an end user, set the status to active. When the incident is submitted by the user or through email, the status is logged.
5.Click Save.
•The system notifies the end user that the incident has been logged.
•The system notifies both the Service Desk Analyst and the Service Desk Manager about the incident assignment.
6.Click Refresh to view the resolution target values.
Creating an Incident by Cloning an Existing Incident
1.Log into the Service Desk Console.
2.Open the Incident workspace.
3.Open an incident. The system displays the incident details.
4.Select the incident to copy.
5.From the Action Menu, select Form Actions > Clone Incident.
6.Select the incident status from the drop-down list and click OK. The system creates a copy of the incident with the new status.
•The system does not copy or link any child business objects. For example, the system does not attach any journal email records or tasks associated with the original incident to the new incident.
•The system copies the field values exactly, except for the field values that are overridden by the quick action. You can modify the quick action to specify which fields are automatically copied from the original incident.
7.Update other fields as needed.
8.Click Save.
•The system notifies the end user that the incident has been logged.
•The system notifies both the Service Desk Analyst and the Service Desk Manager about the incident assignment.
Creating an Incident By Using a Template
For a list and description of the incident templates, see Default Incident Templates.
1.Log into the Service Desk Console.
2.Open the Incident workspace.
3.In the toolbar, click New Incident > Templates.
4.Select the incident template that matches the incident that you are creating. The system displays an incident form.
5.Enter as much information as you can.
6.Click Save.
•The system notifies the user that the incident has been logged.
•The system notifies both the Service Desk Analyst and the Service Desk Manager about the incident assignment.
Applying a Template to an Existing Incident
When you apply a template to an existing incident, the system overwrites any existing data.
For a list and description of the incident templates, see Default Incident Templates.
1.Log into the Service Desk Console.
2.Open an incident.
3.Do one of the following:
•From the Action Menu, select Templates.
•From the toolbar, click Apply Template.
4.Select a template from the list. The system applies the template to the incident and automatically adds data into the following fields:
•Category
•Service
•Impact
•Urgency
•Summary
5.Enter data in the remaining fields.
6.Click Save.
•The system notifies the end user that the incident has been logged.
•The system notifies both the Service Desk Analyst and the Service Desk Manager about the incident assignment.
Modifying an Incident
You can modify the values in an incident, or update it to correspond to changes in status. The extent to which you can modify an incident depends on your role and edit permissions.
1.Log into the Service Desk Console.
2.Open the Incident workspace.
3.Open an incident. The system displays the incident details.
4.Change the information as needed.
5.Click Save.
Was this article useful?
The topic was:
Inaccurate
Incomplete
Not what I expected
Other
Copyright © 2018, Ivanti. All rights reserved.