Skip to main content

    Idea Pipeline

    Filter by idea status

    Filter by product area

    5795 Ideas

    phaneendhar_lingam
    phaneendhar_lingamContributor ⭐️⭐️⭐️

    History Tracking for MDA ObjectsDevelopment

    History tracking data is important for  trend analysis/ forecasting. But, there could be some objects where we are required to maintain just the snapshot data. For example in standard objects like Company/ User or any custom objects – In Company, when did the CSM change or what was the previous ARR? As of today, we do not have the luxury of keeping historic changes in Gainsight but with the help of rules/ objects we can still accomplish this.   For demonstration – I’ve created the object ‘Kite Info’, which is loaded around 7am daily. Schema as follows, {*Kite Id(String); Kite Name(String); Kite Date (Date); Kite Value (Number); Kite Location (String) } *Kite Id is the identifier field. I’ve created a backup object that has only those fields which require history tracking(along with the Identifier) – ‘Kite Info Bkp’. This object is loaded 10am daily. But, for the first time – data from ‘Kite Info’ is loaded once ‘Kite Info Bkp’ is created. {*Kite Id(String); Kite Date (Date) ; Kite Value (Number);  Kite Location (String) } *Kite Name is consistent hence not required for tracking.   Rule Name -> ‘Load Kite Info Backup’, scheduled to run at 10am Load all the values from ‘Kite Info’ to ‘Kite Info Bkp’ with Upsert operation and Identifier ‘Kite Id’   History Tracking object – ‘Kite Info History’   Column Name DataType Kite Id String Kite Date New Date Kite Date Old Date Kite Value New Number Kite Value Old Number Kite Location New String Kite Location Old String Kite Date Changed Boolean Kite Value Changed Boolean Kite Location Changed Boolean Changed Date Date   History Tracking Rule Setup, Rule Name à ‘Kite History Tracking’ ; Scheduled to run at 9am daily. “Timing of this rule is of highest importance – this should be scheduled to run after the source ‘Kite Info’ is reloaded but before the backup object ‘Kite Info Backup’ is refreshed. In the Merge task, I’m doing inner join on Kite Id.   Fields in the Transformation task ‘Change Capture’ are as follows, Those with prefix ‘new’ are from ‘Kite Info’ Those with prefix ‘old’ are from ‘Kite Info Bkp’ Field List – Kite Id, Kite Date Old, Kite Date New, Kite Date Changed and similarly for Kite Value and Kite Location Case statement, When ‘Kite Value New’ not equals ‘Kite Value Old’ then ‘Kite Value Changed’ is True Similarly for Kite Date and Kite Location. I’m introducing another case field as, When ‘Kite Value New’ not equals ‘Kite Value Old’ (OR) ‘Kite Date New’ not equals ‘Kite Date Old’ (OR) ‘Kite Location New’ not equals ‘Kite Location Old’ Then ‘Changes Made’ is True Only if the above value true, a record will be considered for inserting into History tracking object.   Loading into History Tracking object is of INSERT type action, as we have to capture all the changes being done.

    AnitahgContributor ⭐️⭐️⭐️⭐️⭐️

    Advanced Weighted Gamification Scoring (Quality over Quantity)New Idea

    Context & Use Case: Right now, our point system is entirely based on generic actions rather than the actual value of a contribution. For example, our current rules award 1 point for giving a like and 15 points for creating a topic. This means a user can spend 15 seconds clicking "like" on random posts and earn the exact same number of points as a user who spends two hours documenting a highly complex, net-new use case for the community. This inadvertently rewards volume and "point farming" over genuine knowledge sharing.Proposed Solution: Introduce Advanced Weighted Scoring that allows admins to adjust the relative weight of actions to prioritize quality. Specifically, we need the ability to: Devalue or Cap Basic Actions: Give admins the option to cap clicking like a small daily limit so they can't be used to climb the leaderboard. Highly Reward Complex Contributions: Allow us to create custom, high-value point allocations (e.g., 100 or 200 points) for actions that drive the community forward, such as publishing a verified knowledge base article or sharing a detailed, multi-step use case. Value/Impact: By creating a wider gap between low-effort clicks and high-effort content creation, we can naturally encourage our users to share deeper, more meaningful insights. This ensures our leaderboard accurately reflects our true community experts, rather than just our most active clickers.If you think our gamification should reward deep expertise over quick clicks, please upvote this idea and share how you'd like to see points weighted!​@olimarrio ​@Mithila Jayalath ​@Snjezana Slabek ​@Maritsa  

    dkobeContributor ⭐️

    Learning Path Feature ParityNew Idea

    Currently, there is a significant functional gap between Courses and Learning Paths within Skilljar. While Courses offer robust administrative controls, automation, and granular reporting, Learning Paths often act as simple containers.To provide a seamless experience for both admins and learners, we request feature parity for Learning Paths. This will allow for more sophisticated curriculum design and reduce the manual overhead currently required to manage multi-course programs. Advanced Enrollment Management Admins need the same level of control over Path entry as they have for individual Courses. Specifically we need the capability for admins to edit the "Enrolled On" date for a learner’s path record. Path-to-Path Prerequisites Mirror the flexible gating logic available at the course level to create structured learning journeys. Sequential Locking: Requirements to complete Path A before unlocking Path B. Flexible Gating: Support for "AND/OR" logic when setting prerequisites across multiple paths. Completion Controls & Scoring Learning Paths should carry their own "transcript-level" weight rather than just reflecting the sum of their parts. Status Management: Clear Pass/Fail logic for the entire path. Aggregate Scoring: A path-level grade based on weighted averages of the underlying courses. Completion Actions & Automations Automate the "What’s Next" after a learner finishes a complex curriculum. Chained Enrollments: Automatically enroll a user in a new path or course upon completion of the current path. Deactivation Timers: Automatically revoke access to path content after a set period post-completion. Approval Workflows: A "Request Access" flow for paths that requires admin or manager sign-off before the learner is enrolled.