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
11791 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 8 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 8 years ago
akshayan, thanks - that will work for most situations, except for group changes mid-process. We have models where hundreds of tasks will sit with a group for months - during which time the admin group is often changed, where the new admin will then not be able to see current records they should and the old will be left with views of records they should no longer have permissions - unless we create a mechanism to update close to 1,000 process instances during each group change. For example, one model has 1,246 running instances of which 743 are with 1 group for which the admin/visibility rights can change at any time. This could be part of the resolution however.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
Chris
over 8 years ago
akshayan, thanks - that will work for most situations, except for group changes mid-process. We have models where hundreds of tasks will sit with a group for months - during which time the admin group is often changed, where the new admin will then not be able to see current records they should and the old will be left with views of records they should no longer have permissions - unless we create a mechanism to update close to 1,000 process instances during each group change. For example, one model has 1,246 running instances of which 743 are with 1 group for which the admin/visibility rights can change at any time. This could be part of the resolution however.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data