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
4 replies
Subscribers
6 subscribers
Views
2356 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Process
Here is a use case There is a workflow which goes this way, the recor
vinayakb
over 8 years ago
Here is a use case
There is a workflow which goes this way, the record flows between different user groups Group A -> Group B -> Group C -> Group D
There is a user which can belong to Group A, B and D. Once the user in group A has initiated the task, he shouldn't be able to accept the task belongs to Group B and Group D. I can take care of this at interface level, if the user in Group A has accepted the task of Group C or Group D. But is there a way, we can avoid the user to accept/hide the task which belongs to Group B and D. If the user is the orignial initiator.
I hope I have expained the use case well :-)
OriginalPostID-221199
OriginalPostID-221199
Discussion posts and replies are publicly visible
Parents
0
rawich
over 8 years ago
The most elegant solution is to have a new feature in the product that implement "Two-Man Rule" aka "Four-eye Principle" by accepting list of groups or users to be excluded from the task assignment.
en.wikipedia.org/.../Two-man_rule
Without that, any solutions would come with a trade-off.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
rawich
over 8 years ago
The most elegant solution is to have a new feature in the product that implement "Two-Man Rule" aka "Four-eye Principle" by accepting list of groups or users to be excluded from the task assignment.
en.wikipedia.org/.../Two-man_rule
Without that, any solutions would come with a trade-off.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data