Incident record fields limited for non-itil user
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-06-2024 12:57 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-06-2024 03:13 PM
Hi,
In what way did you modify the Incident query BR? Seems you may add another 'current.addQuery()' line after the one present. I don't understand how that affects the form but form fields can be affected by ACLs, client scripts, UI Policies, etc. Is there a group or role that you want to assign to "The business" users? If so, a quick test would be to create a Read ACL for those users and the incident and task tables.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-09-2024 06:06 AM
Hey @Bert_c1, I added the role the business users will be assigned into the if statement condition. Other than that the script wasn't modified but prior to that change they couldn't access any records.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-09-2024 06:32 AM
Hi
It looks like after modifying the 'Incident Query' Business Rule to grant read access for tasks and incidents, some fields on the Incident form are still not visible, likely due to an ACL (Access Control List) issue. ServiceNow enforces field-level and table-level ACLs, and if a role is missing the necessary permissions, fields or even entire records can be restricted.
Please check below points:
- Ensure that field-level ACLs are allowing access to the fields.
- Check table-level ACLs to ensure full form access.
- Use the Debug Security Rules tool to identify which ACLs might be restricting access.
- Modify the ACLs to include the role of the business users or create new ACLs that specifically grant the needed access.
i hope my answer helps you to resolve your issue, if yes please mark my answer correct & helpful.
thank you
rajesh