Just doing some testing I found out the Request Data task action is doing it right. It's the only task action that populates the TaskID even before task completion. I tested all task actions and also included action id on the test. Below you can see the results.
|Action ID||Task ID|
|Assign Flexi Task||No||No|
James Tyzack, can you check this out if this is by design? I hope all task actions will populate their task id as soon as the task item is created.
Solved! Go to Solution.
jimbo alba, thanks for doing the testing on this. Definately voted for your idea to make the task id available as soon as the task is created (Populate task id as soon as the task is created – Customer Feedback for Nintex)
I did. The solution is not beautiful, but works fine.
On my solution i need an ID item of Workflow tasks to build an external URL.
I used the parallelism action. One branch goes to Flexi multi task and the other goes to query workflow tasks list.
Look, the second branch goes faster then one, so i need to get "Pause for" action.
The first branch creates a task on Workflow Tasks list, and the other, before a time expired, gets the ID.
Query by: Workflow name, outcome (equal Pending), status (not equal Completed), Related Content (the IDItem from my list) and title ( because on my solution, from one item to another the content of title field changed)
I hope you undertand.