Flow Context Field editable in RITM List view
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-27-2025 04:21 AM
Hi All,
We recently upgraded to Xanadu , and after the upgrade in RITM List view the field "Flow Context" is allowed to be edited and select any random flow to be updated on this field for fulfiller users (non-admin) , in our instance which is still not upgraded to Xanadu does not have this issue.
I know that there have been many upgrades done to flow designer recently, but could not figure this out. Checked the acls through access analyzer and access to list_edit is passed in both upgraded and not upgraded instances but still the difference in behavior exists.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-27-2025 04:50 AM
if this was not happening earlier and started happening after upgrade then it's a platform bug.
Please raise a case with ServiceNow.
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-27-2025 08:12 AM
Yes I did raise a case with them

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-27-2025 04:51 AM
HI @Anubhav24 ,
You are right, the flow context is open to be enetred with any value from the flow context table.
This was not the cae in Vancouver , guess what it's open in Yokohama as well !!
So what you can do is you can write a Client Script and make it read only or write an ACL for the same.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-27-2025 08:13 AM
@Community Alums , ideally it should'nt be right , because once a flow is attached to a RITM it should not be changed. I can write an ACL however before that I need to understand why was this enabled post that we can enable a logic.