redirect / landing page

poyntzj · ‎12-22-2016

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

TrevorK · ‎12-22-2016

When I read through your post, it sounds like the biggest problem is that the links that go out in the email point to nav_to.do and that is ultimately the cause of your problems?

If so, my comment is simple. Run a mail script to alter the link to the appropriate one. We ended up doing that for the Survey/Assessment piece because we customized the page. Here is a snippet of the code:

I might be understanding your problem incorrectly, but if the problem is the link in the emails then you could just fix that and all your problems are solved. Rather than allowing a link that does not work great and attempting to work around it. Just a thought!

poyntzj · ‎12-23-2016

Hi Trevor, the issue is more the clients requirements

As we have a few sites and their branding is different, when we send a notification they only want a single URL and that should always work and take that user - regardless of role - to the right link - process or the right site and link.

I have looked at the Evergreen templates and reworked a lot of that. It will look at each notification, break it down to each user and then update the URL link and any date / times into the correct link for that user and their date / time zone.

Only issue is that it sends out a lot of notifications and we are aware that O365 has some limitations as we have encounterd these with our standard notifications, let alone if we increase x folder.

Some of this update may get pulled back, and the only way I can then think of providing a single link is to create a page, pass the parameters and let it determine where to go next. Still may not be as seamless as I would like, but a lot better than what happens now.

Cheers

jamesmcwhinney · ‎01-25-2017

If I understand what you are trying to do, then we had the exact same requirement.

We wanted to keep end users within ESS, which means if they click a link to their incident (or whatever other record we have sent them) then it should open up with the user friendly ESS frames etc etc.

For Example, have emailed approval request hyperlinks to open the respective approval request within ESS.

Here is what you have to do:

1. Create a CMS page "Portal — Approval Detail" (sysapproval_approver_detail.do) to handle requests to view approval records.

That page contains a content block of type "Show the page's current document".

2. Create a content type "sysapproval_approver" to handle the display of the approval record.

As part of this page, include mobile detection to redirect mobile users to the mobile UI for that record. Otherwise mobile users will see the desktop ESS, which is annoying. Also bear in mind the sysparm_stack so that if the user hits the back button once they get to the record, they will go to the appropriate list with the expected filter already in place.

Here is the content type details:

<?xml version="1.0" encoding="utf-8"?>

<j:jelly trim="false" xmlns:j="jelly:core" xmlns:g="glide" xmlns:j2="null" xmlns:g2="null">

<g:evaluate>

var gr = new GlideRecord('content_block_iframe');

gr.initialize();

gr.frame_name = 'gsft_main';

var recordURL = "sysapproval_approver.do?sys_id=${current.sys_id}${AMP}sysparm_view=ess${AMP}sysparm_stack=sysapproval_approver_list.do%3Fsysparm_query%3Dapprover%3Djavascript%3AgetMyApprovals()%26sysparm_view=ess";

gr.url = recordURL;

gr.sizing = 'expand';

gr.putCurrent();

</g:evaluate>

<g:render_content_block_iframe />

<g:evaluate>

gr.popCurrent();

</g:evaluate>

if(isMobile()){

window.location.replace("$m.do#/form/sysapproval_approver/${current.sys_id}"); //Helsinki Mobile UI

//window.location.replace("nav_to.do?uri=${recordURL}"); // Fuji Mobile UI

}

function isMobile() {

var check = false;

return check;

}

</script>

</j:jelly>

3. Your hyperlinks then need to look like this:

<a href="${mail_script:baseURL}ess/sysapproval_approver_detail.do?sysparm_document_key=sysapproval_approver, ${sys_id}">Click here to view the approval request</a><BR>

jamesmcwhinney · ‎01-25-2017

More detail on this here:

Re: How to get email hyperlinks to open in ESS or Mobile