PX Product Ideas
PX Product Ideas
- 641 Posts
- 1,406 Replies
Add the capability to import, update, and manage PX application users and role permissions sets via the PX REST APIPlanned
Posting on behalf of several customers… Description:Currently, every PX application user must be created manually and their Role permissions assigned manually too. Additionally, PX does not implement the concept of shared user role permissions sets, so updating user permissions must be complete on a one by one basis. These shortcomings to managing PX application users can be challenging … even for small sets of users and for minor role permission changes. Feature Requests:Add the ability to create/manage user role permissions sets and assign these quickly to PX application users. Add the capability to create update, and manage PX application users and roles via a new set of REST API call. Implement a new option in PX Data Loader to import PX application user from a CSV file.
Posting on behalf of a customer: Requesting to add the producttags and description(different from engagement name) to the AWS export of the engagement metadata table.Screenshot reference: https://share.getcloudapp.com/wbubPO0q
Posting on behalf of a customer:Currently, there is no limit to prevent the KCB from being dragged completely off screen the Bot behaviour with draggable enabled for reference https://share.getcloudapp.com/KouJBXG1. When this happens we either have to zoom out or re-login to view the Bot.It would be helpful if there was a limit to prevent KCB being dragged off completely.
Date Filter to end at TODAYNo Status
My Onboarding team thought it would be useful to be abel to create custom dynamic date ranged that go from a specificed start date to (TODAY). This way the filters, widgets, reports, would always be up-to-date. The predefined timeframes do this, but the fexibiliy of any start date until today, would be helpful.
Posting on Behalf of a Customer. It is found that PX typically track mouse browser events on anything clicked on a web page. For certain HTML libraries that default to using Pointer events, it is found that it isn’t tracked by PX, as in the command calls are not coming in for them. Info on Pointer Events.https://developer.mozilla.org/en-US/docs/Web/API/Pointer_events
I need to be able to push an individual user’s NPS survey result back to Salesforce, in order to trigger tasks for our CSM team. Syncing at the Account level isn’t specific enough to segment feedback by customer persona (reps vs ops vs executives).Within the PX survey configuration, I would expect a tab that gives me the option to additionally record a user’s feedback to a custom attribute of my choosing. Perhaps with the option to track history or overwrite the field with the latest score. I know the data exists on the contact record in PX and is viewable under the feedback tab, I don’t understand why that can’t be passed through to an attribute.This was data we could previously capture with PX NPS surveys triggered by Journey Orchestrator, I need to be able to sync the data back to SFDC so other software can pull from those fields on the contact level.
Would like to be able to see which/how many users are qualified by an audience.Would be really helpful to see how many or ideally which users are qualified for an engagement to be able to discover if the audience has been set correctely. It’s tricky to guess sometimes.
Use cases & Outcomes:1. Trigger a post-engagement survey after an engagement (to understand the effectiveness of an engagement, we can’t rely on the completion)2. Trigger an engagement based on survey responses (push appropriate content based on the user’s need)Problem: In our case, we can only accomplish UC #1 by following this resource by setting up two separate engagements (guide, survey). However, we have noticed some issues (shared with PX).#2 isn’t possible since we restrict sharing PII data (hashed user-id) that can’t help retargeting.Request: Provide an option to have survey as one of the steps of an engagement - for #1, first step; #2, last step. Further flexibility on the step choice would be nice to have.
Knowledge center alert badge - Ability to select categories that are included in the main badge countNo Status
Please add the ability to select which categories are included in the main badge count.For example, I only want the badge to show for the What's New category.However, the main badge count includes all unopened engagements, including those in another category. When I open the Knowledge Center, the badge displays the correct number (2) on the What's New section but doesn't match the number (4) on the icon. I understand now that the category selection is only for setting which categories display a badge inside the knowledge center. However, I just want to notify users when they have unopened engagements in the selected category, and not for every unopened engagement.
Knowledge Center Bot Font CustomizationUnder Consideration
For our use case we really want more customization. For starters we would like to be able to customize the font setting in the knowledge bot to better fit with the rest of our portal. It looks a little strange to have our knowledge center bot and engagements in a different font from everything else.
Please add more options for customizing the knowledge center alert badges. Some ideas:Allow the main alert badge and category badge to be customized separately Make the count optional inside each badge Add access to the css for alert badgesExample:
Bulk download XLIFF files for localization.Implemented
We need an option of bulk downloads for the localization XLIFFs in the list of languages from the editor. If we have many languages in the list to download and equally many engagements, it takes a lot of time to download one file at a time. So an option for BULK DOWNLOAD would be really helpful. Thanks, Shireesha.
Posting on behalf of customer:With the current product design, We only export engagement name and type, and id fields to the AWS. It would be helpful to include all the engagement data like,Channel,Priority,Description,Status,Product,Environment,Labels,URL,sIgnore ThrottlingCreate DateLast UpdatedLifetime ViewsOn the AWS Engagements file.cc: @Janine Marlatt
[Query Builder] Improvement For Bar Graph X-Axis LabelsUnder Consideration
It is found that when there are more than 4 x-axis labels possible for the bar chart in query builder. Every other label is skipped to be shown. Currently there is a code level limitation where all labels are not able to be shown responsively based on screen size available. This post is to hope in the future that the chart is able to carry responsive x-axis to use space available to add as many x-axis labels as possible.
Export labels of engagementNo Status
It would be great if Gainsight PX provides a way to filter engagements based on the assigned labels (front end). At least, label information should be accessible using the /v1/engagement end point of the REST API. Generating and maintaining engagements require different steps to be executed by different roles and users (e.g. design, localization, QA, ...). To manage these steps I’d like to introduce processes covering generation and maintenance. I’d also like to use the labels to document the steps and the ownership with regard to a specific role.However, to get an overview of all engagements I have to individually check each entry manually. Moreover, using the REST API the label information is not available.Example use case:Since I know that QA has a lot on their desks at the moment, I would like to check whether this becomes a bottleneck for the upcoming release.I login to Gainsight PX, go to the engagement overview and filter the engagements by the tag “QA approved”, OR I fetch enga
[Zendesk Requests Feature] KC Bot : Allow For Sending Of Custom Field On Ticket CreationAcknowledged
It is found for certain ticket default forms, different fields are marked as required when creating a ticket in Zendesk. Although the “Zendesk Requests” feature can directly create Zendesk tickets after a feedback is submitted in KC Bot, request from PX fail Zendesk validation due to x required field, as PX typically sends subject and description. Given the PX config isn’t able to config additional custom fields to send to Zendesk, it be nice to have that function to cater the different required fields customers have.
Multiple Gainsight PX tenantsAcknowledged
It would be great if multiple (at least 2) Gainsight PX tenants can track usage data and interact with a single product. This allows the different tenants to independently track PX, show engagements to the user and provide different KC bots. Why is this important?Customizing a product is not unusual for enterprise software. While engagements or the KC bot will work well for standard components they might be useless for customized user workflows. Even though the customer refrains from customizing the software the user workflows might still differ. Individual company policies will render engagements, e.g. guided tours, useless. Customers are very interested in their own product adoption, including individual requirements about what should be tracked. Customers want to bring their own company knowledge into individual KC bots.A single tenant hosted for a customer would satisfy the customer’s needs depicted in 1.-4. However, I will lose the ability to track the customer’s PX.Solution: Two
Hello everyone,Consider some usual feature adoption funnel:Exposed to the feature Activated feature usage Recognized the value of this feature Adopted the featureWith the current options we have in Gainsight PX for funnel reports, we don’t see an elegant way of creating this kind of adoption funnel. There are two usual ways of defining what it means that “the user adopted the feature” - either by counting the number of times this feature was used by the user or considering that the feature was adopted only if the user uses it over a longer period of time.In other words, there are two main options for setting up conditions on features and custom events that are missing here:the option to set the number of total times that the feature or custom event was used/triggered (greater then x, equal to x...) the option to set up a condition on the time interval when this feature was used - for example, in the “adopted stage” of the funnel (last stage) we should find only the users which trigger
Typically PX Engagements retain their original size as shown in the editor, which is then shown to end users.At times if a tooltip is left or right position biased , and being close to the viewport edge of an engagement creator’s screen, if an end user viewing it has a smaller screen in the end, things can go off the viewport like below. It is desired to have some configuration to control over the responsiveness aspect of engagements. Maybe if the screen is two small, go ahead and do word wrap to fit or remove an image within the engagement or remove certain text as things get smaller. etc.
How SFDC and GSPX Connect Data. It would be so much better if the connection would have a way to link Contacts to SFDC without the LoaderAcknowledged
If we had a admin window that would tell you if a User might be a Contact in SFDC and ask you if you want to connect them this could help with the errors and also allow a much easier way to connect only the contacts that you want to between GSPX and SFDC. The connection as it is today will be very difficult to maintain and keep up to date. Also if there are errors you cannot drill down in the report to see who the errors are an how to fix them so this connect falls short here.
SSO Set Up from PX login pageImplemented
Posting on behalf of Customer,In PX, with the current SSO/SAML set up we can login using the IDP, but our PX login page does not redirect users to IDP when SAML authentication is used.This is Currently a limitation and it would be really helpful for most of the customers if we implement a SSO process/set up where the PX login page will be automatically redirecting to the IDP which they have used in SAML Authentication set up.cc: @peppe
Posting on behalf of customer, Whenever user selects Audience rules in engagement to restrict it to only particular set of audience, it would be displayed to only that set of audience when Triggered by is set to Automatic. Instead if the Triggered by is set to Knowledge Center, the Knowledge center Audience Logic rules overrides the Audience logic of engagement. Example Scenario: If in Engagement audience logic, it is selected to be shown to only particular account users. But in KC bot, if audience logic is set to be shown to all users. In this case, Engagement is being shown to all the users of all accounts. Instead if the engagement is shown to only users who are selected in Engagement audience logic, it would be of great help instead of creating multiple KC bot’s for each required filter at engagement level.
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.