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

Question

Question

Entry path of an emailed .lfe shortcut

asked on January 16, 2020

Hello, I have a user who is emailed several .lfe shortcuts to combine into a pdf to be delivered to regulatory bodies.  The user needs to be able to get each entry to combine into a file.  Copies can;t be emailed since they exceed our servers maximum mail size.  Currently, to find the entries, they open the .lfe in laserfiche document viewer, and then select  File>new browser window to get to the entry.  There has to be an easier way to identify the path of the entry in an emailed .lfe shortcut.  Right?  Any recomendations for this activity?  Thanks!

0 0

Answer

SELECTED ANSWER
replied on January 21, 2020

That's fair, thanks for explaining it.

And no, there isn't a good way to get the path of the original entry from the shortcut. Some of it is by design because the main point of shortcuts is to make it easier to make documents visible to a user who may not (or should not) be able to see the entire path.

I'll pass the use case along and we'll look into how we could make this easier in the future.

0 0

Replies

replied on January 17, 2020 Show version history

Rather than spending human time menial tasks, use workflow to combine the documents and email that.   Quick and dirty mockup below.

1 0
replied on January 21, 2020

Thanks for the reply.  A workflow could do this task if we changed the way the persons performed their work.  Something I am still working on.

Besides the specific process, the issue I am trying to resolve is how can we discover the repository location of received shortcuts? Is there a way to do that?

0 0
replied on January 21, 2020

The LFE file itself is just a very simple XML file that contains the repository name and the entry ID, so it does not have any of that info.

Can you describe their process more? Why would they need the original entry paths? The shortcut opens the document, so they can copy the pages into the combined document.

0 0
replied on January 21, 2020

The documents are not always paged documents, for example an in progress word file or excel file.  The process is basically that one user, which won't enter metadata or generally increase their administrative work, sends a collection of lfe shortcuts, comprised of many different file formats, including MS Office documents, to another admin to be combined into a single file for printing and delivering to various citizens.  

I know procedurally we could do many things to modify this process and account for the issue.  The process isn't entirely relevant to my question. 

Lets say someone sends you an lfe shortcut informing you the document is filed in the wrong location, or you are trying to set securtiy access for a document and the person only has the shortcut, and you manage security based on folders/entry paths.  I was really hoping that there is a faster method to navigate to the true entry path than opeining various browser windows or XML editors + searching.  It appears as though there isn't.

So far I can obtain path information from an lfe shortcut by 1) searching based on the entry id and viewing the path property/column; and 2) opening the entry in document viewer, and opeining a new browser window from that document viewer window.

I was curious if I was missing some other method.

0 0
SELECTED ANSWER
replied on January 21, 2020

That's fair, thanks for explaining it.

And no, there isn't a good way to get the path of the original entry from the shortcut. Some of it is by design because the main point of shortcuts is to make it easier to make documents visible to a user who may not (or should not) be able to see the entire path.

I'll pass the use case along and we'll look into how we could make this easier in the future.

0 0
replied on January 21, 2020

Thanks for the reply!  I do agree the better solution is to modify the process in the specific case, and the infrequent times I need this information, it isn't particularly onerous.  If there were a way though....

Have a great week!

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

Sign in to reply to this post.