Tessa
My feedback
-
39 votes0 comments · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →
The work around for this is to create a list with the appropriate columns to store the data one wants. Use update list to store the data and query list to retrieve the data.
Tessa
supported this idea
·
-
36 votes0 comments · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →
The work around for this is to create a list with the appropriate columns to store the data one wants. Use update list to store the data and query list to retrieve the data.
Tessa
supported this idea
·
-
6 votesOpen for voting · 1 comment · 5 - Nintex Workflow Cloud » Workflow Designer · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment Tessa
shared this idea
·
-
1 voteTessa
shared this idea
·
-
3 votes1 comment · 5 - Nintex Workflow Cloud » Dashboard Experience · Flag idea as inappropriate… · Admin →Tessa
shared this idea
·
-
22 votesunder review · 2 comments · 5 - Nintex Workflow Cloud » Workflow Designer · Flag idea as inappropriate… · Admin →Tessa
shared this idea
·
-
6 votesTessa
supported this idea
·
-
15 votesTessa
supported this idea
·
-
20 votesTessa
supported this idea
·
-
46 votesplanned · 1 comment · 5 - Nintex Workflow Cloud » Workflow Designer · Flag idea as inappropriate… · Admin →Tessa
supported this idea
·
An error occurred while saving the comment Tessa
commented
I've had another situation where this feature would be helpful. I wanted to wait to set a variable until a Boolean variable on a parallel path was set to Yes. We ended up using loops to pause and periodically check the value of the Boolean variable. However, we ran into failures because of the high number of loops the workflow ran through (We needed to check frequently but the task setting the Boolean value frequently wouldn't be submitted until weeks or months later.) Having a "pause until variable is set to XYZ value" would have been very helpful.
-
27 votesOpen for voting · 1 comment · 5 - Nintex Workflow Cloud » Workflow Designer · Flag idea as inappropriate… · Admin →Tessa
supported this idea
·
-
25 votesTessa
supported this idea
·
-
31 votesTessa
supported this idea
·
-
8 votesTessa
supported this idea
·
-
3 votesReleased · 0 comments · 5 - Nintex Workflow Cloud » Workflow Designer · Flag idea as inappropriate… · Admin →Tessa
shared this idea
·
-
153 votesOpen for voting · 18 comments · 5 - Nintex Workflow Cloud » Workflow Designer · Flag idea as inappropriate… · Admin →Tessa
supported this idea
·
-
3 votesOpen for voting · 0 comments · 5 - Nintex Workflow Cloud » Workflow Designer · Flag idea as inappropriate… · Admin →Tessa
shared this idea
·
I just realized this needs some clarification. My team reports task form links to SharePoint so that our users have access to them in an all-encompassing dashboard. The tasks in NWC do have a form URL variable associated with them. However, it is impossible to report them to our SharePoint list. We cannot use an "update item" action directly after the task because we need the link reported before the task is completed. We also cannot use a parallel path to report it because the form URL variables will not transfer information to the other path. We currently use API to get the form links in the background on a parallel path, but it would be ideal if the existing variable was able to transfer to a parallel path.