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

Question

Question

Despite following instructions, Weblink fails to inherit column attributes. What is the proper method for implementing these changes globally?

WebLink Administration
Updated May 19, 2015
asked on October 1, 2014

I have read the other threads on this topic, and I am still not sure I am doing this correctly. I am attempting to set up columns that will propagate to all users that log in through Weblink. I have set this up as follows:

 

  • I created a brand new user called "testweblink"
  • I logged in to the client as this user and set up the columns the way I want them
  • I cleared all attributes from the Everyone group and imported only the attributes created on the "testweblink" account
  • I then cleared all of my cookies from Firefox and logged in to Weblink as the "testweblink" user after 20 minutes. The columns are still the original, default columns.
  • I verified that the attributes were still set to the default, which has the same columns for all folders and not for each individual folder (I know this is an active bug).

 

Please advise on the proper method of implementing these, if there is some other way of doing this. Thanks for your help!

0 0

Answer

SELECTED ANSWER
replied on October 1, 2014 • Show version history

I just learned that you can manually create the attributes within the Everyone group in a format that WebLink can read. 

Navigate to the attributes for the Everyone group and choose "Add". 

In the Name field, type: [Settings]ColumnDisplay

In the Data field, type: N,number of pixels you wish the name column to be;F"Field Name of the field you wish to display",number of pixels you wish the column to be;  

The N here stands for the Name column and the F is to demote that what is in the parenthasees is a field name. Each system column (Pages, Template Name)  has a corresponding letter (P,T). Note: Not all codes are so obviously correlated.  It is easiest to determine the corresponding letter by adding the column Client 9.0.


This syntax can be continued for as many columns as you wish to display. Make sure to include a semicolon after setting each column. 

 

Here is an example:

 

Note that the attributes you set in this way will not translate to the Client at it now reads attributes in the [XmlColumnDisplay] form. 

1 0
View 2 previous replies
replied on October 7, 2014

Are you able to go a step further with this by specifying which folder to apply the column settings to? (That is you want different column settings for different folders).

 

I tried the syntax:

[Settings]ColumnDisplayXXXX where XXXX is the folder id but this doesn't work. Only [Settings]ColumnDisplay works.

 

Regards

0 0
replied on October 7, 2014 • Show version history

As mentioned in Gareth's question and previously on Answers, WebLink does not currently work with Column attributes for each individual folder (See https://support.laserfiche.com/ForumsFrames.aspx?Link=viewtopic.php%3ft%3d20053 for the original thread on the issue)

0 0
replied on December 19, 2014

Just curious about this as would the following make a difference about custom folder column attributes?

Name:
[SETTINGS]UniqueFolderColumns

Value:
Yes

 

Columns for specific folders (NNNN = Folder ID):

Name:
[SETTINGS]ColumnDisplayNNNN

Value:
F"My Column Name",\d;

 

Custom columns:

Name:
[SETTINGS]ColumnDisplay

Value:
F"My Column Name",\d;

 

I don't think WebLink can actually read the width attributes due to the "Bug". Also, maybe it's case-sensitive in where "Settings" doesn't work but "SETTINGS" would?

replied on December 23, 2014

Using Laserfiche 9.0 and WebLink 8.2.2 the only way I could get this to work right is to actually modify the attributes on the WebLink account.

The original attribute and value showed:

Name: [SETTINGS]ColumnDisplay
Data: N,179;P,70;C,155;L,155;LT,116;Z,128;M,92;XS,138;Y,65;

However, WebLink just didn't like this and would always show the default column listing instead. However, when I manually modified the data value to:

Data: F"Creation Date",50;F"Type",50;F"Page Count",50;F"Last Modified",50;F"Total Document Size",50;F"Electronic File Size";

It worked like a charm after logging out and then logging back in. I did notice though that if I used the Laserfiche Client to do this change then it would revert back to the unreadable data string. It also appears that WebLink doesn't honor the width value as well.

Also, I tried applying this to the Everyone Group and it still would not work.

2 0
replied on December 23, 2014 • Show version history

Hi Wes, 

Just wanted to let you know that we're currently working on an update for WebLink that will address this issue. I'll make sure it covers the additional items you've noted here as well. That said, I'm not sure why the everyone group isn't working for you off the top of my head, but we'll check that out too. 

 

