Redirect users from link to our old portal to our brand new Service Portal
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-23-2019 12:18 PM
So we have put a lot of work into making our new Service Portal and would like to drive the users to it. I have the log in rules working for that but I have questions about what I need to do with the old self service portals that we have. Currently, there are two portals in prod, myinstance/student and myinstance/internal
Where I run into a bit of an embarrassment is we have links to these portals in places that I may not be aware of so I want to make sure that if anyone clicks on those links (or have bookmarks) that it still drives them to my new shiny portal. Is it enough to just set those old ones to inactive or do I need to set up redirects somewhere? If I do need redirects, is this done within the ServiceNow system or do I need to make some DNS changes somewhere?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-23-2019 01:17 PM
Hello Travers,
Look through these posts about re-direction
The thing about redirecting to the Service Portal
6 ways to set up your Service Portal for redirection SUCCESS!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-17-2019 11:10 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-18-2019 10:17 PM
Hello Travers
Please check below link it will help you to redirect.
https://community.servicenow.com/community?id=community_blog&sys_id=cbcda2e9dbd0dbc01dcaf3231f961949
Mark Correct if this solves your issue and also mark Helpful if you find my response worthy based on the impact.
Thanks.
Dhananjay.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-06-2019 08:28 AM
Hi Travers,
We had the same exact requirement and didn't want to create a UI Script that would be loaded much more times than needed.
Since we did not care about having a bit of a delay on our redirect, we used the footer from the theme to run the client logic needed.
On the client controller, we had:
function ($scope, $location) {
var c = this;
var nUrl = c.data.new_portal_home;
// Redirect to homepage on new portal but allow it to be loaded on the Main UI frame
$location.url(nUrl);
}
On the server script:
(function() {
/* populate the 'data' object */
data.new_portal_home = '/portal?id=portal_home';
// Present message for users that have disabled javascript from running in their browsers
gs.addErrorMessage(gs.getMessage('decom.portal', data.new_portal_home));
})();
