
- Post History
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on ‎08-05-2019 08:37 AM
As of release LONDON Vanity URL has moved to Custom URL:
Here are the steps for custom url:
1. Activate the Custom URL Plugin:
Enable custom URLs to be set up on your ServiceNow instance. You can activate the Custom URL plugin (com.snc.customurl) if you have the admin role.
Before you begin
Role required: admin
Procedure
Navigate to System Definition > Plugins.
Find and click the Custom URL plugin.
Note: Do not select the Custom URL - Internal plugin, which is an internal component for scripted custom URL APIs.
On the Custom URL record, click the Activate/Repair related link.
In the Plugin Activation window, click Activate.
When the Plugin Activation window reopens with a message that the plugin is activated, click Close & Reload Form to stay on this form.
In the Plugin Files related list, find the following property, and change the setting value:
Option Description
glide.customurl.enabled To enable custom URLs, set the value to True. By default, this property is set to False, which means that you cannot associate a custom URL.
Note: To disable this feature, set this property back to False.
Click Update.
2.Create a new Custom URL:
*IMPORTANT: Must be the same as existing Vanity URL.
Add a custom URL to your instance configuration to use instead of your ServiceNow designated URL.
Before you begin
Role required: admin
You must have purchased or registered a URL before adding the custom URL to your instance.
Procedure
Navigate to Custom URL.
Click New to associate a new domain name.
Choose a custom URL to set as your instance.
Fill in the appropriate fields:
Option Description
Domain Name Fully qualified domain name (FQDN) of the custom URL.
Note: If the custom URL is 'https://servicenow.acme.com', enter 'servicenow.acme.com' as the FQDN.
Is Instance URL Checking this box enables this custom URL for all outbound URLs. Only one active custom URL can be the instance URL. To enable this setting, click the 'Set as Instance URL' button on an active custom URL. This setting activates the chosen custom URL and removes any other custom URL previously set.
Status :
Status of the custom URL record. Once the status shows as 'Active', the custom URL is provisioned and ready to use.
[Optional] Service Portal Choose the service portal to redirect users when they access your instance using the custom URL.
A custom URL should activate within six hours. Polling for custom URL job completion occurs every 30 minutes.
Note: There is a poll button for manual polling an in-progress custom URL job.
When complete let support know so that a change can be completed for System admin team to remove the vanity url.
Thanks,
DeanP
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Question on this: can a portal have a different custom URL domain (https://companyASubsidiary.com) from the instance custom URL (https://companyA.com)? Or must they both be in the same domain? Thanks!

- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Hi Alex,
Ive multiple domains in use for a specific portal.
See the following information.
Dean
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Thanks, @deanproctor. So my understanding from that post and the docs page is that as long as the ServiceNow customer owns the domains, manages the DNS properly, then it can have different domains (not just subdomains) (e.g., companyA.com, companyZ.com) for different portals (1:1), but still only one domain for the instance (e.g., companyA.com, but not companyZ.com). Is that how you understand it?

- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
That is correct.