You're correct that width isn't supported, as discussed in https://answers.laserfiche.com/questions/49693/WebLink-Column-Width-Settings. We've got that on our list to investigate, although I can't confirm whether that will be added. Do you have a specific need or use case for configuring the width? 

0 0
replied on December 23, 2014

No I don't Justin but just wanted to add this bit of information just in case someone else runs into the same issue before the updated Weblink comes out.

0 0

Replies

replied on October 1, 2014

Are you referring to this previous thread? You'll need to use Client 9.0 and earlier to set the default columns for that user. That is the last version of the Client that writes the column settings to the [Settings]ColumnDisplay attribute. Client 9.1 and higher writes to the [XmlColumnDisplay]Data attribute.

2 0
replied on March 17, 2015

This feature is available in WebLink 9 which was just released.

WebLink 9 will first check to see if the user has attributes in the new column syntax or the old column syntax. It will first grab the new column syntax and use those as default columns. If the user doesn't have this attribute, WebLink will then check for the old syntax, migrate it into the new XML syntax and use that as default. If the user doesn't have any column attributes, we have provided default columns. As was the case in WebLink 8.2, the user can modify their browse and search columns on a per session basis.

1 0
View 3 previous replies
replied on April 9, 2015

Is there any documentation for this?  This is the current online (that was found) version of the manual, but does not contain how to set the columns in the new version.

http://www.laserfiche.com/support/webhelp/weblink/9.0/en-US/WLA/WLAdmin.htm

 

0 0
replied on April 9, 2015

I was able to find this screencast, http://www.screencast.com/t/bk0xGQ9PNe

 

0 0
replied on April 9, 2015

Yes, that screencast is a good example of how to specify columns for everyone in WebLink. If each individual user would like their own columns, all they would have to do is set the columns up in the Client or Web Access and ensure they are reflected in the user attributes. The screencast shows the user setting up columns, finding the attributes in the admin console, and importing them into the everyone group so if any individual user doesn't have columns set up, they will see the columns set in the everyone group. 

Keep in mind that after these user attributes are set, you need to reset IIS or wait 10-20 minutes for the attributes to be reflected in WebLink. 

0 0
replied on April 9, 2015

I am using version WebLink version 9, LF version 9.2.

The only way I could get the columns to default to specified columns was to use the syntax listed for earlier versions.  The use of [XmlColumnDisplay]data as indicated in the video, did not work.

The use of [SETTINGS]ColumnDisplay did work with the following syntax, F"DBA",50; F"Sales Office",100;
Where "DBA" and "Sales Office" are the names of the respective Fields.

 

0 0
replied on April 9, 2015 • Show version history

I missed something in my example, the first field in the Data string needs to be N,100;  So my full string in for everyone's [SETTINGS]ColumnDisplay is  N,100;F"Sales Office",100;F"DBA",50;

0 0
replied on April 9, 2015 • Show version history

Hi Kristoff, 

When attempting the XmlColumnDisplay syntax, do you have the user attribute [XmlColumnDisplay]HasMigrated with a value of Yes?

0 0
replied on October 2, 2014 • Show version history

Thanks all! I installed an 8.3 client and was able to configure columns that translated to Weblink.

Any plans to fix this in the next version of Weblink?

0 0
replied on May 19, 2015

Is there a fix for this yet ? We are on 9.2 LF and weblink is version 9.0, having a hard time setting default columns for retrieval users on weblink. Yes I have deleted cookies, used different computers even and browsers but the XML or the columndisplay method just does not work ! 

 

What is a sure way to setup a weblink only user having retrival rights only, with default column set ?

0 0
replied on May 19, 2015 • Show version history

There's no additional fix because it's present and works in WebLink 9, as discussed in this thread. If it's still not working for you, you might want to talk to your VAR about opening a support case. To confirm, you are logging in to 9.2 Lf as the user account that public users connect as, correct? 

If it still doesn't work, try clearing out the attributes for the user account as well in the Laserfiche administration console, in case something is messed up in there. 

0 0
replied on May 19, 2015

And as Melanie mentioned above, make sure you have both the [XmlColumnDisplay]Data attribute listing the columns AND the [XmlColumnDisplay]HasMigrated attribute with a value of Yes

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

Sign in to reply to this post.

Details
Related Posts
Loading ...