Change Request and Problem Field not getting populated in UI Policy UI Action tree.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-29-2026 10:39 AM
I have tried installing Service Operations Workspace ITSM Advanced Applications Plugin due to which I got Change Request and Problem fields visible on Incident form layout. But I want to make them mandatory when On hold reason is Awaiting Change or Awaiting Problem, so I tried creating UI Policy for that and in the UI policy Action when I tried selecting field form the Tree I was not able to see Change Request/RFC and Problem fields.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-31-2026 02:43 AM
Some things to check:
Did you log out and back in again after installing the plugin?
Did you validate that the fields are on the form?
Are you really on the incident form?
I checked on my instance, and the fields are simply there to select (Change Request / Problem).
Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-01-2026 11:51 PM
Hi Mark, Yes I tried log out and log in after installing the plugin,
Yes fields are there on the form.
Ye I'm on incident form.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-02-2026 12:17 AM
I’m facing the same issue in my instance. The Change Request/RFC and Problem fields are visible on the Incident form, but I’m not able to find/select them when creating a UI Policy.
I’ve already tried logging out and back in and confirmed that I’m working on the Incident form. Has anyone found a solution or workaround for making these fields mandatory based on the On Hold Reason?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago
This issue feels like an issue with the instance. @sharmakrishnam try raising case with ServiceNow.
