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

Question

Question

Web Client Custom Tab Issues- BUGS?

asked on October 1, 2019

Hello everyone,

I am taking my first stab at using a custom tab in Web Client.  I have read a few posts that are almost 2 years old and the issue still does not seem to be resolved. Looking for any kind of answers if it has been resolved or if it is still an issue and if it is a bug being worked on.

 

I want to make a custom tab available only when a document with a specific template is opened and I want the tab to show only in the document viewer (not on folders).  It seems that this does not work.  You have to have both folders and document viewer checked to get it to show up on a document.

 

Has anyone found how to make this work yet? In my screen shots I show what my pane looks like when opening a document with the specific template for just document viewer and for both folder and document viewer.  My repository is 10.3.

 

Along the same line, I want to send an email (internally) through workflow with a Web Client link where it opens with the custom tab showing. In creating the URL link I can see where to change what tab opens but 1) it opens to my default order no matter which tab I select to have opened, and 2) it does not allow me to choose any custom tabs.  Is this also a bug?

 

Thanks

Jennifer

CustomTabDocView.png
CustomTabFolderView.png
0 0

Replies

replied on October 1, 2019

I hope that this is on their fix list but it has not been fixed yet.  We use quite a of embedded forms with custom tabs and its a real issue at multiple clients.  Users have to be trained on what tab they should be on or there are too many tabs which leads to a full action bar.

Only thing I could suggest is I have gone to trying to use one tab if possible.  Its certainly not possible on all processes but usually the tab is tied to a forms url.  You can treat the form name as a variable in the template and pass it with syntax. 

So document comes into Laserfiche, workflow determines what it is/does its thing, then assigns a field value with the name of the form (or whatever variable you are trying to pass).  Then the tab URL has the value from the template.  So tab URL is http://server/forms/formname and the formname is on the template of the document.  Then one tab will show multiple forms.

0 0
replied on October 1, 2019

Thanks for the added information.  I am only working with 1 form in a custom tab right now but will definitely keep your work around in mind.

I would really like to get it working in workflow where I can set which tab is showing when the document opens. That does not seem to be working at all. 

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

Sign in to reply to this post.