Priority Calculation
Priority calculation is a predefined set of values that automatically set Priority, Urgency, and Impact fields on problems and incidents.
When you install this version of CA Service Desk Manager, a Default priority calculation automatically manages ticket values. You can modify the Default priority calculation settings, or create additional priority calculations to manage incidents or problems. For multi-tenancy, you or the tenants can create additional priority calculations with specific settings for each tenant.
In the priority calculation, you define the outcome based on business scenarios to make the level of importance and ticket handling more consistent. Users can override some settings, but they no longer can set the Priority on the ticket because this value is data-driven.
Note: If you migrated from a previous version, priority calculation is disabled by default. For information about how to enable priority calculation or retain your customizations, see the Implementation Guide.
When an analyst opens an incident or problem, the system automatically uses an active priority calculation and ticket values to generate Priority, Urgency, and Impact settings. The settings are based on one or more of the following fields:
■ Urgency
■ Impact
■ Affected End User
■ Incident or problem Area
■ Open Date
■ Affected Service
Analysts can override Urgency and Impact values as necessary. Depending on how you configure Options Manager, employees can only override incident Urgency values when the urgency_on_employee option is installed. When the Capture Reason flag is enabled and users override Urgency or Impact values and click Save, the Escalate Detail page appears to let users describe a reason for the change.
All ticket priority calculations, manual overrides, and reason information appear in the New Activity Log. If no priority calculation adjustments occur, the system does not create an activity log entry.
How Priority Calculation Manages Ticket Values
The system adjusts problem and incident values based on active priority calculation settings to assist Analysts in handling tickets more effectively. The following table summarizes how priority calculation changes fields based on the priority calculation and user actions for problems, incidents, web service, email, and the Text API:
Action Automatic Field Changes Description
User changes Affected Service Impact
Priority The system evaluates the Service Impact value on the CI of type Service to calculate the new Impact value. The CIs of type Service are defined as CIs with have their class defined in the Enterprise Service family. If the open date of the ticket is within the blackout window time frame, the system increments a new Impact value based on the Impact Increment field. The system only replaces the Impact value when the new value is greater than the initial Impact value.
User changes Incident Area Urgency The Urgency value changes only when the new value is greater than the default value.
User changes Incident Area and Affected End User Urgency
Priority If the user sets the Incident Area field first, the Urgency value changes after the user sets the Affected End User. The priority calculation sets the Priority.
User changes Urgency and Impact Priority
Impact The system evaluates the Service Impact value on the CI of type Service to calculate the new Impact value. If the open date of the ticket is within a time defined by a blackout window, the system increments a new Impact value based on the Impact Increment field. The system only replaces the Impact value when the new value is greater than the initial Impact value.
If the Administrator sets Capture Reason, the user must to provide a reason for the modification.
If the user changes the Urgency or Impact values, these values remain the same throughout entire ticket creation or ticket update unless the user modifies them again. However, the system can update the overridden values for Urgency or Impact the next time the user updates the ticket.
After the system adjusts Urgency and Impact, the priority calculation sets the Priority value.
User selects New Incident based on the Knowledge Document and system has overrides for Knowledge Documents (see page 284) Impact
Urgency The system always uses the Knowledge Document or knowledge solution values irrespective of whether the values are greater than or lesser than default priority calculation values.
For example, if a priority calculation has an Impact value of 3-Single Group and Urgency value of 3-Quickly, and Knowledge Documents have an Impact value of 2-Multiple Groups and Urgency value of 4-Very Quickly, the system applies the values from the Knowledge Document to the incident. The priority value always derives from priority calculation.
User accepts Knowledge Document as solution to problem or incident Impact
Urgency The system uses the values from the Kn
Priority Calculation Priority calculation is a predefined set of values that automatically set Priority, Urgency, and Impact fields on problems and incidents. When you install this version of CA Service Desk Manager, a Default priority calculation automatically manages ticket values. You can modify the Default priority calculation settings, or create additional priority calculations to manage incidents or problems. For multi-tenancy, you or the tenants can create additional priority calculations with specific settings for each tenant. In the priority calculation, you define the outcome based on business scenarios to make the level of importance and ticket handling more consistent. Users can override some settings, but they no longer can set the Priority on the ticket because this value is data-driven. Note: If you migrated from a previous version, priority calculation is disabled by default. For information about how to enable priority calculation or retain your customizations, see the Implementation Guide. When an analyst opens an incident or problem, the system automatically uses an active priority calculation and ticket values to generate Priority, Urgency, and Impact settings. The settings are based on one or more of the following fields: ■ Urgency ■ Impact ■ Affected End User ■ Incident or problem Area ■ Open Date ■ Affected Service Analysts can override Urgency and Impact values as necessary. Depending on how you configure Options Manager, employees can only override incident Urgency values when the urgency_on_employee option is installed. When the Capture Reason flag is enabled and users override Urgency or Impact values and click Save, the Escalate Detail page appears to let users describe a reason for the change. All ticket priority calculations, manual overrides, and reason information appear in the New Activity Log. If no priority calculation adjustments occur, the system does not create an activity log entry.How Priority Calculation Manages Ticket ValuesThe system adjusts problem and incident values based on active priority calculation settings to assist Analysts in handling tickets more effectively. The following table summarizes how priority calculation changes fields based on the priority calculation and user actions for problems, incidents, web service, email, and the Text API:Action Automatic Field Changes Description User changes Affected Service Impact Priority The system evaluates the Service Impact value on the CI of type Service to calculate the new Impact value. The CIs of type Service are defined as CIs with have their class defined in the Enterprise Service family. If the open date of the ticket is within the blackout window time frame, the system increments a new Impact value based on the Impact Increment field. The system only replaces the Impact value when the new value is greater than the initial Impact value. User changes Incident Area Urgency The Urgency value changes only when the new value is greater than the default value. User changes Incident Area and Affected End User Urgency Priority If the user sets the Incident Area field first, the Urgency value changes after the user sets the Affected End User. The priority calculation sets the Priority. User changes Urgency and Impact Priority Impact The system evaluates the Service Impact value on the CI of type Service to calculate the new Impact value. If the open date of the ticket is within a time defined by a blackout window, the system increments a new Impact value based on the Impact Increment field. The system only replaces the Impact value when the new value is greater than the initial Impact value. If the Administrator sets Capture Reason, the user must to provide a reason for the modification. If the user changes the Urgency or Impact values, these values remain the same throughout entire ticket creation or ticket update unless the user modifies them again. However, the system can update the overridden values for Urgency or Impact the next time the user updates the ticket. After the system adjusts Urgency and Impact, the priority calculation sets the Priority value. User selects New Incident based on the Knowledge Document and system has overrides for Knowledge Documents (see page 284) Impact Urgency The system always uses the Knowledge Document or knowledge solution values irrespective of whether the values are greater than or lesser than default priority calculation values. For example, if a priority calculation has an Impact value of 3-Single Group and Urgency value of 3-Quickly, and Knowledge Documents have an Impact value of 2-Multiple Groups and Urgency value of 4-Very Quickly, the system applies the values from the Knowledge Document to the incident. The priority value always derives from priority calculation. User accepts Knowledge Document as solution to problem or incident Impact Urgency The system uses the values from the Kn
การแปล กรุณารอสักครู่..