While Linkin' Tasks could certainly be the name of an amazing new alternative band, I would like to use this post to highlight a scenario that a fair amount of you may have faced while building a workflow:
This seems to come up often when:
Now you may be thinking to yourself, "Just hold on a second... I can just create a variable and store the TaskID in it when I configure my task in the workflow designer! Bam!". But... and it's a big but... The Task ID value isn't populated until the task is completed.
Curses! Foiled again...
Well, as it turns out, I have a little trick up my sleeve that I would like to share. The magic of Nintex allows me to use things like parallel branching and looping to do other things while my task is pending. So below I will show you how to get the Task ID and URL for a pending task.
Note: Some of the steps below could be further automated (e.g. collecting up the task list ID, removing the link to the task after the task has been completed, etc.) and there is some additional complexity to consider if you're creating individual tasks for many individuals belonging to a group (which can be solved by using collections) but for the sake of this blog post I have inserted some static values (e.g. the task list ID in the first Build String action) and target a single assignee to quickly demonstrate the solution.
Setup
There isn't too much setup necessary outside of finding the task list ID and possibly adding a Hyperlink column to the list.
The first can be accomplished in a couple of different ways; you could pull it out of the URL when you navigate to the task list (which may not be very friendly as you'll see URL encoding in action), or by opening the site in SharePoint Designer and navigating to the appropriate task list which will display its ID.
Workflow variables
*Make sure your Boolean Found Task variable is set to 'No' so that you can enter the loop!
Item form with the Task URL:
After clicking on the URL, you will navigate directly to the task form for the currently assigned task:
So there you have it. I hope this helps you and as always keep on sharing your experiences here on Nintex Connect!
Note: I will be adding this workflow to the Nintex Xchange as well.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.