Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Suggested Answer
+2
person also asked this
people also asked this
Replies
16 replies
Answers
2 answers
Subscribers
8 subscribers
Views
10842 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
User Interface
hiding the task toolbar (reassign task, save changes, etc.)
erickp
over 7 years ago
There is a known Appian defect: when an admin user reassigns a task to a non-admin user, that non-admin user is able to reassign to ANYONE. I am trying to find the best way to avoid this in PROD because we don't want non-admin users to be reassigning. I thought a way would be to hide the task bar on the left where the Reassign Task link shows up. Is there any way to remove this task bar WITHOUT removing the Save Changes functionality? On the user interface task, I saw an option under Forms that says Hide task toolbar but it did not work. Why? What other options do I have?
OriginalPostID-235796
Discussion posts and replies are publicly visible
Parents
0
Matthew Kornfield
Appian Employee
over 7 years ago
Just make a variable (type user or even type text) that is the assignee, pv!assignee. Have the task "submit" (i.e. flow out) and then be assigned again to the pv!assignee, but at the outflow, have an XOR check for reassignment, and then that XOR should direct to a script task or something to designate the new assignee as the value of pv!assignee.
I made a small visual below. The key is that the process variable (pv!assignee) is the same assignee, but the contents have changed (user A to user B). Let me know if you still have questions.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
Matthew Kornfield
Appian Employee
over 7 years ago
Just make a variable (type user or even type text) that is the assignee, pv!assignee. Have the task "submit" (i.e. flow out) and then be assigned again to the pv!assignee, but at the outflow, have an XOR check for reassignment, and then that XOR should direct to a script task or something to designate the new assignee as the value of pv!assignee.
I made a small visual below. The key is that the process variable (pv!assignee) is the same assignee, but the contents have changed (user A to user B). Let me know if you still have questions.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data