PDA

View Full Version : Direct link (URL) for Workspace or Worklist possible?


hubbadubba
10-14-2007, 07:40 PM
Workspaces and worklist are a dramatic improvement from the 2.X 3.X days.

But is there a formula I can follow to generate a unique URL for a particular group workspace or a support rep's worklist? I'd like to incorporate these links in the personalized portal pages our reps use.

jstanden
10-14-2007, 09:39 PM
Hey there!

Yeah that's possible, though at the moment the direct URLs aren't very intuitive.

For group workspaces the syntax is currently:
http://localhost/cerb4/tickets/workspaces/team/2

Where the "2" is the unique ID for the group, which can be found in the URL for the group's Control Panel link.

We should probably improve this to look more like:
http://localhost/cerb4/tickets/workspace/Dispatch
http://localhost/cerb4/tickets/workspace/Sales

I added the improvement to the roadmap here:
http://www.wgmdev.com/jira/browse/CHD-223

Thanks!

hubbadubba
10-15-2007, 07:56 PM
Thanks for the quick reply Jeff- that works fine- except the syntax is actually http://xxx.domain.com/cerb4/index.php/tickets/workspaces/team/4 - note the insertion point of index.php

hubbadubba
10-15-2007, 08:22 PM
Also a problem with using this as a quick jump to their worklist- if they aren't logged in, they are taken to a bare-bones error page. "Access denied. Session expired?" is all they see.

Can this take them to a login screen that will redirect them to the worklist url they originally used?

And will that be cookie based? I'd like to use Cerberus embedded in our company site using inline frames, so I don't think that's possible if cookies were needed.

EDIT: I see you already are addressing that in the roadmap notes, though it's unclear if an embedded site like ours will have problems: http://www.wgmdev.com/jira/browse/CHD-223

jstanden
10-24-2007, 10:10 PM
Hey there,

Yeah the redirect issue on no-session is already fixed in SVN.

It doesn't depend on cookies, it uses the URL string. The IFRAME should maintain its own URL with the backend so you shouldn't have a problem.

As for the URL needing 'index.php/', it's not really wrong -- it depends on if you're using .htaccess or not. I'll pretty much always write URLs in examples without the superfluous 'index.php/' just because it's cleaner/easier. ;)