Skip to main content

Idea pipeline

5538 Ideas

bradley
bradleyExpert ⭐️

Improved Action Setup for Horizon RulesOpen

Hopefully not a repost, though I’m sure I’ve seen similar, and probably made similar. The Setup Action page isn’t great if you have more than three actions:I’m sure I’ve commented already on the criteria getting clipped and the action not having any useful information on it. Here, you can see that the number of additional criteria is barely even visible. The main issue is the workflow. If I ever want to work on one of these 25 other actions, I have to click show more criteria. When I work on the action, save and close it, I’m not even snapped back to the design. I’m just in empty space. See gif below to embark on a delightful journey with me: I’d really like to have more show by default or at the very least when I expand the list, have it stay expanded while I’m on the Actions Page unless I collapse it myself. Part of the reason for this is I’d also really like to see which actions are active, which are not, AND have the ability to toggle actions off without having to go into each action individually.If the actions are all on the same criteria branch, it’s pretty easy to see what is/isn’t active and do the toggling. But for the most part, my actions all have different criteria and, as you can see above, going into each action to toggle it on or off is a nightmare:You have to go through this expand, click, scroll, expand, click, scroll nightmare 25 times. Because of that, and the fact you can’t see if the action you just toggled off is off or not, it’s hard to keep track.Toggling actions on and off is great for testing, but really hard to manage for larger rules. When I wanted to test this rule, I ended up cloning it, and just deleting everything because it was easier :(, and even that was a pain.

ChristianCDW
ChristianCDWContributor ⭐️

Year over Year (YOY) comparison reportingNew Idea

Hey all,I’m a business analyst for my company and recently was asked to create reports comparing year-over-year (YOY) data pieces. In attempting to create these reports and widgets I learned that Gainsight does not have (by default) the following capabilities: Current Year YTD Values → Comparison Over Previous Year YTD Values Current Year QTD Values → Comparison Over Previous Year QTD Values Current Year MTD Values → Comparison Over Previous Year MTD ValuesThis was shocking to me considering these are fairly standard, cross-industry, reporting requirements for all business in all business sectors.Being able to take X period (current year, or other), with Y data (sales amounts, or counts, or other) and compare it to the same period in the previous year (or another year). This can be further expanded to a specific month (April 2025 compared over April 2024, or April 2023, etc...) Our account manager and technical account manager asked me to create this post for visibility.I was able to create a makeshift YTD year-over-year report, comparing current year to previous year, but it is very limited compared to a standard comparison report/widget.Support provided instructions on how to create this as a dynamic data-set, requiring us to create an object for each period that we want to see and comparing it to the previous 1 year back. However, this is still limiting and requires the set-up of multiple complex objects and requires us to upload a data table for what we want to compare, rather than using data within Gainsight.Please comment, upvote, etc!

rschlette
rschletteHelper ⭐️⭐️⭐️

Enable Dashboard and Report Sharing for Pending PX UsersNew Idea

Current StateNewly provisioned PX users who have not yet logged in (status = Pending) cannot be included in user-based sharing for dashboards and reports. Sharing options are limited to “Public,” which creates one of two issues:Low trust: Dashboards must be publicly editable, exposing them to unintended changes. Poor first experience: Pending users see no shared assets when they log in, reducing perceived value.Example ScenarioA CS leader wants to use PX to view adoption data. A dashboard exists for them, and ideally, they log in and simply filter by any customer ID in their book of business. Today, this is not possible because:To filter a shared dashboard, users need Edit permission. Direct sharing requires the user to be Active, so we cannot share dashboards or reports until they log in and change status from Pending to Active, unless we settle for completely open public write/edit access.Current WorkaroundsMake dashboards Public with write access for all users (low trust). Ask the user to log in, confirm, then manually share dashboards/reports (awkward and inefficient).Business ImpactEveryone’s org is different, but in most of them you get one shot to demonstrate value. In the current state, a new user either logs in to find dashboards that are constantly open to public changes (so low trust), or an initial user experience that literally does not provide them with any value (no shared assets to view) Please allow Dashboard and Report sharing for Pending PX users so we can have productive first sessions with our largest PX user group

romihache
romihacheVIP ⭐️⭐️⭐️⭐️⭐️

Standardize Time Zone Display Across ApplicationNew Idea

ProblemGainsight CS displays execution history and related time-sensitive data using inconsistent time zones across different features, leading to confusion, wasted time, and the need for manual time zone conversions. Lack of time zone parity across features creates an unnecessary cognitive load for users trying to understand the status and timing of critical jobs.When investigating why a specific user was missing on my end, I checked the execution time of the relevant Job (Salesforce connector). The Job's history showed the last run was yesterday at 7:00 AM. Knowing it’s a daily run, I expected it to have already executed today as it was 8:45 Upon checking the Job's configuration, I realized the execution time was set to 7:00 AM PDT (the application's time zone), which corresponds to 4:00 PM in my local time. This caused me to mistakenly believe the execution was missing and required me to manually trigger the job; all because the displayed time was not in my local context. Connectors → Activities UIThe root cause of this confusion is that I spend most of my time in the Rules Engine, where the execution history is displayed in my local time zone. When I switch to Connectors 2.0, the time zone shifts to the application's default. This broken experience forces users to perform "mental gymnastics" and consult external converters just to confirm the expected run time. Proposed Solution I request a feature to allow users to select the time zone for displayed data within each feature that shows execution history or timing (e.g., Jobs, Rules List, Rule Chain, etc.).Ideally, this would function similarly to the Rules Engine → Activity view, but be integrated directly into the feature's interface, not as a separate activity section. Rules Engine → Activity allows users to select the time zone for displaying dataExample Implementation:Introduce a prominent UI element (like a toggle or dropdown) that allows the user to switch the display of time-stamped data between: Application Time Zone (e.g., PDT) User's Local Time Zone (The time zone of the user browsing the app)  Mockup: Allow the user to select the display time zone, dynamically adjusting all dates and times shown in the UIStandardizing the display across all features will prevent user error, reduce support inquiries, and greatly improve the overall user experience.#adminQoL