Get a first look at what's coming. The Developer Passport Australia Release Preview kicks off March 12. Dive in! 

ITSM

vodnalar26
Mega Contributor

Change requests without sufficient lead time pose a greater risk to the environment and should be documented as such. Risk calculations should consider required lead times, as defined by the organization's change policy: 

- If lead time of 7 days is not met for model = Normal change request, Risk should be set as "High", Impact should be left alone.

- If lead time of 3 days is not met for model = Standard change request, Risk should be set as "Moderate", Impact should be left alone.

1. Disable Risk Condition "Insufficient lead time".

2. Add a new risk condition: "Insufficient lead time - Normal Change" so that if a lead time of 7 days is not met for Normal change requests, the Risk will automatically be set to High, and Impact should be left alone.

3. Add a new risk condition: "Insufficient lead time - Standard Change" so that if a lead time of 3 days is not met for Standard change requests, the Risk will automatically be set to Moderate, and Impact should be left alone.

solution for this scenario.

1 REPLY 1

Dr Atul G- LNG
Tera Patron

what is your question mate?

*************************************************************************************************************
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/dratulgrover [ Connect for 1-1 Session]

****************************************************************************************************************