nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to customize for user controllable entry points

Robert_Davies_(unlondonadmin_-_(deleted))

Hi.We want to be able to assign different users different entry points into Livelink. That is when a user requests the base url http://somehost/livelink/livelink, we would like some users to get the Enterprise WkSpc, some their Personal WkSpc, some perhaps a project WkSpc or maybe a different type of workspace (if we figure out how to do it).I have traced into the WebDSP:RequestHandlerSubsystem:Dispatch and found out how it assigns the func='' when it isn't already supplied.Unfortunately this means I also discovered that the login state isn't processed at this point, hence I don't know which user is using the system, hence I cannot determine where to send them.Does anyone have any good idea's? My first thoughts are to create a dummy request handler that ensures the user gets logged in and has a context, then re-routes them to the appropriate handler, e.g. Enterprise.Home, MyWkSpc.Home, and so on...Any thoughts?Best regards/matt.

Find more posts tagged with

Comments

Robert_Davies_(unlondonadmin_-_(deleted))

To follow up:I have created my own handler called Dynamic.Home which uses the Login info (using a simple lookup table at the moment) to return a dynamic starting point. In the future I will use an attribute of the user & allow them to customize.My problem is that I need to replace the WebDSP:RequestHandlerSubsystem:Dispatch() method with one that defaults to calling the Dynamic.Home handler rather than the default handler.Can anyone advise me on how I do this?Best regards/matt.

Robert_Davies_(unlondonadmin_-_(deleted))

Well i'm not sure if anyone is listening but maybe this will be useful to someone following after...The approach of registering a new Subsystem seems to work, however there is one problem. It would appear that not all of the Request Handlers get registered with my registry -- possibly because they are in OSpaces that get loaded between WebDSP and me.Is there a good approach to ensure that my OSpace is the next one to be loaded? Or should I just copy the contents of the existing registry when I swap over the subsystems?Best regards/matt.

Robert_Davies_(unlondonadmin_-_(deleted))

Well i'm having an interesting thread here all by myself ;-)In my Root startup I now copy the contents of WebDSP's RHS registry before it get's abandoned when my Cuckoo's egg nests in the WebDSP nest. This works great!There's still a problem though. When I unlock my OSpace the value of the global$WebDSP.RequestHandlerSubsystemis somehow broken: "This Object does not exist"My request handler object has been destroyed! Relocking the OSpace doesn't do anything useful. I could run Root.Startup to recreate my temporary and install it, however all the request handlers registered with my registry have been lost.I suppose what I am after is a method that gets called when the OSpace is closed. That way I can gracefully resynchronize the WebDSP registry and reinstall it's RequestHandlerSubsystem.Can anyone help me? Or are you all still in bed? (it's 12:23PM here!)Best regards/

Mike_Oliver_(ollie_(Delete)_137504)

Did you try simply changing the "DefaultRH" entry in the opentext.ini? You could then store the user's preferred entry point either in kini or the extended data assoc for that user's Personal Workspace Node(easier there because you can put the preference selection in the info screen for the Personal Workspace.

Robert_Davies_(unlondonadmin_-_(deleted))

Hi Mike.No I didn't, but it sounds much easier than what I amdoing. So in my case I would simply make:DefaultRH = Dynamic.Homeand then in the Execute(), read the data from the personal workspace node?This sounds good.Best regards/matt.p.s. Glad to see you here...

Bill_Breslin_(bbreslin_(Delete)_1351824)

Our approach may seem a little radical, but lot's of good things happen in terms of developing other non-livelink applications if you use it. Our user database is in Oracle. Our maintenance app for adding a new user also calls LAPI to add the user to the livelink db. All users logon to our ASP script and we verify against our database then pass the information over to the Livelink logon script. We've modified that logon script so that we send to the script the place in livelink or even an alternate home page where we want the user to go next after a successful log on to our one intranet system and to livelink.In this way different users are sent to different places inside or outside of livelink. Our extranet users see an entirely different view of the intranet world than our trusted folks.

Mike_Oliver_(ollie_(Delete)_137504)

That is a good idea, I will have to try it. I know of a couple more. One is to do a "Save As" of the Login html page as you are loggin in. This local copy of the Livelink Login page will also have the "nextUrl" embedded in it and that can take you anywhere you want. Put that local copy in your browser favorites and poof, login and start where you want to. Another is to create special directories in your http server, in each directory place an Index.html or default.html or default.asp(forthat matter), each one can have different customized content and a Login form to take you someplace in Livelink. It can even log you in as a specific user, i.e. Extranet user, Partner company, etc.Then you can restrict access to those pages using the standard http server access controls, and you can then expose and control what you want.

Robert_Davies_(unlondonadmin_-_(deleted))

Hi Ollie.Can you outline what steps are necessary to add a custom tab to the Info page of an existing object, i.e. the Personal Workspace.I can add a command to the function drop-down using the WebNodeCmd & WebNodeAction but am not sure how do make a tab appear.Any suggestions?Matt.

Arlene_Elder_(GlaxoWellAdmin_(Delete)_1421884)

Orphan Home:HomeRequestHandler:Personal and name it.Set fEnabled, fHomeLabel, fHomeOrderfHomeOrder = 1000 puts it at the far right.This should get you started. If you dont have a manual from the builder course you should consider ordering one. This is from Section 11

Arlene_Elder_(GlaxoWellAdmin_(Delete)_1421884)

This ia a good solution. We will implement something similar.You can modify the Livelink login, so you login to a separate DB that does the validation that also contains a NextURL parameter for each user. If the user hasn't specified a next URL, use the one in the DB is used. Otherwise send them to the NextURL they requested. If you have NT IIS you can use Challenge Response to the separate login page created to implement an autologin feature.

Judith_Oliver_(submeppuser3_-_(deleted))

Maybe I'm missing something regarding what you are trying to achieve, but it seems to me that any user can establish a "custom entry point" simply by setting a favorite or bookmark in their browser. If you log into Livelink and navigate to your desired starting point, set the favorite / bookmark at that point. Make sure the menu bar is OFF when you do this. Then anytime you start Livelink from that favorite / bookmark, you will get the logon screen, and a successful logon will open Livelink at your custom starting point. Unless you're doing something pretty sophisticated to control how users log into Livelink, this ought to work for most folks.

Robert_Davies_(unlondonadmin_-_(deleted))

I agree for a lot of people this will be fine. However there were reasons why they weren't appropriate here and I suspect that those reasons are not unique.1) When you are using several machines (e.g. work and home) keeping bookmarks synchronised is a pain.2) Our students are using different machines all the time and may not be able to save their bookmarks.3) Some of our users (mainly external ones) are only involved in one project. Being able to start them there simplifies things.The module was very simple in the end, all the difficulty was in learning enough of Livelink to figure it out.Best regards/matt.

CingularUser_1_(x-cingularuser1_-_(deleted))

We don't have any "developers" here who know enough about using the livelink builder/sdk, but following this conversation, it seems we can still implement this. I would just like to know where this "NextURL parameter for each user" is. In the KINI table?TIA,Verna

Liz_Connors_(sunvalleyfoodadmin_-_(deleted))

We just set a few extra cookies on each login page, one storing the user name, the other storing a domain value, we then use a customview.html to check the value of these and JS to redirect accordingly, simple.