Topics started by mikewohlwend
I know certain engagements can, but can the product mapper distinguish an element via the text inside it?
Can the product mapper do what tooltip/hotspot engagements can do--target a part of the product by looking at the text inside an element? I have a bunch of generic buttons and am wondering if there is an alternative to asking dev for some ID tags on them. (Ultimately, I want clicking the Save button to trigger an engagement.) Thanks, community!
Help navigating in the contextual engagement builderUnder Consideration
From this spot in the builder, it's hard moving to any next or previous step. I have no idea what to click in the menu: PX could help me navigate by either: highlighting the current step in the dropdown menu showing some text from the modal in the dropdown instead of the title it asks me to enter (which can become outdated and which I tend to skip)* adding the <5/18> style navigator used in other parts of the builder to this part of the builder (but what would really be prefereable would be to integrate all of the builder functionality into this contexual builder where my app is in the background) *I have not been entering meaningful title info because it is fragile to updates and even well done provides no value to my users. I generally pass through multiple iterations where the content and targets change, so a correct title would need to change as well. This sort of title maintenance would not be a good use of my time.
I often interspersed a modal like this in the walk through tool my company used prior to shifting to PX: The users could do whatever they needed on the page, and the modal would persist in a corner of the screen despite minor url changes. When they clicked "Next," the next step would appear. (The (?) spots reveal explainer tooltip text on mouseover--just regular html stuff that we can do in PX too) WHY IS IT USEFUL This technique worked well in cases where a user may need to take any number of steps (or no steps if already ready) before moving on to the next part of a process. It's the digital analog to a tour guide saying, "get some snacks, hit up the restrooms, meet back at the bus in ten minutes." Does this make sense and has anyone found a good way to handle this kind of function in PX?
I come to PX from six months of working with HelpHero and more years of peaking at WalkMe. In both of those places, I saw a different stance in the tour/walk-thru/engagement editors. I'd like to encourage PX to build toward incorporating these three modes: 1. out-of and 2. in-app editing and 3. in-app preview modes into a more unified mode, with your customer's web application at the core. That application is the context to rule all contexts (well, your customer's customer's workplace workflows are probably the only more essential context--but more abstract and less accessible than your customer's applications). So, this is not a feature request, but a vision request. You can help my users by my helping me keep closer contact to the point on the ground, in my application, where my user needs me. I'm looking forward to learning much more, but happy in the meantime to share an impression that benefits from PX inexperience (as I have not yet gotten use
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.