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

The query rule was returning all columns - unfortunately when I implement 2 new query rules (one taking the loggedininitiator() parameter) with just the fldID as the only other column, I'm still seeing issues loading the Record with only 24,771 rows.

ERROR org.hibernate.util.JDBCExceptionReporter - The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Too many parameters were provided in this RPC request. The maximum is 2100.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Chris over 9 years ago

The query rule was returning all columns - unfortunately when I implement 2 new query rules (one taking the loggedininitiator() parameter) with just the fldID as the only other column, I'm still seeing issues loading the Record with only 24,771 rows.

ERROR org.hibernate.util.JDBCExceptionReporter - The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Too many parameters were provided in this RPC request. The maximum is 2100.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data