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
  • I was able to run a few performance tests today, and the results are not exciting. With 24,771 records in the DB - I'm receiving memory threshold errors as the Record refuses to load:

    Error evaluating function 'queryruleexec' : Memory threshold reached during output conversion (rule: [QR_SIR_All], type: [CDTSoftwareInstallRequestDT999], threshold: [1,048,576 bytes], objects successfully converted: [20,468]

    So, this method may not work for me. It is also concerning as I have users who will need to view 150,000 records - might have to try something along the lines of the 'best practice' route, hopefully that will perform better. ugh.
Reply
  • I was able to run a few performance tests today, and the results are not exciting. With 24,771 records in the DB - I'm receiving memory threshold errors as the Record refuses to load:

    Error evaluating function 'queryruleexec' : Memory threshold reached during output conversion (rule: [QR_SIR_All], type: [CDTSoftwareInstallRequestDT999], threshold: [1,048,576 bytes], objects successfully converted: [20,468]

    So, this method may not work for me. It is also concerning as I have users who will need to view 150,000 records - might have to try something along the lines of the 'best practice' route, hopefully that will perform better. ugh.
Children
No Data