Service Desk Practitioners Forum
cancel
Showing results for 
Search instead for 
Did you mean: 

When change category is Urgent Change,The Change must related a Incident which cause this change

SOLVED
Go to solution
Highlighted
Judy Sun
Occasional Contributor

When change category is Urgent Change,The Change must related a Incident which cause this change

In Change Process,When change category is Urgent Change,The Change must related a Incident which cause this change. Can we realize it in OVSD change process?
2 REPLIES
Robert S. Falko
Honored Contributor
Solution

Re: When change category is Urgent Change,The Change must related a Incident which cause this change

Try this:

1) You must create the change from an incident, using sd_dataform, in which you pass the change category as a parameter. You'll need to create a UI rule to do this, perhaps triggered by a button on the form.

2) Limit the ability to manually select the category Urgent Change. You should be able to do this if you are on SP 17 or later. (I wonder if you can simply block the category, and still use it via sd_dataform?).

I do not think you can enforce this business rule by testing for the existence of a relation between a change and an incident, unless you develop the logic in an external program using the Web API.

-Josh

Re: When change category is Urgent Change,The Change must related a Incident which cause this change

Hi Josh,

The idea of blocking the code wouldn't work. at the moment you open the ticket it would ask you to change the value since it doesn't exist anymore.

Lawrence
we have been where you wanna go..
//Add this to "OnDomLoad" event