I have been using People Task for approval processes in my recipe. What i would like to know is whether i can set an apporval threshold for a certain task to complete. My current scenario is that when i have multiple approvers for a task, even i one approve approves the task the recipe proceeds without letting the other approvers vote in their choice. So instead i would like to set up a threshold for the approval process to let the recipe proceed. Any help is appreciated.
Thankyou.
Best Answer
P
Patricia Guevarra
said
over 6 years ago
Hi Dorothy,
Thanks for reaching out! Unfortunately, this is currently not a built-in feature of our People Task tool. However, perhaps this workaround can be of use to you --
You can make different callable recipes that each request for approval from different approvers based on your needs. The parent recipe should asynchronously call these callable recipes so that it can send the request for approval at roughly the same time without having to wait for one to approve the request. At the end of each callable recipe, you can have the recipe update another app or update a lookup table to show that the task has been approved by at least one approver.
In the parent recipe, after the steps that make asynchronous calls, you can add a wait step, and you can set the duration depending on how long you think it may take for your approvers to approve the task.
After the wait step, add a step that searches in the app / lookup table to check if the task has been approved. You can set the recipe up to do this multiple times in case the wait step was insufficient.
You can then add a conditional action that states that the recipe proceed once the search returns an "approved" status.
You can refer to our documentation to find out more about the various features mentioned.
If you would like to learn more about how this can be done, you can join us for a screenshare session with one of our technical experts.
Answer
Patricia Guevarra
said
over 6 years ago
Hi Dorothy,
Thanks for reaching out! Unfortunately, this is currently not a built-in feature of our People Task tool. However, perhaps this workaround can be of use to you --
You can make different callable recipes that each request for approval from different approvers based on your needs. The parent recipe should asynchronously call these callable recipes so that it can send the request for approval at roughly the same time without having to wait for one to approve the request. At the end of each callable recipe, you can have the recipe update another app or update a lookup table to show that the task has been approved by at least one approver.
In the parent recipe, after the steps that make asynchronous calls, you can add a wait step, and you can set the duration depending on how long you think it may take for your approvers to approve the task.
After the wait step, add a step that searches in the app / lookup table to check if the task has been approved. You can set the recipe up to do this multiple times in case the wait step was insufficient.
You can then add a conditional action that states that the recipe proceed once the search returns an "approved" status.
You can refer to our documentation to find out more about the various features mentioned.
If you would like to learn more about how this can be done, you can join us for a screenshare session with one of our technical experts.
Dorothy Xavier
People Task Approval Threshold
Hi,
I have been using People Task for approval processes in my recipe. What i would like to know is whether i can set an apporval threshold for a certain task to complete. My current scenario is that when i have multiple approvers for a task, even i one approve approves the task the recipe proceeds without letting the other approvers vote in their choice. So instead i would like to set up a threshold for the approval process to let the recipe proceed. Any help is appreciated.
Thankyou.
Hi Dorothy,
Thanks for reaching out! Unfortunately, this is currently not a built-in feature of our People Task tool. However, perhaps this workaround can be of use to you --
You can make different callable recipes that each request for approval from different approvers based on your needs. The parent recipe should asynchronously call these callable recipes so that it can send the request for approval at roughly the same time without having to wait for one to approve the request. At the end of each callable recipe, you can have the recipe update another app or update a lookup table to show that the task has been approved by at least one approver.
In the parent recipe, after the steps that make asynchronous calls, you can add a wait step, and you can set the duration depending on how long you think it may take for your approvers to approve the task.
After the wait step, add a step that searches in the app / lookup table to check if the task has been approved. You can set the recipe up to do this multiple times in case the wait step was insufficient.
You can then add a conditional action that states that the recipe proceed once the search returns an "approved" status.
You can refer to our documentation to find out more about the various features mentioned.
If you would like to learn more about how this can be done, you can join us for a screenshare session with one of our technical experts.
Patricia Guevarra
Hi Dorothy,
Thanks for reaching out! Unfortunately, this is currently not a built-in feature of our People Task tool. However, perhaps this workaround can be of use to you --
You can make different callable recipes that each request for approval from different approvers based on your needs. The parent recipe should asynchronously call these callable recipes so that it can send the request for approval at roughly the same time without having to wait for one to approve the request. At the end of each callable recipe, you can have the recipe update another app or update a lookup table to show that the task has been approved by at least one approver.
In the parent recipe, after the steps that make asynchronous calls, you can add a wait step, and you can set the duration depending on how long you think it may take for your approvers to approve the task.
After the wait step, add a step that searches in the app / lookup table to check if the task has been approved. You can set the recipe up to do this multiple times in case the wait step was insufficient.
You can then add a conditional action that states that the recipe proceed once the search returns an "approved" status.
You can refer to our documentation to find out more about the various features mentioned.
If you would like to learn more about how this can be done, you can join us for a screenshare session with one of our technical experts.