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

Question

Question

For Each Entry No Activities with Relevant Data

asked on September 14, 2015

Hello,

I am designing a workflow wherein the workflow retrieves a multi-value field, creates an entry for each retrieved value from the starting entry, copies the pages from starting entry to newly created entry, then for each created entry goes through a series of routing decisions.

I’m having troubles with the ‘For each Entry’ portion.  When I attempt to set the properties for this activity, designer states ‘No activities in this workflow provide relevant data.’  However, based on the LF help file a ‘Create Entry’ should be an activity that a ‘For Each Entry’ activity can work with.  

What is it I am doing incorrectly/should do differently?

 

0 0

Answer

SELECTED ANSWER
replied on September 14, 2015

For Each Entry typically only works with the results of activities that produce listings like Find Entries and Search Repository to provide iteration capabilities. Currently workflow does not have the ability to build an 'ad-hoc' listing of your created entries for you to iterate on. You would have to use a Find Entries after or a search if there was a common criteria between them all. The risk of this approach is that if you are creating entries in the same folder, and its non-empty at the start, you'd grab more documents then you intended. You could maybe do a search based on the common criteria and creation date, but still a small chance of extra results.

Now, to actually help you out, depending on exactly what you are doing in 'For Each Entry 4', I'd probably say this is a common case where an Invoke Workflow inside your For Each Value at the end will work better for you in the long run. Invoking a workflow to handle your created entry will allow you to run all the created entries in parallel instead of constantly having to reiterate over the list. 

 

3 0

Replies

replied on September 14, 2015 Show version history

Hi Darren,

 

Have you checked that you have set the create entry activity to the current value and not the starting entry?

 

It could also be that you have the for each entry inside the for each value....indecision

1 0
replied on September 14, 2015

Ed,

Thanks for answer, explanation, and solution; much appreciated.  

I ended up isolating the sections into two separate workflows as per your suggestion, and used differentiated starting rules for the starting vs. created entries in-place of the 'invoke' flow. I am using the same folder for starting and created entries and worried about creating an endless loop with the invoke.   

1 0
replied on September 14, 2015

Chris,

The 'Create Entry' activity is set to 'Current Value.'  Also, moving the 'For Each Entry' outside the 'For Each Value' yields the same the results

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

Sign in to reply to this post.