catalog ui policy is not working in target record
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-20-2023 11:30 PM
Hi,
I have converted one catalog form into a record producer, all variables,ui policy and script is copied into the record producer. in that we have one ui policy which is used for making variable editable in the target record (a new custom table extended from task).
all working fine in my development instance but when i moved this update sets to QA instance, the variables are still ready only means it is not editable we don't have any script or UI policy in our custom table to make all variables read-only, but when i am executing a alert message from ui policy on target record it is showing the alert message as well, but field are still not editable.
here i am attaching my screenshot for both dev and QA instance.
2. QA snapshot
can anyone here help me on this please..
thanks in advance..

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2023 03:26 AM
@Priyansh_98 There could be multiple reasons behind the read only variable editor on the QA instance.
1. Check if there is any client script which is having g_form.setVariablesReadOnly(true);
2. Check if there are any write roles defined on your variables in the QA instance. Please refer https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0683863 for details.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2023 03:55 AM
thanks for your response.
the custom table is newly created and I have also checked that there is no client script created for this. only the OOTB client script is there which is not containing any logic to make variable formatter readable only.
i have also checked the roles, for the variable but that is also not the case here.
i am not able to find out why this is happening.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2023 04:11 AM
On your QA instance are you checking the task using an admin role or are you using a user which doesn't have the admin role.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2023 04:15 AM
yes, using the admin role I am checking, in the variable we haven't defined any role for editing a variable