Currently admin users can only delete one rule at a time. It would be great if we could delete multiple rules at once, instead of having to do them one by one.
MDA’s created by Data Designer jobs are currently classified as System MDA’s, so they cannot be deleted. It would be more flexible to use the Custom type for these, so admins can freely delete them.
I feel as though more people than just me would be facing this issue, so I’m starting an idea for people to manifest interest on this.Currently the embeddable widget will only display public content due to the fact there is currently no way to authenticate the viewers of the widget on the external website where it sits. HOWEVER, in some cases the authentication is ensured by the placement of the widget. (ie. If you place your widget inside your paid tool - which requires a login - then you know only paying customers will see the widget).In this case you would want the embeddable widget to display any content that is available to the equivalent paying customers’ custom role within InSided, instead of limiting it to public content because InSided cannot authenticate the user.All this would require in the Control side is the selection of a content permission setting done by selecting 1 or more roles. In the backend this would mean using this variable to filter the embeddable widget search results.
Scenario: A PX admin builds a full Product Map and Engagements based on v1 of their application. V2 comes out, and the engineering team informs the PX admin that they updated several HTML elements. Now, the PX admin needs to manually comb through the Product Map and Engagements in order to find and update the CSS selectors that have were affected by the UI change. Problem: Locating all instances of a specific CSS selector can be tedious and challenging, especially if the PX subscription has a large Product Map, multiple products, or many Engagements). Proposed solution: Allow PX admins to bulk edit CSS selectors across both the Product Map and Engagements. Perhaps we could expand on the feature cloning functionality to work for existing features as well? Value proposition: Save time otherwise spent manually updating CSS selectors; reduce user error by ensuring that the PX admin does not accidentally miss a feature or Engagement that contains an outdated selector.
Similar to another Idea I posted but not quite the same - Currently, when a Rule Chain is in queue, we cannot see that it is so until one of the Rules in it begins to process in the queue. This makes it very difficult for understanding expected processing times and delays when trying to optimize the overall schedule.Furthermore, we cannot abort the Rule Chain until one of the rules begins to run - which we don’t have visibility on, so we are essentially left monitoring the Rule Timeline until it appears. Beyond that, since the Rule Activity Timeline does not auto-refresh, we cannot just leave the page open on a monitor; we have to be constantly watching and refreshing it. When the Great Rules Engine Outage of May 2022 happened a few weeks ago, neither we nor GS Support realized our delay went on for several days because Rule Chains were stuck in an invisible queue!
We would like the comments section in the Timeline entry for Scorecards which is periodically pushed through the Rules engines to show text that can be easily read. Right now it pushes run-on sentences that makes for a poor user experience. This may be a bug vs. Idea.
It would be useful if you can select a specific group to send a private message to. In my closed community we have different projects so different groups (user roles) . Currently, if I want to send a group message to one of these groups I have to manually type in all their usernames, which is quite time consuming.
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.
I have had a couple conversations with customers now where the topic of being able to dynamically assign activity types has come up. By default all activities created via the integration seem to have the activity type of Call. Customers often have KPIs wherein their team is expected to log certain type of activities at certain cadences. The request has come up that it would be nice if we were able to dynamically create the gong.io activities in the timeline with certain meeting or activity types. Not sure how that would work technically but something I think we should explore further.
We need these everywhere. Rules Engine, JO, Connectors, Playbooks, 360 layouts, everything. There is clearly a modification log somewhere behind the scenes, but we do not have access to it in the UI. It is extremely frustrating that I learn from tribal knowledge that “that thing I need should be available by asking Support” - and this takes days, not seconds as it should be readily available to me at any time. I understand 30-day limits and things like that such as what is applied on Rules Engine execution history. However, as teams grow and things happen, we need to be able to track back to specific changes far more easily.
Today, I have to add fields to a report one-by-one. Would be awesome if I could multi-select fields to more quickly add them to a report.
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.
In one recent scenario - linking of a report was required in the JO email, but we were unable to customise the background of the Report linked. Just like the global reporting settings, the reports in the JO should be customisable as well so that it can match the overall look and feel of the Email template.
Hi, is there currently the option to edit a CTA so that it is recurring, or edit an existing task to be recurring? To clarify, this is for CTAs configured at the Relationship level. We'd want to edit the CTA and/or Task so that it recurs on a weekly basis.
We love tabular reports -- it’s what our users prefer and what managers like to see. So, we use a LOT of tabular reports in our dashboards, through report sharing, etc. It would be great if we could set color themes to these tabular reports, to make our dashboards more colorful and eye-catching, like you can do in Excel.
Any chance we could get a refresh button on the Rules Engine timeline screen so you can refresh the status of running rules without having to reload the whole browser, similar to the refresh on S3 jobs in Connectors?
We admins need a single document that contains all the known limitations (and instructions for how to increase, if applicable) within Gainsight’s platform. I know @sdrostgainsightcom and I pushed for this a few months ago when I was still at Gainsight, and I think it’s just as relevant as ever. For example, A Data Design can only contain 50 fields (but if you need more, contact support). A Rule can only contain a maximum of 15 total tasks. A Dashboard is capped at 20 (maybe 25? - see, this is why we need this...) reports. And so on. This would be so massively helpful and would almost certainly deflect countless hours of tickets/questions from Gainsight’s support and CS teams, respectively. Please consider prioritizing this.
We have fields that calculated for numbers to display in reports. Right now, I cannot set a range of numbers to a specific color that is not a scorecard. IE I have a field that calculates number of months since an update was made. I want to display the number of accounts by the number of months not updated, and if the number is greater than 2 to have a red as that is considered too long since update. Right now it is defaulting to a green - which is counter intuitive to what that actually means
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.
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.