Multi-row variable set value is being cleared when it is made read only
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-26-2020 12:42 PM
I've got catalog item which contains multi row variable set. The multi-row variable set is being displayed on the RITM and SCTASK variable as read only.
I have created UI Policy to make the variable set read only on RITM and Task forms. but when i perform any update operation on the RITM or Task, the variable set value is getting cleared out.
If i deactivate the UI Policy and then perform update operation on RITM or Task form, then the value is not getting cleared out.
clear variable value is also set as false in the ui policy.
Has anyone faced this issue or anyone can assist on resolving this issue?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-27-2020 09:53 AM
Thanks! Dennis
If I deactivate the UI Policy and then perform update operation on RITM or Task form, then the value is not getting cleared out.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-04-2020 05:57 AM
I have encountered the identical behavior with a MRVS being displayed on an HR Case. Deactivating the policy prevents the contents from being cleared out.
I went a step further and created a UI policy from within the variable set setting all variables within to read only. While the prevented the contents from being cleared, anyone can still delete or add to the MRVS on the target record. In essence...it's not entirely read only.
I have reported this on a HI case and include their response on this thread.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-04-2020 09:38 AM
Here is a response I received from ServiceNow on this matter.
Reason:
This issue is identified as PRB1369331 which is fixed in NewYork Patch 5.
https://hi.service-now.com/kb_view.do?sysparm_article=KB0787378
Solution Proposed:
Above kb contains a workaround until upgrading to NP5, which is available for upgrade.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-04-2020 10:13 AM