Hello, I'm currently learning about the various functions of Appian to understand how powerful it can be. At the moment, I'm facing an issue with creating an approval process that has a condition where at least 2 out of 3 approvers must approve in order for the flow to continue. This is what I have configured in the user input task node so far.The problem I'm facing right now is that I don't know how to update the value of pv!approvalResults (which is a list of text) when each approver takes an action. Could you please give me some advice?
pv!approvalResults
Discussion posts and replies are publicly visible
Something like this?
What I want is to check 2 out of 3 conditions by sending tasks through a single user task input step, where the tasks will be assigned based on the number of people in the group.Is it possible to do it this way, or do I have to separate the user task input steps as in the example you provided in order to meet this requirement?
This would not work?
My question is: What happens with the tasks still waiting for the user to make a decision, once you have all the positives you need?
Just tried it.
When I try to cancel the orphan task, I get this message
It's my fault for not explaining the requirements clearly. What I actually need is for the task to be assigned to all users in the group. If any two of them approve, the process model should proceed to the next step. However, if any one person rejects, the task is considered rejected and the process model should immediately continue. Regardless of whether it's approved or rejected, once the process proceeds based on the condition, the tasks previously assigned to the other users should be removed.
It's my fault for not explaining the requirements clearly. What I actually need is for the task to be assigned to all users in the group. If any two of them approve, the process model should proceed to the next step. However, if any one person rejects, the task is considered rejected and the process model should immediately continue. Regardless of whether it's approved or rejected, once the process proceeds based on the condition, the tasks previously assigned to the other users should be removed.Based on the configuration shown in the image you sent, I don't think it would meet the requirement. This is because if one person rejects, it would still require another person to take action before the process model can proceed to the next step.