The right approach depends on what the three URLs are. I’m assuming they are portal URLs such as /sp, /hr and /csm, and that you want them all to land on one portal, for example /esc.
- From the Xanadu release, ServiceNow offers a Deactivate a portal and optionally redirect to another portal option. Apply it to each of the three portals, with your target portal as the redirect, rather than using the older workarounds. A community article says the older Page Route Map method became obsolete once this arrived.
- If the three are different custom domain names, add each one under All > Custom URL > Custom URLs and set the Service Portal field to the same portal. The domain’s CNAME record must point to your instance.
- If users arrive from the login page, the default landing portal comes from the property glide.entry.page.script and the SPEntryPage script include. Community answers show it can point to another portal’s URL suffix. Editing the script include is a customization, so test it in a sub-production instance and keep it in an update set.
- If you only want some users redirected, community members use a UI script that checks the user’s role through GlideAjax before redirecting. This is a workaround and needs testing for each portal page.
If you meant three different kinds of links, such as knowledge, catalog and ticket pages, tell me the URLs and the target. The right method differs for page links and portal links.
Sources:
