Tech Note: Using Relative URLs in Guide Button Actions for apps with Multiple Subdomains
The button action of URL Link in guides is used to take users to a URL. This is the default view for adding a URL to a guide:
But let's say my app uses unique subdomains for each customer we have. So Acme, Inc. customers access the app through acme.testapp.com and OmniCorp customers access the app through omni.testapp.com. Because each customer has their own individual subdomain, using a full URL in the button action won't work.
You might be able to use a relative URL to solve this. In this example, I want to button to take users to the features page. So for Acme, Inc the URL would be https://acme.testapp.com/features and for OmniCorp it would be https://omni.testapp.com/features.
In order to make a guide button action work for both customers, we could use the relative URL of /features in the button action as pictured below.
Using a relative URL allows the button action to automatically pull in the domain the user is currently on, and will simply add the relative path that you place in the URL field to the end of the subdomain.