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

Question

Question

Is there any way to not change the modification date of a document when changing templates or adding fields using workflow?

asked on August 3, 2018

We have many documents that have been scanned into LF through many years.  When they were originally being scanned they did not all get templates or fields assigned to them.  Now I want to use workflow to assign templates and fields to all of those documents scanned in the past.

Using workflow I can make the assignments easily, but is there any way I can do that without changing the modification date of the document?  The modification date shows when the documents were scanned into LF, and I need to keep that as the modification date.  Preserving that date in metadata or something like that won't work.

0 0

Replies

replied on August 3, 2018

I think you are trying to use the last modified field incorrectly.  If you need a field to record only when the last time a page was added or removed that would need to be a user defined field and filled/modified at the time of change.  You potentially could add a hidden field to record the number of pages and on entry change have workflow test if the page count is still the same and if different, then update the page count and the page change fields.

2 0
replied on August 3, 2018

Why do you need to keep the Modified Date to show when it was scanned in?  Doesn't the Creation Date show that?

0 0
replied on August 3, 2018

The creation date shows when the first document was scanned for that folder, but there are likely to be multiple scans of forms filed for a given parent item over the years (they are forms with different assigned numbers and each those forms is in a separate folder under the same parent item folder, like Form 02, Form 03, etc.).  As new Forms with the same number (like Form 02) come in after the first one is scanned then those new scans get copied into the existing document using the LF client.  hen that happens the creation date stays the same, but the modification date changes.  We use that modification date to show when the last one of a particular form was scanned.

We use the LF Integrator's Toolkit to show those Form document scans inside of a third-party application.  We do not want dozens of document names showing under each Form folder which is why we copy them into the one that already exists, but we do want to show when the last one was scanned for that form type.

0 0
replied on August 3, 2018

That could be done if this were a new implementation or if the third-party software hadn't already been developed.  I need to make them more searchable and I was hoping there would be a way to change metadata associated with historical scans without changing the modification date on the scans themselves, but it seems there isn't. 

Is there a way to do this in the DB using SQL?  We have thousands of documents that have not changed in years, but I need to add metadata to them now without making it look like all of them are new. 

 

0 0
replied on August 3, 2018

Again, you are thinking about it incorrectly!  Changing the metadata is changing the document!  To change the metadata without any recorded indication would lead to a very questionable system.  You would not be able to trust the metadata because there would be no trace of who entered it or when.  Can you really say that you want a system that has no way to manage and track who changes things?  I, for one, do not!

0 0
replied on August 3, 2018

You are totally correct about that not being an ideal solution. 

It seems I will have to give up on adding metadata to those historical documents without losing the date on which they were scanned.  I cannot change the way that third party software displays and uses that modification date.  It made sense when there were no associated templates (it started with LF v7 before I was hired), but now we have upgraded to LF v10 and our needs have changed.  Our new scanning projects do have Templates and fields assigned to them when they are created.

Thanks for your replies.

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

Sign in to reply to this post.