Replies posted by rschlette
now with fewer typos: The issue you encountered was in the specific and limited case of www.domain.com . PX strips www. out of all urls so that www.domain.com and domain.com are auto resolved. So whether your url is www.domain.com or domain.com, PX consumes domain.com. If www. is treated like a subdomain in a rule, like (*.domain.com), the rule will fail because the dot is stripped. Basically you can always ignore www. in a url, because PX will strip it out of both the incoming event and the rule. No need to address it.
There is actually a much more narrow case here, so I’ll add some additional details.In general, using a wildcard followed by a dot is a fine way to wildcard a subdomain. If my url scheme is accountName.domain.com, I can write a universal rule for that by using *.domain.com No issues with that at all; the *. at the beginning of the rule works just fine.The issue you encounter was in the specific and limited case of www.domain.com . PX strip www. out of all urls so that www.domain.comn and domain.com are auto resolved. So whether your url is www.domain.comn and domain.com, PX consumes doimain.com. If www. is treated like a subdomain in a rule, like (*.domain.com), the rule will fail because the dot is stripped. Basically you can always ignore www. in a url, because PX will strip it out. No need to address it.Again, any other subdomain is unaffected here so subdom.domain.com can be matched to *.domain.com.Hopefully that clarifies the scope a bit
additional customer feedback:“In my opinion, this is critical for the appropriate use of the Recommendation tab in KB. Because we have many different sets of roles and it's impossible to create a meaningful recommendation without the ability to configure AND/OR operators”
Following up here, manually adding <h2> elements in the source code for tooltips and saving as a template, allows the customer to use this going forward on any new guides. However, a new template won’t help with any previously created guides with multiple steps and localizations these would all need to be recreated.from the Customer:“The easiest workaround would be for Gainsight to add this to any Divs used as the title for tooltips, guides, dialogs: role="heading" aria-level="2"This keeps all the CSS intact and doesn’t shift things around like adding an H2 tag, but it does give screen readers the information to treat these elements as headings. This could also be applied to all the legacy tooltips/dialogs and localized versions without causing any effort to update CSS.<div role="heading" aria-level="2" class="px-dialog-title" >Accessible Titles!</div>”
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 email@example.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.