PX Product Ideas
PX Product Ideas
- 276 Posts
- 1,452 Replies
It seems very strange to me that when using the widget, the knowledge center is expandable to provide the user with more space to view a video or article. However, if I use the embedded (mapped to UI element) option, the knowledge center is NOT expandable. Can the ability for the user to expand the KC bot be added to the embedded bot option?I believe this is also what @molly.phillips was referencing in another idea post. Apologies, Molly, if I’ve misunderstood your comment.
Hello to PX Product team, I would love more user management for PX end-user. Better analytics around access and control over access for users. As well as ability to inactive rather than delete. Additional profile fields to help us understand our stakeholders and responsibility. An open text field would be great for notes on our end-user. For security reason we need to be able to manage our end users. who has access to what pieces of PX. We have close to 86 users and there is no auditing trail for changes. So you can see the need here. Best Regards, Darshana Shah
Email OPEN events are not currently available for Email Engagement Audience Logic rules. Including OPEN in this event list would facilitate email engagements like ‘send email B to users who did not open email A’, ‘send reminder email B to users who did open email A’, etc.A GET request to the EmailEvent can return emailTrackType: EMAIL_TRACK_OPEN. That’s the event that would be great to add here.
Posting on behalf of a customer… It would be great to include Browser and Device Type as available filters in PX Analytics. We still use Google Analytics for this analysis and would like to do this in PX if possible. Gainsight Add-on… We do currently support targeting PX Engagements by Device, platform (OS), and Browser and we also have a Dashboard widget available for Browser analysis. See below screenshots:
At the moment in KCB, if you have a section with for example the name “Section” that has articles in it, you can select a color for the “Section” copy. When the user has read all the articles in that section the color of the copy will be lighter, to indicate it’s completed. We would like to disable the function where the color becomes lighter, or be able to pick which color it should be once completed. Reason for this is we want to have “permanent” content for sections, like “always on” articles so to speak, so we don’t what the copy to be lighter since we don’t consider the section to be “in progress/completed” etc.
Ability to undelete an engagementNo Status
When you delete an engagement, it would be helpful if the engagement went to a “trash” or “archive” area instead of being completely deleted. Administrators could then go to that area and undelete engagements.Accidents can happen where someone accidentally deletes the wrong engagement. This feature would make it easy to reverse deletion.
It would be good to have the option in filters for user attributes, on number of visits in reports.We are able to see this in the UI in audience explorer but not able to apply it in filters.It would be good to identify users who are not adopting and can use these filters to engage them.
Screen readers use HTML Section Heading elements (e.g. h1, h3, etc.) to specifically announce content as headings. PX is using div elements (e.g. .px-tooltip-title-wrapper) as containers for titles, so the screen reader does not read them as headings. This reduces accessibility. Consider the Guide tool tip, for example. The distinction between the title and the body text is pretty critical. The workaround is to disable the title and manually code a heading element into the body of the engagement. This works in theory, but in practice this would need to be done for every localization version of every engagement, making it relatively impractical.
It would be great if, when searching for an engagement by name, you could hit enter and get a list of matches. Currently, you just get the dropdown that truncates the engagement names and hovering doesn’t display the full name. It’s then hit-or-miss by clicking on one to see if it’s what you wanted. THEN, if you search that keyword again, the dropdown results are not shown in the same order! So it’s an even more complex game of hit-and-miss.If the search finds 6 engagements with the keyword I enter, it would be great to see just those 6 appear in the regular engagement list view. Similar to how the engagement list changes if you click on a filter or a label.Also, I don’t know if this needs to be a separate idea, but it would be great to be able to export a list of engagements: full list, filtered list, labeled list, search results list, etc.
In an organization in which not every user has access to PX or to share with a customer who may not have a PX license, it would be helpful to enable PX users/admins to seamlessly export Dashboards and their associated report/widget data externally (PDF, PPT, excel, etc.). Currently, this requires the PX user to manually capture images of the dashboard/widgets and export the csv data, then merge this in a single sheet/presentation. As these are images, it is not possible to drill into the data. Use Case: PX usage data is needed by a member of the organization who does not have PX access or this information needs to be shared with a customer. The dashboard and associated reporting is created in PX then shared externally for data transparency.
I am trying to integrate our Salesforce data to PX, but am unable to because there is a case mismatch. There should be a step where I can transform the data to get it to lookup properly. Getting the information to be the same between our CRM and products is operationally expensive, and is not guaranteed to last.
Our cloud-hosted software makes use of modules hosted in a separate domain. These modules are written as plug-n-play so can be used over our suite of products. Each product makes the module available through an object tag in its HTML code.We are unable to get the PX Product Mapper to recognise any module-UI elements embedded in the object tag. We added our product PX tag to the module code as advised by support (with Srinivas Myakala) to no avail. Further testing with support have concluded that the object tag is not being treated the same as iframe tags by the Product Mapper.This is an important issue to our company as we would like user analysis to continue inside the new modules.
Posting on behalf of customer:Hi Team,Currently, we can get the webhook events generated for the events that are initiated from the application like new user signup/custom events/engagement.But for events that we can be generated via API like custom event/new user creation cannot trigger corresponding webhook events. It would be great if we can extend this feature to the events from API as well.Thanks,Srinivas.
The “Title and Body” section of the article editor cannot be resized which makes it difficult to edit articles with a rich content like images. It would be nice to be able to resize this, or just have the content section a lot taller by default.
Hey Folks,Have you ever needed to make a minor update to an engagement but were locked out because it was active? And then you go to pause the engagement to make the quick edit, but again, blocked because the engagement is also housed in a K-Bot library. It would be really great if we could make an update on the fly without having to:Start on the engagement you notice has a spelling error Find the Right K-Bot where the engagement might be housed (there is no way to know without looking through each K-Bot) Find and remove the engagement Go back to the engagement launcher and pause it Go to the engagement editor and make the update to word or phrase Go back to the engagement launcher and launch it Go back to the K-Bot and find the engagement again (BTW it is no longer in the same order as it was when you removed it, so you will need to search through every engagement available to every K-Bot.) Add it back to the Bot. Re-order it in your K-Bot Menu and/or assign it to a Category. Save th
It would be very helpful to allow higher level of “view” access to user engagements and Knowledge Bots. View currently only allows system users to see the list of engagments, it would be nice to allow the user to “view” the editor page without ability to edit. This way, they can see what currently exists without permissions to edit. We have a lot of Marketing team members that would like to see what is available and determine if we need yet another message or if we can simply relaunch an older message.
Trying to do iterative development on engagements is very painful and time consuming, especially when you enable triggering them from the KC Bot. Anyone with a rudimentary exposure to software development lifecycles knows that you should never work directly on what’s in production. Since there’s no real versioning or branching support, you end up cloning active engagements and the active KC Bot, changing the audience criteria and working on the new version.Working on the clones is also painful, as you need to constantly pause the Dev Bot or remove the engagement from it, then pause the engagement and then work on it. Actually, if you have the engagement open before you pause the bot, it will keep complaining it’s being used in an active bot, even if you have since paused it. The engagement doesn’t refresh the bot’s state after every attempt to pause the engagement. The opposite happens when you work on a bot, to add an engagement. It doesn’t refresh the engagement state, when you try t
Ability to link a URL from a badgeNo Status
We would like to be able to add a badge to our cloud based app that launches context-sensitive help topics in our help centre. Whilst I appreciate that Developers can code this, we’d like to be able to make changes on the fly and react to any support tickets or issues that may arise. We don’t just want to launch engagements, we want to be able to call URLs.Is this something that others would find valuable?ThanksTracy
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.