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

Question

Question

.LFE Shortcuts from drag & drop in full client - behavior change between LF8 and LF9

asked on February 19, 2014

In LF8, when a user dragged and dropped a folder to their desktop, it created a .LFE shortcut to that folder, and when they double-clicked the shortcut, it opened a Laserfiche browser window into the folder with that folder as the root. In LF9, the .LFE that's created in the same manner opens the new browser window to the folder, but it is not the root - the full folder tree is also available.

 

I see that now in the syntax of a shortcut, you can set this manually using makeroot='n' or makeroot='y', but is there any way to have drag & drop creation of folder shortcuts default to makeroot='y' instead of 'n'? I have a client whose users want it to work exactly like it did in version 8.

0 0

Answer

SELECTED ANSWER
replied on October 14, 2014

We have added this as a new attribute in 9.2 Laserfiche Client (see 9.2 release announcement). After adding user attribute [Settings]DefaultMakeFolderRoot in Admin Console and setting value to "Yes", .lfe shortcut will open that folder as the root.
For individual .lfe shortcut you want to make exception for, the XML attribute (makeroot='n') can override the default behavior set in user attribute, see Parameters for .lfe Shortcuts

2 0

Replies

replied on February 19, 2014

We looked into the code and it looks like this was a change that was basically a side-effect of a different change, made following version 8.3. I'm curious, why is the root folder important? Is it strictly a performance issue about not having to load the folder tree?

0 0
replied on February 19, 2014

Justin - 

 

The users are a group of financial advisors that bring clients into a conference room to review their portfolios (which reside in Laserfiche), so to prepare, they place .LFE shortcuts to the relevant client's LF folder on the desktop. When they open the shortcut, the client shouldn't see all the other clients' names in the folder list - they should only see their own - even though they don't see the contents of the other clients' folders, they still see the names of other clients, which is a security concern for them.

 

Thanks!

0 0
replied on February 21, 2014

Any chance there's an Attribute we can give users that can change this behavior?

0 0
replied on February 21, 2014

There is no attribute for this currently, we will look into adding one for a future version.

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

Sign in to reply to this post.