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

Question

Question

Cloud Workflow - Create new document based on multi-value field group of original doc

asked on March 17

Hello,

I'm trying to come up with a workflow for a Cloud customer that takes documents with a multi-value field group and creates separate documents (with the same original image pages) for each multi-value field group. In the screenshot below, I'd like to end up with 2 documents - each one only has 1 of the multi-value field groups assigned in its metadata.

I'm having trouble figuring out how to assign each document it's respective fields here. Anyone have any insight in the simplest way to do this in Cloud?

Thanks!

0 0

Answer

SELECTED ANSWER
replied on March 17

I'm a little fuzzy on your exact process, so I apologize if I'm way off, but you should be able to accomplish this using a "For Each Value" activity, and then applying an index on the field values, separating each value by "For Each Entry - Iteration".

Does that help at all? Please let me know if I've caused more confusion and I can try to rephrase.

1 0
replied on March 17

Hi Sarah,

Nope, that makes sense, or at least it should. Getting some weird behavior in the Cloud workflow designer where it won't let me apply an index the way I want - it keeps reverting back to "all values separated by" instead of letting me use for iteration token to choose the index position. But that's an entirely different problem - I think your solution is what I needed. 

Thanks!

0 0
replied on March 17

Yeah, it does that. Should still work for you though!

This is how the syntax should look, obviously adjusted to your token/workflow names:

And the index will look something like this:

Let me know if you have any questions and I can try and help walk you through it a little more. :)

0 0
replied on March 17

I'd want the "value at index" option, correct? And the value would be what you have in "all values separated by" field?

Talked to LF Support and the behavior in my video is just a visual bug - as long as I don't touch anything with the index on those values when I modify this workflow, it'll work fine.

1 0
replied on March 17

Good to know it's just a visual bug, I've always wondered why it jumps to the other field haha

But yes, find your "For Each" token in the drop down, then select "Iteration", and you should be good to go.

0 0

Replies

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

Sign in to reply to this post.