GPX support for regular expressions?
Hi,
Does GPX support regular expressions beyond a single * at the end of a URL?
Thanks,
Chad
Does GPX support regular expressions beyond a single * at the end of a URL?
Thanks,
Chad
Login to the community
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
We want to trigger a dialog engagement for visits to:
http://domain.com/meetings/ABC123
But exclude:
/meetings/live
/meetings/recap
/meetings/ABC123/edit
We started with /meetings/* in the include list.
When we add these in the exclude list, they are successfully excluded:
/meetings/live
/meetings/recap
But when this is in the exclude list, it is still triggering the engagement:
/meetings/ABC123/edit
So I tried adding this to the exclude list, with no effect
/meetings/[A-Z0-9]+/edit
And then tried using /meetings/[A-Z0-9]+/ in the include list instead of /meetings/* with no effect.
Before continuing to try other options, I thought I'd see what the community already knows about what is/not supported.
Thanks!
-Chad
We have a main page that has the form:
https://domain.com/*/mainpage/[guid]
Sub-pages have the form:
https://domain.com/*/mainpage/[guid]/subpage/
The problem is I can't isolate tracking page views to the main page. If I use "...mainpage/" then it won't pick up any because of the GUID. If I use "...mainpage/*" then it will pick up all of the sub-pages.
Thoughts on how to solve for this?
To me it seems to be working, happy to jump on a call to address this, if needed
fyi: @dileepnalla @michael_sweeney
cc: @mickey / @ciarapeter
And I didn't really expect my regex attempt to work. For [A-Z0-9]+ to work as expected, GPX would also need to interpret the forward slashes "/" in the URL, which would not work because I did not escape those characters. When I have a moment I'll try a correctly formatted URL with escaped chars and see what happens.
This is now working to capture the /meetings/ABC123/edit urls we need to exclude:
/meetings/*/edit
I swear this was not previously working, with two people trying it separately and a third looking over a shoulder. That said, Harshita confirmed it works, as did I this time around. We'll just call it user error x3 and move on. ;)
-Chad
Yes, we do support Java regex.
Is the feature something like using the URL in combination with CSS elements?
@caudet second those thanks for piping your learning back in here : )
/subpage/]https://domain.com/*/mainpage/*/subpage/
Let me know how it goes
I'm trying to use slightly more complex Java regex in a URL Rule in the product mapper, but I keep getting a "Failed to update event" error message.
As before, I'm trying to capture this URL:
https://domain.com/meetings/GJF69DK70GJE28F9210J
and not:
https://domain.com/meetings/GJF69DK70GJE28F9210J/edit
I've tried these regex options (with and without escaping), but get the same failed error:
https://domain.com/meetings/[A-Z0-9]+
https://domain.com/meetings/[A-Z0-9]{20}
Do you think these should be supported in a URL rule?
Thanks!
Did you try using wild card for that?
Currently, we do not support such advanced use cases with regex.
You previously mentioned having support for java regex - do you have a summary of what is supported and where in the PX product this or that regex will work?
Thanks!
Thanks!
Hi@caudet , @alb , @mikewohlwend please see this month’s Release Notes: https://support.gainsight.com/PX/Release_Notes/PX_Release_Notes_November_2019 > Product Mapper Enhancements, the Regex Support from your ask is supported from the UI now
Great move---icons can help a user know why they might want to click the thing. Makes those hotspot starting points much more useful