Process triggering on Task Accept

@aksharc Unfortunately, we can't associate anything with the events on the SAIL Form which we have discussed above. We could follow some other alternate approaches on the form which but again these are not user-friendly, are associated with some extra efforts, slightly deviates from Appian OOTB behavior and requires educating the user:
1. Have a replica of the task in read-only mode with a question on the form which captures the user acceptance. This task should be assigned to Group as usual. Once if the user accepts the task and submits the form, a new task(current task but in editable mode) will be assigned to him/her and at the same time you can also initiate the process.
2. Also, block the Reassignment privilege and make sure that it is handled from the interface only for these particular tasks. This way you can keep track of the acceptance afresh in the case of reassignment which is otherwise not possible.

Let's see if any other practitioners have got an elegant solution.

@aksharc Unfortunately, we can't associate anything with the events on the SAIL Form which we have discussed above. We could follow some other alternate approaches on the form which but again these are not user-friendly, are associated with some extra efforts, slightly deviates from Appian OOTB behavior and requires educating the user:
1. Have a replica of the task in read-only mode with a question on the form which captures the user acceptance. This task should be assigned to Group as usual. Once if the user accepts the task and submits the form, a new task(current task but in editable mode) will be assigned to him/her and at the same time you can also initiate the process.
2. Also, block the Reassignment privilege and make sure that it is handled from the interface only for these particular tasks. This way you can keep track of the acceptance afresh in the case of reassignment which is otherwise not possible.

Let's see if any other practitioners have got an elegant solution.