My Requirement is that when a user create a special handling contact incident priority should be default 1. In our org. we set incident priority by default 2 for other users.
if someone have a spell code for usp_special_handling contact by default priority 1.
Please help me
I haven't looked at this, but could the Priority Calculation Matrix work in this case?
There is an "Increase Urgency" field against the Special Handling Contacts.
If Urgency is increased, it may be a useful way to set the Priority. (Impact and Urgency determine Priority).
Or can this Contact be assigned to their Own Service Contract with its own Events that determine Priority?
I'm not sure, but there would seem to be other options before going into SPL code.
Thanks for reply, Actually we are not using Priority Calculation in our organization. Can above mention thing done by other way.
like with Site defend condition. Events or spell
Please provide me any solution
Sure, you could go with an Event or an Auto-Event that checks Conditions checks for the Contact and sets the Priority accordingly.
One good way may be to give these users with Special Handling conditions their own Service Contact.
Service Contracts - CA Service Management - 17.1 - CA Technologies Documentation
- - -
A Service Contract also maps Service Types to common reference fields on a ticket, such as Priority and Asset. This mapping associates Service Types with attributes of a ticket. For example, an Organization’s contract can assign Service Types to each of the five Priority objects. When a ticket is created with a certain priority, the mapped Service Type is applied.
Note - the customer does not need to have a physical Service Contract, nor even be aware of the CA ITSM Service Contract. It would be for your own management purposes, like many other fields.
(You can also go down the SPL route for unique one-off situations, but in general you should avoid this route when there are already out-of-the-box ways of doing things. See here to answer a different question with SPL code, as both an example of what can be done, and the complexity which might be the reason not to do it. SPL is a great resource, but it turns part of your system into "out of scope for Support" and introduces complexity.)