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

Question

Question

set default template by folder

asked on July 10, 2014

Can I set a default template at the folder level such that each document scanned into a particular folder will have that default template attached to it ?

I know i can set the default template for 'New Documents' at the user level, but can I specify this on a per-folder level and avoid having to set it at the scanner or individual user level ?

 

thanks,

cb

 

1 0

Answer

SELECTED ANSWER
replied on July 10, 2014

We have been looking at this as well and currently you cannot.  It would be nice that when a user scans to a folder, or imports to a folder, that the metadata would popup with the correct template assigned to that folder.

 

You would have to do this through Workflow.  Though this would only happen after the document is stored.  So they would scan/import the document to the folder, Workflow would run and assign the template, then the user could open it and fill it out.  Not very streamlined but that is what we have done for some of our clients.  

0 0

Replies

replied on September 2, 2015

This appears to be solvable by setting the option in the Thick Client to "Use Parent Folder's Template".  This does not as a result constrain the user by role or job scope.

 

I am not sure if this is apparent or obvious since the original question was lodged - could be some necromancing on my part I know but at any rate this does seem to be a good enough solution.

 

The only improvement now would be the option to present the user with the "Fields" Tab on import (populated with the Parent's Template) rather than "General Tab" in a reliable way - I notice that it seems to do this sometimes but not others...

2 0
replied on July 15, 2016

Hi Will,

 

I've just been looking for this solution and your suggestion works really well - thanks!

 

Now, the only occasional problem is when a template has a required field, and therefore you can't easily apply the template to the folder: because A: you don't want there to be any content in that field at the folder level, and B: you can't apply the template if that required field doesn't have any content.

 

So just to add to the above - if this happens:

  1. Temporarily remove the 'required' tick on the template field
  2. Apply the template to the folder(s)
  3. Reconfigure the template to have the required fields again

 

It's a bit 'ugly' (since you'll have a folder with a template that has empty 'required' fields) but it works.

 

Another workaround it to use a default value in the required field, but in many cases that wouldn't be appropriate since you may want to force users to add/select content and not allow the default through.

 

+1 vote for having this as a configurable option that accounts for the above - it would be preferable and more robust.

1 0
replied on July 10, 2014

I am using the WF workaround.  Was just looking for a more streamlined approach.

Thx much for your speedy response....

cb

1 0
replied on September 1, 2015

Is there any idea of the possibility of an improvement in this area for Laserfiche 10?

 

This is a bugbear for several of my clients and especially one in which the demo of the Laserfiche system is alongside a competitive product where the comparisons are easily and often made despite there being considerable respect for both the solutions.

Regards.W

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

Sign in to reply to this post.