Hi Omer,

Normally with Data Domain segmentation it's done at the Record level. So all the attributes within the record would have the same data domain assignment. A potential way you could try to limit access to the Attachments is to use a Business Rule for Rendering forms. You could use the Hide Section rule and then look at maybe preventing certain group/user etc from being able to see the attachments. The only thing by doing that is that all attachments for that Record type would be hidden to that group/user depending on how you define the rule.

a simple example is something similar to this:

Then the user with that Id will no longer see Attachments in the Record type you place the rule in. So if its a specific group you dont want to see the attachments that would work. However, if its a specific attachment that you want to hide that type of rule wouldn't help.

Thank you for your answer. In addition, I would like to ask the following. Can it be prevented from seeing attachments added using Data Domain?

Hi Omer,

You could do something similar to this:

So with that I've assigned the request to a service Desk group called UserGroupB which my logged in current user does not have access to. They have a primary domain of UserGroupA. So within the Request Record the Data Domain is public but the current_user is the value that is hiding the Attachments for that request:

Whereas, if the same user looks at another request they will see the attachments section:

So, Yes you can hide attachments using DataDomains, it's just a matter of setting up the Business rule that best fits for your scenario.

Hi Dave

Thank you for your reply and suggestions. I will work on the subject.