Skip to main content

Idea pipeline

5527 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.

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.

kristineoContributor ⭐️⭐️⭐️

Granular Permissions/Configuration for Ideation (View, Vote, Comment)Development

I'd like to request a feature that allows for more granular control over user permissions within the Ideation section, specifically by splitting permissions into "View," "Vote," and "Comment," similar to the existing permission structure in the forum discussion areas. Basically, would like product parity for permissions between forums and ideation. Current Situation:Currently, the Ideation section permissions are "all or nothing." If a user has permission to access Ideation, they typically have full access to view, vote, and comment. This lacks the flexibility we require for our community management. Desired Functionality:We need to implement a permission system for Ideation that allows us to control "View," "Vote," and "Comment" permissions independently based on both primary and custom role. This would enable us to create custom user roles with specific access levels, like how it is in the discussions. Use Case & Rationale:Our community utilizes a multi-tiered user permission system. All registered users initially go through a screening process."Registered users" (Primary Role): All users upon registration. "Role B" (Custom Role): Registered users who have passed the screening and are granted full posting permissions in forum discussions. "Role C" (Custom Role): Registered users who have not passed the initial screening and are limited to viewing content in forum discussions.Currently, we can effectively manage these roles in the forum discussion areas. "Role C" users can view but not post, while "Role B" users have full posting capabilities.However, this granular control is lacking in the Ideation section. We wish to extend the same level of control to Ideation. Specifically, we need to:Allow "Role C" users to view Ideation submissions. Allow "Role B" users to view, vote, and comment on Ideation submissions.The current "all or nothing" approach prevents us from implementing this refined permission structure and may be impacting our support community’s SEO and discoverability.