Add ability to store "Action ID" into a variable in a Flexi Task
Currently available in a Request Approval action but not in a Flexi Task.
Mining
shared this idea
8 comments
-
Scott
commented
Hi Jon,
Thanks for that - that solution definitely works for 95% of the requirements that you'll get around these.
The only time it gets 'funny' (and not ha-ha funny) is when you need the x parallel approvals to have individual outcomes. I.e. if Approver 1 rejects, do these things. If A2 rejects, do these different things.
A bit picky, I know, but you know how The Business can be...
-
Hi Scott and Cory,
I believe your use case is already supported by the Flexi-task action.
Select "All must agree on a specific outcome" under the "Behaviours" section in the configuratio.
Specify "approive", for example, as the response that all must agree to.
Then should the first or subsequent person not agree, the task will complete at that time without waiting for any other respondents. You do not need the task iDs (which can be saved if you select a variable to store them in under "Store task IDs in" in the configuration).
I believe this request should actually read "Populate task id as soon as the task is created" which is then the same reqiuirement as the idea of that description and we should merge these two.
-
Scott
commented
Very confusing why this isn't already included. I thought Flexitasks were the 'flagship' tasks, and yet functionality is missing.
Use Case : I have 3 parallel approvers. When one rejects their tasks, it needs to auto-complete the other 2 tasks. The Complete Workflow Task action needs the Action ID to do this. Flexitask cannot store Action ID. Pout.
-
Mike M
commented
Hello Nintex: are you able to update the Flexitask action to support the Action ID just like the Request Approval action does? This would make using the Complete Task action possible.
Thanks
-
Cory Westerlund
commented
I don't think the Task ID's will work. I want to run 2 Flexi tasks in Parallel. If one gets rejected, I want to be able to automatically reject the other one with the Complete Workflow task action so that the workflow can finish immediately instead of waiting for the other Flexi task to finish.
-
Greg. M
commented
There might be some scenarios where you need to complete the whole task (beacuse a status was changed for example) and start over an approval process.
-
Emiel Schönfeld
commented
It would be nice to get a collection of task ID's in the order of which the participants are filled.
-
Jimbo Alba
commented
I need the Action ID in order to run 'Complete Task' on a task from a separate workflow.
