How is everyone handling record security, when requirements require dynamic visi

Chris over 8 years ago

How is everyone handling record security, when requirements require dynamic visibility? For instance, we require records for an application to be visible for all application administrators and also to the process initiator (initiator should only see the record for the process isntance they have initiated). Sometimes, company divisional views are necessary as well - divisional administrators should only see records for their specific division. With nearly 40 applications in production, we do not want to have 3+ records for each application. Just wondering if anyone has experience with similar situations. Thanks!

Discussion posts and replies are publicly visible

Parents

0 Mike Schmitt
Certified Lead Developer
over 8 years ago

Yeah, I seem to remember something to pass in there. It may even be as simple as setting the record field to the record's primary key ID, and in the expression, have it resolve to be equal if the user matches correctly, and have it return something else otherwise. I'd recommend playing around with it, i believe you'll find something that satisfies your requirements without too much trouble IIRC.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Mike Schmitt
Certified Lead Developer
over 8 years ago

Yeah, I seem to remember something to pass in there. It may even be as simple as setting the record field to the record's primary key ID, and in the expression, have it resolve to be equal if the user matches correctly, and have it return something else otherwise. I'd recommend playing around with it, i believe you'll find something that satisfies your requirements without too much trouble IIRC.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data