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.

Description Field Not Showing as Mandatory in SOW View for Standard Change – Need Help

lakshmi9
Tera Contributor

 

  • I’m working on a requirement where the Description field should be mandatory for Standard Change Requests, but only when the State is 'New' and the view is SOW.
  • I tried implementing this using a UI Policy, but it didn’t work in the SOW view. I then attempted it using a client Script, and it works fine in the Default view, but not in SOW.
  • The field is present in the SOW form layout, so I’m not sure why the mandatory condition isn’t being applied.

If anyone has faced a similar issue or could kindly guide me on how to achieve this, I’d really appreciate your help.

3 ACCEPTED SOLUTIONS

Hi @lakshmi9 ,

Please check and confirm if you have selected for a specific view
because it will work.

SD_Chandan_0-1752657829298.pngSD_Chandan_1-1752657842385.pngSD_Chandan_2-1752657846707.png

Mark it helpful if this helps you to understand. Accept solution if this give you the answer





Thank you
Chandan

View solution in original post

Hi @lakshmi9 ,

it is directly coming from template that's why is is not appearing mandatory.

Thank you
Chandan

View solution in original post

Hi @lakshmi9 

There are two possible reasons: First, there might be another script running on the same field that is overriding the mandatory setting. Second, it could be a bug. Also, please check if there are 2-3 views in the SOW and whether you added the correct view in the script.

*************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.

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/atul_grover_lng [ Connect for 1-1 Session]

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

View solution in original post

13 REPLIES 13

Hi @lakshmi9 ,

it is directly coming from template that's why is is not appearing mandatory.

Thank you
Chandan

Dr Atul G- LNG
Tera Patron
Tera Patron

Hi @lakshmi9 

 

As per my understanding, a Standard Change is logged via a template, and in the template, you're already adding the short description and justification. So, if the value is coming from the template, it will not appear as mandatory to the user."

*************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.

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/atul_grover_lng [ Connect for 1-1 Session]

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

Hi @Dr Atul G- LNG / @SD_Chandan 

 

  • I agree, but I noticed that in the default view, the Description field is showing as mandatory for the Standard Change template after I used an onload Client Script.
  • However, in SOW the same script doesn’t make the field mandatory, which is confusing.

lakshmi9_0-1752661522435.png

 

Hi @lakshmi9 

There are two possible reasons: First, there might be another script running on the same field that is overriding the mandatory setting. Second, it could be a bug. Also, please check if there are 2-3 views in the SOW and whether you added the correct view in the script.

*************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.

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/atul_grover_lng [ Connect for 1-1 Session]

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