I don't think so. I could imagine some logic to achieve this but to give you a suggestion it would be helpful to know more about your scenario, like who is approving/rejecting whose tasks in what situation and how the workflow should act in case of approving all or only some of the tasks given.
Thanks for your reply. We have a list for sales order approval. For each list item created, one approval task will be assigned to manager. The manager may have multiple approval tasks every day. It is not convenient to open each task item and complete it. We still only allow task assignee to approve/reject the task.
I have tried create the sales order task view by modifying the workflow tasks list default view. When updating the tasks by editing list, "Outcome" field cannot be edited.
Hmm, I see.
I always think it's best to review each task to not approve/deny a task by accident because the approver thought it would be another task but if it's a requirement I leave that to you.
I still don't think there is a good way to achieve this. You would need to manipulate workflow task list which is never a good idea. I would rather think of using other approval channels first to make it more convenient for your approvers to approve tasks before I would go for the 'dirty stuff'
Do you think you could introduce one of the following approval channels to your approvers?
Each of them still require tasks to be approved one by one but it might be a bit more sexy for your approvers.
@toby_lin ! I know this is 2 years later but did you get any solution for this concern from nintex? If you still need it I can share the workaround we made from our end.
I’m interested in your workaround. The ability to approve multiple items at once would work very much for one of my workflows.
I would be very much interested as well. Something as simple as manually changing the outcome column in the task list by the task assignee in Quick Edit Mode would work perfectly, but I can't find a way to make this field editable.
Adding a list column with a trigger to update the outcome value using CSOM could be an option but if I can avoid this route...