UI Policy issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-10-2023 08:27 PM
hola
Within my change instance, when the change is in implement state, the actual end date should remain not mandatory
If I then click on to move to the implement state, it should move to the implement state without the actual end date becoming mandatory instead it becomes mandatory and ask for me to enter an actual end date
In other words, I want to be able to proceed to the implement state without that field becoming a mandatory field.
I have checked my ui policies, data policies, BR and CR and cannot find anything causing this behavior so that I can turn it off
How do I troubleshoot to figure out what is making that actual end date mandatory so I can turn it off
Thanks people
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-10-2023 08:46 PM
Here two things might be happening your UI policy or client script will make the field mandatory in Implement state. If there is no UI policy check the data policies and make sure your field is not there in the actions.
Check these two places.
sys_ui_policy_action and search with your field name
sys_data_policy_rule
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-10-2023 09:36 PM
Hi @Mitchell_Milo ,
Can you check the UI action.Assuming the change is being moved into implement state when u press the implement UI action. Maybe there it is configured.
Thanks,
Danish
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-10-2023 11:45 PM
Hi @Mitchell_Milo ,
You can troubleshoot below things :
- If you have button to move state to implement then check that UI action script if you are making it mandatory from there or not.
- Go to UI policy action and enter backend name and check if any UI policy is doing it mandatory
- Go to Data Policy and check from there if any data policy is restricting that.
- Go to client script for that change table and apply filter as script contains backend name of your date field and check if any client script is doing that or not.
Please Mark My Response as Correct/Helpful based on Impact
Regards,
Gunjan Kiratkar
2X ServiceNow MVP
Community Rising Star 2022
Youtube : ServiceNow Guy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-11-2023 06:41 PM
I appreciate the recommended solutions but I have followed all that was recommended and cannot find any script, data action or even ui action causing that field to be mandatory. Any more solutions that you all can recommend?