You are viewing limited content. For full access, please sign in.

Question

Question

Wait Conditions

asked on June 20, 2016

I am in the preliminary stages of designing a Workflow, and I have a question that would be helpful to have answered before publishing the Workflow and testing it. When configuring the Wait Condition Entry: Path do you set the Path so that it equals the last known folder the Entry was stored in or is it necessary to add an additional condition for every folder the Entry has traveled to? In other words, is it necessary to mimic the Routing Path of the Entry with Wait Conditions, adding a condition for each additional folder the Entry has traveled to? 

I would greatly appreciate the help! 

0 0

Replies

replied on June 20, 2016

last known would be the right answer. 

0 0
replied on June 20, 2016

Entry Path condition is the current path at the time a change is made to the document. Are you expecting the user to move the document to satisfy the condition?

0 0
replied on June 20, 2016

Hi Miruna, 

Thanks for your help! To answer your question, I am not looking for the user to move the document, rather I would like it to be routed automatically using a Route Entry to Folder activity. When establishing Wait Conditions, in order to make them as specific as possible, I was asking if it was necessary to mimic the Entry's routing path, adding a Wait Condition for every folder the Entry has been in, in order to specifically route the Entry to the next folder? 

Thank you again! 

0 0
replied on June 20, 2016

No, you don't have to worry about being specific with paths in wait conditions. Workflow already knows which entry to check and where it is.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.