Portal and URL Migration Advice
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-22-2025 03:37 AM
Hi everyone,
We’re going through a transition in our ServiceNow environment and I’m looking for some advice and best practice recommendations around how to manage URL construction, both short-term during the migration, and long-term to make things more maintainable.
Currently we have a lot of email templates, events/actions, email scripts, logic (business rules, UI actions) that construct URLs in different ways. Some are hardcoded, some build dynamic URLs using glide.servlet.uri, etc.
The challenge is that we’re changing both our ServiceNow instance URL and our portal suffix/model. During the transition period, both the old and new instance URL will be live, but we want all new URLs, especially in emails and end-user communications — to point to the new instance and new portal.
But the default methods like glide.servlet.uri always point to the original instance URL and hardcoded paths are a trouble to maintain/refactor.
Has anyone dealt with a similar portal and domain migration before? Looking for advice on how to approach this, especially given that we have a lot of existing content that references the old portal and uses inconsistent logic.
Would appreciate any insight into:
How to cleanly manage this kind of dual-environment transition
How to future-proof URL generation going forward
Thank you,
Greg