Hi there.
Sometimes there is a business scenario you need to make some actions more user friendly (quick). For example, if someone approves many tasks, you don't want him to open every task and click the approve (submit) option. I want to give the approver an option to submit from a site (not an input form). So I have in mind grid or list of his tasks and he can click "approve" or "reject" button in each line (instead of opening each task and click tehre). Is this possible in Appian?
Discussion posts and replies are publicly visible
YOU can try using functions like getactivetaskidsforprocess() , and showing the results in an interface, where the user can select as much tasks as needed and once click submit, start a process that makes the operations you may need (probably using an smart service)
A couple of ways to do this but one of them could be to use the Complete Task Smart Service.
docs.appian.com/.../Complete_Task_Smart_Service.html
I am assuming that your tasks are Process Backed and not DB backed, which makes this requirement even more difficult.
So this is what I would do - Execute Complete Task smart service in a loop in a process that submits all of these tasks one-by-one
IMHO, a task that is meant to be mass-accepted, is a bad candidate for being designed as a user input task. Just trying to find a technical solution for this does not feel right.
I am not into mass approval. I just want an option for the better (faster) option to approve. Because you can approve tasks based on info in a grid without opening the input form. So, only one at a time.
I would like to approve only one task at a time. If I click the approve button in a grid, this task should be completed.
Then you can add a buttons in a dedicated column of the grid, and execute this smart service in the button's saveInto
OK. Again, does that approval require any input other than YES/NO? Did you enable deadlines and escalations? If NO, NO and NO, why make it a UIT?
Then, is there an option do automate approvals based on some logic?
I mean, nobody wants to be bothered with meaningless approvals.
In case of rejection, a comment would be required to be entered. This is the case for the leave request approval process. The approver will have a calendar with all leaves to make it easier to decide. There is a need to notify requesters about the decisions and some automatic approval options, and there would also be two layers of approval.
There is no need to open the approval form in a new (or same) tab just to click approve or deny. The approval decision can be important, complex (in a sense that it can't be automated) and simple (only two outcomes possible) at the same time.