Question

Merge metadata on drag and drop

Laserfiche How To Version 10 Web Client

Updated November 6, 2020

asked on November 5, 2020

We are using LF Forms for end users to submit information and attachments. Once approved the form and supporting documents save into the repository, it is assigned Template #1. The accountant starts processing from within the repository using Web Access (no client), clicks the document (document #1) coming in, drags and drops on top of a document (document #2) that is already in the repository to merge them together. The existing document in the repository is using Template #2. Both templates share one field for email address. When the Accountant drags and drops the Document #1 over Document #2, the email address field is not pulling over the metadata from Template #1.

There is no workflow since the users is dragging and dropping.

LF v.10.3 - On-Prem

Laserfiche Forms Professional Version 10.3.1.635

0 0

Replies

replied on November 5, 2020

Hi April,

This sounds like expected behavior. The "original" document (document #2 in this case) will retain its metadata and receive the new document pages that you added to it. If you dragged document #2 into document #1, the metadata on document #1 would be retained instead.

My thoughts are to look into the possibility of your accountant dragging document #2 into document #1 instead, or to have a workflow do this step instead, but copy the metadata from document #1 to document #2 before moving the image pages.

Does that make sense?

0 0

replied on November 5, 2020

Reversing the drag and drop removes Template 2, which is the most important data. Basically the invoices comes in through Forms. The accountant needs to merge with the existing vouchers in the system. Both templates are different, the only shared field is email address. We really only need the email address to populate in Template 2 from Template 1. It doesn't seem like drag and drop in browser will work on a workflow action on change.

0 0

replied on November 5, 2020

Sorry, I was under the impression that both templates had just the one field - Email Address. So we can disregard that suggestion.

Is there a way for workflow to identify document #2 based on something about document #1? My thought was that upon creation of document #1 in the repository, you could have a workflow starting condition that kicks off a workflow that takes information from document #1, identifies document #2, copies the Email Address field data from document #1 to document #2, and then moves pages from document #1 to document #2.

Does that sound plausible?

0 0

replied on November 5, 2020

Is there a way to have a workflow based on a user dragging and dropping action? the dragging and dropping from the browser, is the easiest way for the accountants to process. The vouchers have these numbers that are a mile long.

0 0

replied on November 5, 2020

I don't believe there's a super clean way to do that, but one thing you could try is creating a hidden field in the template that will be assigned to document #2. Workflow would compare that field value to the current page count, and if the two values differ, then workflow can assume that the entry change that kicked off the workflow was this drag and drop. Workflow would then update the hidden field value to the new page count. However, workflow would still need to get the email address from document #1, which may not exist anymore in the repository as its pages have been moved to a new document. Even if you kept document #1 as an entry without any pages, I'm not sure how workflow would be able to identify that document, and then subsequently grab the email address field, assign it to document #2, and then delete what remains of document #1.

How does your accountant know which document in the repository in document #2 in this scenario?

0 0

replied on November 6, 2020

April,

One option is to set up a workflow that's started as a business process. So your accountant, instead of dragging and dropping one file on top of another, instead selects the files, or right clicks on one of the two files, and then runs the business process. If multiple files come in all at once, this would make it possible to merge them all at once with a bit of clever workflow design.

Either that, or you could create a workflow that watches for when a document is deleted. That would be the document that's dragged into the other. That would let you have your workflow act on the dragged/deleted document as the starting entry.

0 0

You are not allowed to follow up in this post.

Question

Question

Merge metadata on drag and drop

Replies

Sign in to reply to this post.