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

Question

Question

Linking Changing Template Color

asked on August 31, 2016

Hello,

 

I am creating a link between two separate templates in our LF repository.   When I do this LF automatically changes the color of one of the templates to a different color.

Picture 1 shows the 2 test files to be linked, one template is using green, the other is using pink

 

Picture 2 shows that once linked the pink template has been changes to yellow

Picture 3 shows that the other linked document did not change color and is still green

What would cause this? and how to I fix it?

 

Thank you,

Darren

0 0

Answer

SELECTED ANSWER
replied on August 31, 2016

This is a bug that was fixed in version 10 of the client (reference# 128461).

0 0
replied on August 31, 2016 Show version history

I like this color change option though. Like an active contract is green but inactive it changes to red. That would be awesome. I am probably asking for too much.

0 0
replied on August 31, 2016

Hi Chynna, easy to do, you create two Templates with the same Template Fields, but you assign each Template your Color of choice (appears in the top right of the Template Properties. Then you create a workflow that watches the field where the status is, if the Status is Active, assign the Template with the Green Color, if the Status changes to InActive, assign the Template with the Red Color. As the fields are the same the metadata just rolls between templates. FYI, in Webaccess the Folder or files color doesn't change, but a colored bar appears to the left of the Folder/Document.

0 0
replied on August 31, 2016

Hey Steve,

Seems like this might cause confusion for the simple users. For searching purposes, how would the user know if the document was Active or Inactive. The point of the colors would be to notify them before opening the document. Remember these are simple users who know template search but not advanced. I feel if you take them in too deep you might lose them

Then from an Admin view this might be hazardous. Maintaining both templates might be a problem. If security changes or adding/deleting fields you would have a potential breakdown. Especially someone who might solely depend on Laserfiche for contract management.

This would be a cool workaround for one document type but possibly 5-6. That could easily get out of hand. smiley

1 0

Replies

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

Sign in to reply to this post.