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
11773 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
mschmitt, that was the direction I was heading initially. However we will be using entity backed records based on other requirements, but I'm assuming I can log intiiator account in the CDT/Entity and run touser() on that field for comparison. Groups should be less hassle to map as well - being new to Record Types/7.9 I'm just trying to figure how to map that to the filter Field vs Value - where Field is only available from the source entity - not an expression. Seems like I would need a field that holds a value of true() to compare to the loggedinuser() vs initiator vs admin group expression checks..
Will play around with both of the suggestions, thanks!
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
Chris
over 8 years ago
mschmitt, that was the direction I was heading initially. However we will be using entity backed records based on other requirements, but I'm assuming I can log intiiator account in the CDT/Entity and run touser() on that field for comparison. Groups should be less hassle to map as well - being new to Record Types/7.9 I'm just trying to figure how to map that to the filter Field vs Value - where Field is only available from the source entity - not an expression. Seems like I would need a field that holds a value of true() to compare to the loggedinuser() vs initiator vs admin group expression checks..
Will play around with both of the suggestions, thanks!
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data