Remember Browsertree location on timeout

kkamath

Hi,

Looks like issue with timeout. Browsertree location navigation path is not being set after logging in from session timeout. The default cabinet node is being selected on return from timeout. This was not in 5.3 but happens in 6.5. On looking at certain form listners, TimeoutHandler form listener is being used in 6.5. Is this the cause for browser refresh to default cabinet. Is there some kind of configuration to be done to rectify this?

Thanks,

kkamath

Francois Dauberlieu

Don't forget that between 5.* and 6.5, there are some major changes in the technology, for example, in DA, you can;t change the Next Invocation date/time of the Job (BTW, Documentum support says it works as designed but I think it's a load of bul....)

Could be the same kind of stuff with this one, you should log a ticket with Documentum support.

Also, what you could do as a workaround but that would require customization would be to in the BrowserTree component's class (which you;d have to extend as well as the component's def file), when clicking on a node, you could store which node it is in the HTTP Session or a cokkie for example and then in the onInit, you could read wherever you stored it. If there's nothing, that means you just let Webtop do its business, if there's something, you can then force it to the node saved in your session.

Actually, if you use a cookie, you could even override the default folder when logging in Webtop as defined in the user preferences but that's fetching a bit far now....