Question

Workflow's for each value, adding a conditional decision stops it from moving on

Workflow

Updated January 25, 2016

asked on January 25, 2016

Adding a conditional decision stopped the For-Each-Value from moving on. Why?

The WF was working fine (adding shortcuts to folders based on the multi-value field entries) until I added the conditional decision. Now, when the first branch's condition matches the criteria, the workflow just stops instead of moving on to the next value. The Find Entry tells it what folder to look into. The condition is to look for an entry name that matches the starting entry name and create the shortcut (or not) based on what it finds.

I've seen other WF's set up like this. What am I missing?

For more info on this WF: https://answers.laserfiche.com/questions/89909/Using-workflow-for-automated-filing--Part-II

Thx, Connie Prendergast, Flagstaff County, AB Canada

0 0

Replies

replied on January 25, 2016

If I am reading it right, it looks like you are going through a set of values, looking to see if it exists(Find Entry via At/Name) then want to make a shortcut if it doesn't exist.

In that case, your find entry needs to be before your decision tree as you need that to test which tree to it should go down. Then you set your tree to match EntryWasFound token output to determine where to go.

1 0

View 1 previous reply

replied on January 25, 2016

Thanks, John. Okay, I moved the Find Entry above the Decision Tree. No change.

I think I know what might be wrong. I'm asking it to look inside a folder that hasn't been created yet (the folder trees haven't all been created yet, so the Create Shortcut activity has to create the destination folder before putting the shortcut in it). I will test this theory and get back to you.

Thanks for your help!

0 0

replied on January 25, 2016

Okay, so that may have been part of the problem but not all. I think I'm closer. I now have the Find Entry outside the Conditional Decision and the Condition it's looking for is:

but the results are False:

because this condition is comparing the target folder name instead of the documents in the target folder with the starting entry name.

How do I get it to compare the documents in the folder against the starting entry name?

0 0

replied on January 25, 2016

It's kind of hard to tell what's going on without seeing the settings for Find Entry. If you're getting back a folder from Find Entry instead of a shortcut, then maybe you don't have the full path specified in the activity, including the entry name?

2 0

replied on January 25, 2016

Success! Miruna, you gave me my missing clue! I did not have the full path including the entry name. That's what I was missing. Thanks!!! :)

0 0

replied on January 25, 2016

What do you mean by "just stops"? Did you look in the instance details at the Activities tab for the completed activities? Is there a chance it didn't need to create any of the shortcuts?

0 0

replied on January 25, 2016

It needed to create one... the one I had just added to test with (the value of 377991). I've been adding one new field value each time I test again.

0 0

replied on January 25, 2016

Maybe I'm wrong about what didn't happen? In rethinking it, maybe it did check the seven field values, but ... what entry did it not find that it was expecting?

0 0

You are not allowed to follow up in this post.

Question

Question

Workflow's for each value, adding a conditional decision stops it from moving on

Replies

Sign in to reply to this post.