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

Chris over 9 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 Chris over 9 years ago

Hi JR, no resolution for us yet - but we will be in the same boat as you with the amount of processes contained in Records (we are just starting our conversion to Tempo now and beginning load/scalability testing). The best solution I can see (I've suggested the required enhancement) would be to allow access to entity fields in the 'value' area of the Default Filter - as this wold allow you to implement a little trick of comparing the same entity Value back to the entity Field, use the = operator, and save all of the overhead - with unlimited scalability. However this is not currently possible, so I'm unsure of our direction as well. This is what I would like to do in the Default Filter:

fldID

=

=if(or(loggedinuser() = touser(rf!fldProcessInitiator),doesuserbelongtogroup(loggedinuser(),getgroupnamed("Business Admin Group"))), rf!fldID, -1)

- Chris
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Chris over 9 years ago

Hi JR, no resolution for us yet - but we will be in the same boat as you with the amount of processes contained in Records (we are just starting our conversion to Tempo now and beginning load/scalability testing). The best solution I can see (I've suggested the required enhancement) would be to allow access to entity fields in the 'value' area of the Default Filter - as this wold allow you to implement a little trick of comparing the same entity Value back to the entity Field, use the = operator, and save all of the overhead - with unlimited scalability. However this is not currently possible, so I'm unsure of our direction as well. This is what I would like to do in the Default Filter:

fldID

=

=if(or(loggedinuser() = touser(rf!fldProcessInitiator),doesuserbelongtogroup(loggedinuser(),getgroupnamed("Business Admin Group"))), rf!fldID, -1)

- Chris
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data