For whatever reason since upgrading to the latest version of Laserfiche Client, Admin and workflow, latest updates (9.2.0.167) it does not run the items inside the for each value each time the wf runs. This worked fine for about a year prior. It just skips the steps inside and completes the wf. Other times this works just as designed. Any ideas?
Question
Question
I have a for each value in my workflow which works some times and not others
Replies
where are you getting the values from that you are using in the "For Each Value" loop?
Have you Tracked tokens before that activity to see if the tokens you are using have multiple values?
I would try and determine that multiple values are being sent to the activity in the first place. If it is in-fact just not going through that loop, and I confirm the values are set properly, I would try dividing that portion of the workflow out, grouping the current activities into a sequence and disabling it, then adding an "Invoke Workflow" in its place. Make a new workflow and manually set-up a similar series of activities as you just disabled, so that you can use it within the overall process. If in testing you find this still does not resolve the issue, then you may have a bigger problem.
One last thing, you should double check that no messages are being generated, or any events in the event viewer when you find these workflows are not acting as they should. Also, be sure to try republishing the workflow in its current form now that you are on a new version of Workflow. I would also give exporting and importing a backup of the workflow to see if that resolves anything.
Hey Eric,
I'm having trouble replicating this issue - what are you putting into the For Each Value? Multiple things, or a single multi-value token? What are the activity sources of the tokens? Is there anything in particular that you can think of when it runs the For Each Value as opposed to when it doesn't?
there are no messages being generated. There are definitely multiples values in the field I can see this from my test doc in LF Client. I also disabled that and created new for each value, then tested that and created an entry and that ran fine. This is sporadic. I found another thread this morning for the same exact issue, "Workflow: A for each value activity only sometimes works".
I believe there to be a bug. I ran in to a similar issue last week which I just found a workaround for but not resolution.
Tracking Tokens. For whatever reason it does not want to iterate through the multiple tokens. It only ran through one, when there was 2 or more in the same field.
Is it maybe that the tokens are inside one line of the multi-value, like a character return is inside the value for the first item, so instead of what you are visually seeing as two lines, it's still all contained in the index [1]?
As a test, add an assign token value for a new token with the value being for the token you use the "For Each Value" activity on. Then use the token editor to get the value to be whatever is in the first index. Then make sure that is tracked by your token tracker. If you still have two items in your new token, then it isnt storing those two lines as individual values in the token,
Track tokens records all values of multi-value tokens. There will be only one row in the token table, but the Value column will have all the values.
It is completely random that it works or doesn't. I am putting values into to single multi-value token which I am grabbing with the for each value.
Here is what my workflow looks like.
There is not enough information to troubleshoot. What are you iterating over?
Does this field start out with one value, then you add more with the 2 Assign Field Values activities before the For Each Value loop?
This workflow kicks off each time a new piece of Equipment is entered. I have a seperate dynamic field which gets a list of equipment from SQL, once selected an update field is selected and the doc is saved. save kicks this wf off. The wf above then runs. It updates the field values and then runs the for each value. Point being, this worked prior to upgrading tot he latest version, just as the question that i mentioned at the beginning of this thread mentioned. Now i I need a a fix for this in wf designer or a fix/ workaround.
The above workflow is iterating through %(RetrieveFieldValues_Equipment Serial Number_All).
Sorry, that's not a lot clearer without knowing the template structure and what fields are involved in the activities and updates. How many values are in the Equipment Serial Number field at the time Retrieve Field Values runs?
(If it would be easier to look at the workflow directly, please open a support case and attach it)
There can be one or than can more multiples, it really doesn't matter. It MIGHT run the for each value and it MIGHT not. It is just not consistent. I will open a support case.
I have started case # 164206.
It doesn't appear to be iterating through each value. When i run the workflow on the same document, but add a value to the m-v field, then it doesnt want to work.
Dears,
was that solved? I am facing the same issue.