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

Question

Question

Feature Request: Access to Document Creation Date through Token Dialog

Workflow Ideas
Updated June 29, 2015
asked on June 24, 2015

We have been working on a workflow that will process documents that already exist in the repository. Part of the re-processing included renaming the documents to match our new naming scheme. The new naming scheme includes in it a date for the document. To get the document date for existing documents, we wanted to use the document creation date. We have since found out that the only current way to get this date is by using the Find Entry activity. It would be great if this information along with other document information was available using the Token Dialog. For instance, we can already get access to the entry id, entry name, entry path, etc.

0 0

Replies

replied on June 29, 2015

The entry name, ID and path are part of the event notification the Laserfiche Server sends out for each user action. So it's, technically, free. Any other information we need to get requires a call back to Laserfiche. And any additional information we keep around means more data in SQL. And given the hundreds of properties an entry could have, it's not really easy to pick a representative set (we've got requests for a lot of them). So we'd rather not retrieve it unless the user is actually using it, which is why it's available as part of Find Entry, but not the default tokens.

0 0
replied on June 29, 2015

Miruna, that makes sense of why it's not there. Could an activity be added similar to the Retrieve Fields activity where it could be setup to retrieve a documents information?

0 0
replied on June 29, 2015

That's basically what Find Entry does. Are you saying that "Find Entry" is not indicative enough of its extra "powers"?

0 0
replied on June 29, 2015

I guess I'm just being lazy and don't want to change the beginning of some of my workflows. Right now some of our workflows get kicked off by a document being placed in a folder. Right now we do not have to iterate through every entry in the folder, because only one is being processed at a time. In this case it would be nice to have an activity that could, at some point in the workflow, retrieve the document details to be used for other things. This way I wouldn't have to recreate the beginning of the workflow to find all entries in a specific folder and then iterate through each found document.

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

Sign in to reply to this post.

Details
Related Posts
Loading ...