- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-01-2023 06:16 AM
I've read through the various articles about using UI Policies to make your MRV Mandatory.
While most posed questions seem to be resolved by this answer, I like another one I saw am still not able to make this work in the Now Experience or in UI16. Portal view is working.
I've tried using a On Load client script to no avail. (avoiding using an On Submit Validation scrip).
What property maybe causing this or needs to be set? The MRV is new and i have only one UI Policy on the form.
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-01-2023 07:26 AM
Hi @EricG ,
- Go to the System Property "glide.sc.use_sc_form_v2" record using this URL: https://<INSTANCE-NAME>.service-now.com/sys_properties.do?sys_id=d8f08a9b138e5300e4493d27d144b006
- Change its value to 'true'
- Save the record
- Clear the cache by performing cache.do in the application navigator
- Now, try out the affected record producer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-01-2024 08:06 AM
Hello @Sandeep,
I couldn't find the property "glide.sc.use_sc_form_v2" in the sys_properties list.
Do you know, why I cannot find this record?
Thank you in advance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-01-2023 09:08 AM
@Community Alums Thank you so much for that tip. I tried looking everywhere.
That definitely was the issue.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-01-2023 09:09 PM
Am glad to hear @EricG , that i could help you 😊
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-08-2023 08:12 PM
Just telling someone to add or change a System Property is not a very good answer, and in fact can be dangerous: adding/changing it can have repercussions elsewhere that may not be seen right away. The change needs to be understood before being implemented.
That being said, what version is your instance on? The problem seems to have appeared in Tokyo Patch 1 - link to KB article. I have it running just fine in Tokyo Patch 9, Hotfix 2: