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

Question

Question

Weblink 9 Columns for non-client users

WebLink
Updated August 12, 2019
asked on March 20, 2015

Hey guys,

 

So, I know that weblink uses the XML profile settings to generate the columns for users who have a license for the client, and that works fine.  We have an issue where we have a bunch of users that just use weblink for searching (we have a public portal with concurrent licensing).  These users have a windows account setup in the LF admin but they are retrieval only and can only use the weblink site. 

 

Anyways, these users have no attributes when I check them in the admin console.  I have a default setup for the Everyone user that has the columns I want, but these users appear to ignore those settings.  Regular client users (even when using weblink) seem to work fine.

 

Is there any other way to specify what columns come up by default when someone goes to weblink?  I know it can store it in a cookie after they've set them up, but the ones that come up when someone logs in for the first time (and if the everyone user is being ignored) must be modifiable somewhere in the weblink aspx or css pages?  

1 0

Answer

SELECTED ANSWER
replied on March 20, 2015 • Show version history

Please try the following:

  1. Log into the repository using the Laserfiche Client. Any user should be fine.
  2. Configure columns in the manner of which you want it set for the WebLink public portal users.
  3. Close the Client and reopen it. Log back into the repository as the same user and confirm the column profile remains what you want it set to.
  4. Open the Laserfiche Administration Console and look at the attributes for the user that you used to set the columns in the Client.
  5. Confirm that there are four attributes total for the [XmlColumnDisplay] and [XmlColumnProfiles] subsets.
  6. Multi-select those four attributes and export them as an .xml file to someplace like the Windows desktop.
  7. Import the attributes from the .xml file created in step 6.
  8. Go into the Windows Accounts node and view the attributes for one of the public portal users. Make sure there are no [XmlColumnDisplay] or [XmlColumnProfiles] type attributes.
  9. Open a new web browser window and clear cookies (or just the WebLink cookies).
  10. Log into WebLink as the Windows user from step 9.
  11. Confirm if the columns are correct or not.
2 0
View 1 previous reply
replied on March 23, 2015

Hey Alex,

 

This didn't work unfortunately.  The attributes for all of the public portal users are all blank, there are none for any of them.  I tried putting the 4 attributes in the Everyone user, which works for people logging in using the client or weblink if they have a license but not for the public portal users.

 

0 0
replied on March 23, 2015

Hi Shaun,

Have you tried doing an IIS reset on the web server? Otherwise, it takes about 10 or more minutes before WebLink detects column attribute changes. Please see this video for a brief demonstration of setting columns in a Rio environment when using Laserfiche 9.2.1 with WebLink 9 and public portal users.

1 0
replied on March 23, 2015

Hey Alex,

 

That worked!  Wow.  The only thing I was doing differently before (that I can think of) was I didn't have the 'HasMigrated' pieces of the XML imported into the Everyone user.  I only was using the 'Data' pieces (Display and Profile).  Would that have done it (in combination with the IISRESET)?

 

0 0
replied on March 23, 2015 • Show version history

That's great, Shaun. The "HasMigrated" attribute is needed because WebLink checks that first to see whether it should look for the new XML attributes or the old attributes.

Also, WebLink 9 can only automatically "migrate" the old column attribute to the new XML column attribute if they are set directly on the trustee and not the Everyone group.

The IIS reset is just to make WebLink detect the attribute changes immediately instead of after 10+ minutes.

We'll look into clarifying this information, perhaps in a knowledge base article.

2 0

Replies

replied on March 23, 2015

I have tried the steps outlined here and have not been able to get them to work.  If anyone has succussufully configured this please update this with the steps you took. 

We are using windows authenication to login to Weblink 9 with the grid view. 

2 0
replied on March 20, 2015

Hey Shaun,

 

I used Wes's instructions over in this post for our public user account and it worked great. We use a public portal 2 CPU unlimited license tho so I'm not sure if it's handled differently but it's worth a shot to try to apply to the accounts you mentioned.

 

Cheers,

Carl

1 0
replied on March 20, 2015

One thing to note is that when you set up users for authentication based on AD group membership, users won't have an account listed in the administration console until they've actually logged in once and the Laserfiche client applications need to store something in it - such as user attributes. Since items aren't being stored for these users, a user listing never gets created for them. You can always go ahead and create one yourself, so long as you set authentication to inherited. 

All that said, I would expect them to follow the settings on the Everyone group. Are you sure they don't already have saved settings in their cookies? That would take precedenece. 

1 0
replied on August 12, 2019

Hello Justin,

 

Trying to follow up on your reply.

If a Weblink user has set columns view, via Weblink, than they would need to manually remove them (Cookies) in order for column attributes to be set at the User Level in the LF Admin Console correct.

 

Also- If a Windows account has been synced in the LF Admin Console, but they have not logged in, the should have no attributes and get whatever the Everyone Group shows correct?

 

Is there a way to override the Everyone group and just give specific user column view attributes?  Our customer has a small subset of user who they would like to bypass the Everyone group to push out the column view attributes to just these specific users.

 

Thanks and hope I make sense,

Jeff Curtis

0 0
replied on March 20, 2015

Thanks Carl, the issue we have is that we are using this for windows accounts internally so everyone has their own login.  We have well over 100 people that are using weblink with their own username/password and don't have regular client licenses.  These people don't seem to inherit the everyone user's attributes (in fact they have no attributes at all on their account when I look at them in the admin console).

I may be able to manually insert an attribute but then I'd have to do it for each account so that's a pain and hard to maintain moving forward.  Obviously doing it on a group level or something would be better but doesn't seem to work for them.

I wonder if there is some sort of batch attribute editor or script or something I could use.

0 0
replied on March 20, 2015

We have them listed under 'Windows Accounts', not using LDAP.  That was how it was setup by the consultants.  I've gone in and checked, none of the 'unlicensed' users have anything set at all in their attributes, but they have logged in to weblink and it shows their login and logout times.  Even selecting 'show system attributes' they're all still blank.

 

I've tried wiping all cookies and complete internet history from their browsers, no difference.  The reset options and restore defaults options in weblink9 don't seem to do anything for them, the only items that come up by default are 'Page Count' and 'Template Name'.  When I push the restore defaults button on my own user on weblink (and I have a full licensed user account) I get all the defaults from the everyone user.

 

 

0 0
replied on May 20, 2015

I have followed the steps as well however, when I am on step 5, I only have 1 attribute that was listed.  These steps are not working for me.  

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

Sign in to reply to this post.

Details
Related Posts
Loading ...