redirect / landing page

[poyntzj]

has anyone created a page - say ticket_redirect.do that takes a simple parameter or two and based on the user's roles or lack of, directs

so ticket_redirect.do?type=incident&id=98a3b6cf6f0582c0af665c0d5d3ee431

We have a redirect script that is used when our users logon and ensures that the user is directed to the relevant portal (if non process), but we have an issue in that a number of our sites have sitemame/xxxxx_details.do so that a non process user see's their tickets in the portal style.     (xxxx is either incident, request or order)

The notifications typically send out the standard nav_to.do so a non process user follows the link and will then briefly see the ticket in the process view before being directed to the portal (and not to the ticket as it is not coded in)

I can modify the redirect to do this, but it is non elegant as they still go to the process view before being redirected.   What I want to do is create a page like ticket_redirect.do pass a couple of parameters and have that page determine

process user = yes, goto nav_to.do with the relevant codes

non process user = yes, go to their site / portal calling the relevant incident_details.do page

as I feel it would look seamless.

I have a couple of idea's, but thought I'd see if anoyne else has done anything similar first

Cheers

[poyntzj]

Not done too much with this except for a POC and then using that for another use.

I created a ui page called take_me_to.do

it needs to have a sys_class_name and record id

it determines who you are, are you a roled user and if so, off you go using nav_to.do,

otherwise it determines which portal you use and what the portal specific page is and takes you to that (if that portal is assessed via SSO and not local authentication)

Not done too much with it as it is part of a notification revamp that we are planning to hit at some point.

Just nice to have a single link that you know will take a user to the correct record with the correct look and feel (for the portal)

[jamesmcwhinney]

In that case, I think you would have to have one master page to parse the URL and redirect to the appropriate page you created to show the given detail record.

parse the record type parameter.

parse the sys id of given record.

redirect to the appropriate page that you created based on what I outlined earlier:

- Approval Record: ess/sysapproval_approver_detail.do?sysparm_document_key=sysapproval_approver, ${sys_id}

- Incident Record: ess/incident_detail.do?sysparm_document_key=incident, ${sys_id}

- etc

[poyntzj]

that is what I have done and you replied to

[jamesmcwhinney]

(If you want the records to appear within your ESS interface, you will not be able to do it without first creating ESS pages and corresponding content types for each record type as I outlined)

[jamesmcwhinney]

that said, if you are using "service portal" then you can forget everything I just said,.. My instructions are for CMS only.. =\