How to display an error message when a user is not allowed to edit a ticket in SOW.(MRA)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Background:
I have ACLs configured that users with ITIL role can read all tickets, but they can only write/edit tickets that belong to their assignment group.
Current behavior (As‑Is):
1. ITIL user opens a Change Request that they are allowed to edit (Change record belong to their assignment group).
2. ITIL user attempts to add a related record such as an Incident which they only have read access (Incident record not belong their assignment group).
3. Incident record can be selected, but it cannot be successfully related, and no error message is displayed to inform the user of the reason.
Expected behavior (To‑Be):
When user attempt to relate a record for which they do not have edit permission, the system should display an error message indicating that they do not have sufficient permission to relate the record because they are not allowed to edit. In service operation workspace view with MRA page in related recodes tab.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
may be use before update BR on incident and check if the linkage happening satisfies the ACL role or condition and then throw error and abort the update.
💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏
Ankur
✨ Certified Technical Architect || ✨ 10x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi, Ankur Bawiskar
My issue is O2m in related record tab such as Incidents Fixed By Change, Problems, Incidents Caused By Change, Change Requests in service operation workspace. So, I did not know what the value to set in BR.
Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
you should write BR on the table where the field is getting updated
Example:
1) incidents Fixed By Change - write before update BR on incident
Condition: change_request Field Changes and Not EMPTY
2) Incidents Caused By Change - write before update BR on incident
Condition: caused_by Field Changes and Not EMPTY
💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏
Ankur
✨ Certified Technical Architect || ✨ 10x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Hope you are doing good.
Did my reply answer your question?
💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏
Ankur
✨ Certified Technical Architect || ✨ 10x ServiceNow MVP || ✨ ServiceNow Community Leader
