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

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!

OriginalPostID-155229

OriginalPostID-155229

  Discussion posts and replies are publicly visible

Parents
  • As an update for anyone intersted, I was able to satisft ALL of my requirements by utilizing a service-backed record with data returned via a!queryEntity(). The function checks for system admin or process admin status (within certain groups) and applies logicalexpression filters accordingly (filtering by loggedinuser() as the initator or approver otherwise). Best part, since you manually handle record searching you can filter queryEntity() data on any field you would like, rather than just the 'title' as standard OOTB records do.
Reply
  • As an update for anyone intersted, I was able to satisft ALL of my requirements by utilizing a service-backed record with data returned via a!queryEntity(). The function checks for system admin or process admin status (within certain groups) and applies logicalexpression filters accordingly (filtering by loggedinuser() as the initator or approver otherwise). Best part, since you manually handle record searching you can filter queryEntity() data on any field you would like, rather than just the 'title' as standard OOTB records do.
Children
No Data