We have requirement where user clicks on "Save and Exit" button, and the flow will loop back to same task, and assign to the same user.
When the task is initially assigned we don't see the re-assign button, but when we loop back and then user opened the task from task list Re-Assign button is visible. Tasks have assignment privilege as No Privilege across. Has any one faced this issue.
Are you testing as a basic user or as a system admin user, just out of curiosity?
I am testing from basic user.
Is the process containing this task called as a subprocess from another process model?
If yes, please check the assignment of the subprocess where it is configured, the assignment should be "run as whoever started the process".
If it is "Run as whoever designed the process model", it will run as designer who published the process model recently and it will show this Reassign option.
No, this is a standalone process.
Once the user clicks on "Save and Exit". The information is saved and the task is available in "My Task" .
Is there a reason you are using a "Save and Exit" button instead of using the out-of-the-box saving option?
well, i can think of a variety of reasons - mainly centered around the fact that they may wish the "save" operation populate some data to DB, which unfortunately we have no way of controlling using the OOB "Save" button.
Good point - I know there are good reasons to not use the OOTB save (just like Mike mentioned). However, it's always useful to think about whether it's necessary to custom-make a solution. The OOTB save is a single checkbox, while a custom solution like this requires more testing and maintenance.
Thanks Peter and Mike. As, Mike mentioned this is the reason we were not able to use "Save Draft" operation, but my concern is even if the reassignment privilege in the user input task is set to "none" then why the re-assign tab gets visible when the basic user open it from task list? Am I missing something?
I can't replicate this in 19.1 - the reassign button is correctly hidden after each save loop for me. I would suggest attempting to replicate in your environment with a small test model, and posting a few screen shots of your configuration. Which version of Appian are you on?
We use this logic in a number of places as well. Aside from the aforementioned DB persisting, should we need to store documents or reset escalation timers, looping out and back in is necessary.
Thanks Chris. There was security configuration related to the respective process model was setup incorrectly for this set of basic user group. Its been resolved . Thanks all for your help.
Discussion posts and replies are publicly visible
© 2019 Appian. All rights reserved.