To ensure Guides appear only where they are relevant, they are internally linked to the visited URL. Some applications use variable components within their URLs.
Example 1: Quality vs. Production Environment
A CRM system might use a URL structure that includes a unique identifier to display information for a quality focussed environment. In most cases the guide is to be made available on the productive environment once available.
The guide was created on Quality and is linked to below URL:
https://quality\.crm4\.dynamics\.com/main\.aspx\?appid=944052eb-2144-f011-877a-6045bd9f3bb9&pagetype=entitylist&etn=appointment&viewid=606eea12-0c33-47d3-96e1-ba1529ee8205&viewType=1039
To make the guide available in Production, you'll need to add the page targeting using regex:
Step-by-Step:
Go the guide and select "Page targeting' from below selection menu.
Add the URL regex corresponding to the productive system and save.
Why Use Regex for Page Targeting?
To ensure that guides appear only where relevant, they are linked internally to specific URLs. However, many enterprise applications include variable components in their URLs (e.g., environment names, unique record IDs). To handle this, regex allows flexible matching across similar pages.
Example 2: Matching Multiple Records (e.g., Contacts)
To show a guide across multiple contact records—even though each has a unique ID in the URL—you can use a wildcard regex:
Original URL:
https://crm4.dynamics.com/main.aspx?appid=xxx&pagetype=entityrecord&etn=contact&id=ae7fbbb6-ffae-ea11-a812-000d3a8b3ec6Regex to match all contact profiles:
https://crm4.dynamics.com/main.aspx?appid=xxx&pagetype=entityrecord&etn=contact&id=.*
This will apply the guide to all contact person records within the same application structure.
💡 Tips
✅ Ensure regex patterns are specific enough to avoid unintended matches.
✅ Always test your regex before saving.
❓ If unsure, consult your development team or use AI tools (e.g., ChatGPT)