ITSM Simulator - Configure Change Management Form
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-04-2025 01:00 AM - edited 07-04-2025 01:03 AM
Hello, I am currently working my way through the ITSM Simulator at the Configure Change Management Form, I cant seem to suss out where I am going wrong. Scenario details below
Scenario:
Change approvers should have all necessary information on the change request at the time of submission, including:
- Requested by
- Configuration item
- Impact
- Description
- Planned start date
- Planned end date
1. In addition to any fields already mandatory, the fields above must also be mandatory any time a change request is not in a New or Canceled state.
Steps taken so far
Used System UI > UI Policies, New.
Configure the UI Policy
- Table: Change Request [change_request]
- Short Description: Mandatory Fields - Not New or Canceled
- Conditions:
- Add a condition: State is not New
- Add another condition: State is not Canceled
- Global: Leave unchecked (unless you want it to apply to all views).
- On Load, On Submit, Reverse if false: Checked
- Save the UI Policy, then click "New" under UI Policy Actions to define the mandatory fields.
When i try to validate the work, I keep getting an error saying "please verify each of the listed fields for this task are mandatory", they are set to true. Screenshot attached.
Apppreciate input on what I am doing wrong. Thank you
- Labels:
-
ITSM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-04-2025 01:41 AM
Hi @dcb,
from the configuration perspective it looks OK, have you tested it yourself to validate it works ok?
Debug tips:
- try to deactivate and activate it again,
- if you copy/pasted any text, check if it is copied properly and there are not any additional blanks (yes, it can differ),
- try to re-create again.
If nothing helps, you can skip this as all the ServiceNow labs can be completed at 80 % of the overall progress.... So test it if works as required and if so, you don't need to spend too much efforts on making the validation work if you have other stuff to do....
/* If my response wasn’t a total disaster ↙️ ⭐ drop a Kudos or Accept as Solution ✅ ↘️ Cheers! */
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-12-2025 07:16 AM
I was facing the same issue but got it solved. I think, the condition setting must be exactly as requested:
State - is not one of - New/Canceled
With other condition settings I failed as well...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a month ago
I was having the same issue as described by dcb above, until I reviewed his settings against mine and realized my conditions were a little different. So I went back to the method I used on configuring incident fields to mandatory as shown below. And it validated real nice.
Thanks for the hint and good luck.