You’re offline. This is a read only version of the page.
We are exploring the following entity structure for our customer service scenario
1. Super type or base entity will the default case entity has common fields across subtypes like case created date, status, resolution, desc, case type - Issue, complain, investigation etc.
2. Multiple subtypes called issues, complaints, investigation etc are created to carry business specific fields.
The business scenario needs some subtypes + related case entity fields to be available organization wide access and investigation for instance is only available for a specific set of users. So any investigation + case records for that investigation is only available for this specific set of users and not available organization wide.
How do we model the security roles around this requirement. Basically, how do you mimic, attribute (case type) based access control (ABAC)?
Thanks,
Vinod
Hi,
I am not sure if I understand the security requirement clearly so the solution may or may not be applicable.
You can create different security roles for the 2 different types of users. Create an entity called Investigation and secure access to that entity so only 1 role can read it. Link the entity to Case record.
Also create different forms for the user security roles and add fields / lookup only to the form as required.
Hope the above helps.
Share
Report
All responses (
Answers (
4,036
