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

Question

Question

For Each Value, Search Repository, Wait condition on found files

asked on August 31, 2016

Hello,

I am trying to use a 'For Each Value' to find, copy pages, and link from my starting entry to existing files.  I want to prevent the starting entry from moving until certain metadata criteria are met in all the entries found in my search activity.  Using the 'Wait for Entry Change' (shown below) is preventing the page copy and linking from happening in all files subsequent to the 'First for Each Value.' While taking 'Wait for Entry Change' out of the the 'For Each' prevents me from using the found entry metadata.  

Is there a way for me to 'hold' the starting entry based on metadata in files found in a Search Repository using a 'for each value' from a  multi value field? 

0 0

Replies

replied on August 31, 2016

Is there anything above the For Each Value?  I assume so since it is not showing an error.  Maybe a token that holds value and then for each token value you are running a search?  May need to see the conditions of the wait.  Is the wait condition on the For Each Value Current Value?

0 0
replied on September 1, 2016

This is expected behavior. Wait for Entry Change holds the execution of any other activities until the conditions are satisfied.

Your Routing Decision 2 and the subsequent Wait for entry Change should be their own separate workflow that you invoke after moving the pages. That way, you finish processing all the documents you found without having to wait for the user actions in this workflow instance.

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

Sign in to reply to this post.