RITM record not loading on Agent workspace
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-15-2019 01:02 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-03-2020 05:51 AM
Hey don't know if you found the fix, but a UI policy might be causing the issue.
Check the UI policies configured in the "sc_req_item" with a condition which pulls "Variables" which is a field that is not available to choose from in an OOB instance.
Deactivating the UI policy (or) removing the "Variables" conditions from the UI policy should resolve the issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-03-2020 06:38 AM
Thank you so much! I'll revise that with my teammates internally and get back with results.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-06-2023 12:35 AM
Hi Jen.
I'm having the same issue with incident records. did you manage to solve this issue?
if yes can you please help?
Thanks 🙂
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-05-2024 05:47 AM
Hello, In our case it turned out that The "GlideSHN_query" points to the system property "sn_shn.note_preferences". The system property comes from the "Special Handling Notes" plugin. The issue occurs only when the system property is present in the instance but the plugin is inactive. To resolve the issue, we delete the "sn_shn.note_preferences" system property from the instance and perform a cache flush as the ServiceNow support team suggested
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-05-2024 05:48 AM
Hello there, In our case it turned out that The "GlideSHN_query" points to the system property "sn_shn.note_preferences". The system property comes from the "Special Handling Notes" plugin. The issue occurs only when the system property is present in the instance but the plugin is inactive. To resolve the issue, we delete the "sn_shn.note_preferences" system property from the instance and perform a cache flush as ServiceNow support team suggested