- My View
We previously used the business rule below to hide internal attachments on incidents from end users (ESS users). However, it is also blocking those users from viewing images in KB articles, which makes sense due to those images being embedded attachments from the sys_attachment table. I've tried numerous iterations of adding "Table name" filters to the "When to run" tab, and trying various forms of adding the table name condition to the script. None of these have worked.
Can anyone help me to update the BR to apply only to the incidents table when viewing attachments?
**Note: there are currently no filters set on the When to run tab, and the attachments are hidden from ESS users everywhere, unless they added the attachment.
You will be able to achieve it by creating read acls on sys_attachment table. It will be role based, if you want to give all internal users read access to attachment. Use internal role and make your clients external.
Check if removing external role from this OOB acl will help:
Please mark answer as Correct, helpful as appropriate.
Unfortunately this returns the same result as the business rule.
Any other thoughts?