Question

Use workflow to merge all LF documents in folder to one document

Workflow

Updated May 22, 2024

asked on September 10, 2015 • Show version history

We would like some help to build a workflow that will take all the LF documents in one folder and combine them into one document and placed in another folder. None of these documents have any metadata.

We have used Quickfields to take an existing PDF, separate it into multiple documents to add a stamp. Now I need to take the results of multiple documents in one folder and turn them back into one document for processing in a 3rd party program.

Any help would be greatly appreciated!

0 0

Answer

SELECTED ANSWER

replied on September 11, 2015

Something like this should work:

This example has an Input folder where the separate documents are and an Output folder where the new combined document is created and populated. Let me know if you need to see any of the activities' details, but they should be pretty self-explanatory.

2 0

Replies

replied on September 11, 2015

Here are the properties for all activities, Dave:

1 0

replied on September 11, 2015

That did the trick, Thank you very much!

I had the "Move Pages To" wrong.

0 0

replied on May 22, 2024

Hello,

What was the issue. Im following up the same step and getting this document contain no pages.

Thanks

0 0

replied on May 22, 2024

Is it reporting that the source document has no pages? This whole workflow will only work with documents that have image pages. If your documents are edocs without generated pages you'll get that error.

0 0

replied on September 11, 2015

Thank you very much for the reply!

I would like to see the Move Pages activities if I could please. I keep coming up with Output Folder is not a document. It makes a file in the output directory, but that file is blank and the original files are still in their folder.

0 0

You are not allowed to follow up in this post.

Question

Question

Use workflow to merge all LF documents in folder to one document

Answer

Replies

Sign in to reply to this post.