Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

Risk Assessment Form link is not working

SaiprasannaA
Tera Contributor

In my PDI i have installed "Change Management --Risk Assessment"  and i have created a new risk assessment. Also created the assessment categories along with questions. All questions are here of yes/no and i have defined some value for yes and no, also based on them i have defined the threshold.
But when clicking on the Risk assessment on change form, no action is happening. and nothing is displayed.


SaiprasannaA_0-1751269796397.png

SaiprasannaA_1-1751269859968.pngSaiprasannaA_2-1751269891648.pngSaiprasannaA_3-1751269933958.png

 

1 ACCEPTED SOLUTION

Would you please consider dropping a Kudos or Accepting as solution for the efforts? Thank you very much 🤓

———
/* If my response wasn’t a total disaster ↙️ drop a Kudos or Accept as Solution ↘️ Cheers! */


View solution in original post

9 REPLIES 9

GlideFather
Tera Patron

Hi @SaiprasannaA,

can you also share the change details to review whether the trigger conditions are satisfied?
The "Domain" is a custom field or is it the platform's domain?

TIP: you have classified the Metric name in the top of the form but the same name is visible and readable in the related list in the bottom of the form 😉

———
/* If my response wasn’t a total disaster ↙️ drop a Kudos or Accept as Solution ↘️ Cheers! */


Ours is domain separation instance. so i created a new domain, this risk should be applicable only for that particular domain.

SaiprasannaA_0-1751280633539.pngSaiprasannaA_1-1751280661383.png

 

@SaiprasannaA I have not been working with domains for years and even when I did I was not the most knowledgeable in this topic, however is the Domain defined in the form because I can see it in the trigger condition in the original post.

Can you ensure that the conditions are right? You can modify the conditions to something else and more simple - for example: "Impact is 2" then try to test it and you will see if it is a problem of the trigger or anything else

———
/* If my response wasn’t a total disaster ↙️ drop a Kudos or Accept as Solution ↘️ Cheers! */


Thanks for the response i have tried correcting the conditions it worked.