- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-31-2016 09:14 AM
I've encountered something very odd today. A UI policy that continues running after being deleted.
I had a UI policy that was setting some incident fields to read only on specific state values. This was inactive - but it turned out that it was still running. I searched for UI policies running against task doing the same thing - but there are none. UI policy debugging shows that it is the UI policy named "Set fields to read only on resolve". There was only one of these. And this UI policy was certainly inactive.
As the UI policy was inactive and had been replaced with another, I decided to delete it just to stop this odd behaviour.
And what do you know? It's still running and still showing up in the debug log. Even after clearing the log, creating a new incident, and trying again, it's still there. Clearing the log, disable debug, re-enable debug - retry. Still happening. cache.do - retry. Still happening!
Has anyone seen anything similar? This is a Fuji P12 HF1 version instance.
I'm starting to worry that maybe I'm losing my marbles...
Cheers,
Danny
Solved! Go to Solution.
- Labels:
-
User Interface (UI)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-31-2016 09:47 AM
Two options - option 1: turn on the field watcher on that field and see what's going on.
Field Watcher - ServiceNow Wiki
Option 2: check sys_ui_policy_action to ensure no other UI policies are working against that table/field.
Also, check your client scripts! (which may be revealed by option 1)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-31-2016 09:51 AM
Do you have Multi Domain Instance ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-31-2016 09:53 AM
That's a good question. Daniel, this doesn't happen to be a domain separated instance, does it?@
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-31-2016 09:53 AM
Ah ha! GOT IT! It's a Data policy. But field watcher, for whatever reason, shows it as a UI policy.
Nice. Thanks Chuck! Really appreciate your help.
D
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-31-2016 09:54 AM
Because "use as UI policy on client" is set.
Guess who created it too? Me of course.
Doh!
Cheers all!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-22-2016 11:19 AM
Thanks! I had this same exact problem and your post helped me out a lot. Thanks again!
