+1Similar to how Product Mapper URL rules have wildcards it would be nice to have wildcards for UI Element rules. When evaluating the selector it might be such that a UI object has a dynamically created ID and we would want to capture any of the objects of this type.
Example image showing where we would use the wildcard.
+3Hi
Let’s say you’ve got an href that looks like this: [href=”https://www.nytimes.com/crosswords/game/daily/2023/08/10”]. If you want to build a rule for any link that contains text from that URL, you can simply add a * to the attribute name. In this case, we end up with [href*=”/crosswords/game/daily/”], which means ‘URL contains /crossword/game/daily’.
This W3 article shares a couple other ways to manipulate attributes in CSS selectors.
+3I’ve attempted this with a feature that looks like this:
The UI Element was changed to :
[href*="/Folder/FolderProperties.aspx?FolderID"] > .buttonContent This does not seem to have worked. Any ideas?
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
