Ticket Priority Rules

If the system displays the Ticket Priority Rules icon on the tile containing the selected vendor partner's name, then you can access the Ticket Priority Rules page for the selected vendor partner.

You use service ticket priority rules to define how the system should assign a service call's Service description in XSM when a service call is created in e-automate and update a service call's Incident Status in XSM when a service call is updated in e-automate.

When a new service call is created in e-automate, the system creates a matching service call in XSM.  On the Call type mappings tab, you map each e-automate Call type to each corresponding Service code description in XSM.  If one e-automate Call type may have multiple corresponding Service code descriptions in XSM, you create one mapping for each combination and list the mappings on the Call type mappings tab in the order you want the system to assign the Service code description if it is available for the call in XSM.  When you create a service call in e-automate and assign a Call type to the call, the system creates a matching service call in XSM and assigns the first available Service code to that call that you mapped to the Call type on the Call type mappings tab.

When a service call's Call type and/or Call status is updated in e-automate, the system updates the Incident Status and/or Service description of the matching call in XSM.  On the Workflow tab, you define for each of your e-automate Call types the progression of Incident Statuses that can be assigned to the call in XSM as the call is updated, from the time the call is created to the time the call is closed or cancelled.  The Incident Statuses you associate with a given e-automate Call type on the Workflow tab identify the only possible options the system can assign to the call in XSM when the matching call in e-automate is updated.  If a call's Call type is changed in e-automate, the system can only use an Incident Status associated with the new Call Type when updating the matching call in XSM.

On the Call status mappings tab, you map each e-automate Call status to each corresponding Incident Status in XSM.  If one e-automate Call status may have multiple corresponding Incident Statuses in XSM, you create one mapping for each combination and list the mappings on the Call status mappings tab in the order you want the system to assign the Incident Status if it is available for the call in XSM.  When a service call's Call Status is updated in e-automate, the system updates the Incident Status of the matching call in XSM using the first available Incident Status that can be assigned based on the combination of the workflow associated with the call's Call type and the Call statuses mapped on the Call status mappings tab.
Note: The Call status you assign to the call in e-automate must have a Call type that can be assigned to the call in XSM that is defined as part of the call type's workflow on the Workflow tab; otherwise, the system will not update the call's Incident Status in XSM when the call's Call status is updated in e-automate.

To view a sample ticket priority mapping scenario, see the Ticket Priority Rules Example topic.

Defining Call Type Mapping Ticket Priority Rules

Defining Workflow Rules

Defining Call Status Mapping Ticket Priority Rules