Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
36 replies
Subscribers
11 subscribers
Views
12106 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Data and Records
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!
OriginalPostID-155229
OriginalPostID-155229
Discussion posts and replies are publicly visible
Parents
0
Chris
over 9 years ago
Well, with a user in 9,010 groups, that user can barely operate in the system - logging in takes almost a minute and the Reports and Records tabs themselves throw the error below, before any Reports or Record headers are even loaded on those main pages (can't even get to the record I was trying to test).. So, looks like it is back to the drawing board again..
2015-07-14 22:36:56,543 [ajp-/0.0.0.0:8009-2] 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.
2015-07-14 22:36:57,955 [ajp-/0.0.0.0:8009-1] 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.
2015-07-14 22:36:57,958 [ajp-/0.0.0.0:8009-1] ERROR com.appiancorp.rest.shared.FallbackExceptionMapper - Internal Server Error on REST API invocation.
org.hibernate.exception.SQLGrammarException: could not execute query
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
Chris
over 9 years ago
Well, with a user in 9,010 groups, that user can barely operate in the system - logging in takes almost a minute and the Reports and Records tabs themselves throw the error below, before any Reports or Record headers are even loaded on those main pages (can't even get to the record I was trying to test).. So, looks like it is back to the drawing board again..
2015-07-14 22:36:56,543 [ajp-/0.0.0.0:8009-2] 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.
2015-07-14 22:36:57,955 [ajp-/0.0.0.0:8009-1] 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.
2015-07-14 22:36:57,958 [ajp-/0.0.0.0:8009-1] ERROR com.appiancorp.rest.shared.FallbackExceptionMapper - Internal Server Error on REST API invocation.
org.hibernate.exception.SQLGrammarException: could not execute query
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data