Skip to main content

    Idea Pipeline

    Filter by idea status

    Filter by product area

    6160 Ideas

    alizee
    alizeeVIP ⭐️⭐️⭐️⭐️⭐️

    Allow standard fields to be editable from CTANew Idea

    Hi all,Today, it’s not possible to edit company or relationship standard fields from CTAs when those fields are displayed on the CTA layout.The “editable” tick box is greyed out.However, I can think of many use cases where this would be extremely useful, the principal one being a New Customer Assignment / Kick-Off CTA per the following flow: New customer is created in Gainsight with a rule  A CTA to signal that new company record is assigned to a user, for them to review and assign the customer to an engagement model and a CSM The reviewer reviews the information about that customer directly from the CTA to make a decision on their engagement model, and based on that, sets two custom fields (Engagement Cadence and Engagement Model) and two standard fields (CSM and Stage) which are displayed under the Company tab of the CTAToday, I am able to set the engagement model and cadence from the CTA and have to visit the Company C360 to update the CSM and the stage. Considering this is all part of one process, handled with that kick-off CTA, I’d like to be able to do everything from the CTA.My ask:Allow standard field edits from CTA layoutAllow company standard fields to be editableAllow relationship standard fields to be editable  I believe that ties in with the in-line editing work, although a bit different but that’s really the same spirit.  Thanks for considering this request.A. 

    CarollynnC
    CarollynnCContributor ⭐️⭐️⭐️

    Additional Configurations for Due Dates Based on Calendar DatesNew Idea

    I’d like to request additional functionality within the configuration of Due Date assignments where due dates are required. E.g. CTAs level, Task Level, Success Plan level, Success Plan > Template> Objective level.For our use case, the ability to assign objective due dates is the most limiting. For example, we have an annual Success Plan end users manually create in advanced of year end so they’re able to complete steps needed to prepare the Success Plan for use. The due date of this Success Plan should reflect the last day of the next calendar year (12/31/2023). Current configuration limitations means they’d also be required to update all the due dates at the objective level manually as an added step, in addition to updating the Success Plan level.Currently you’re able to assign the dates based on two selections: Assign Date + days OR Objective Start Date + Days.  Pictured below:  What we are requesting to see is something to the effect of:Custom Date Last Day of Current Calendar Year Last Day of Current Calendar Month Last Day of Current Calendar Week Last Day of Next Calendar Year Last Day of Next Calendar Month Last Day of Next Calendar Week First Day of Next Calendar Year First Day of Next Calendar Month First Day of Next Calendar WeekIt’d also be important to include fiscal year within these options in addition to the above. 

    bradley
    bradleyExpert ⭐️

    Allow Admins to Disable Linked Object Record DeletionNew Idea

    I saw this post, requesting that deleting a CTA not delete the associated linked object(s) but I think this request is different enough that it deserves its own post. At the very least, it has not been implemented even if there is overlap. Here is a use case/context around this: You have a low volume custom MDA table that you have configured as a linked object to a Lifecycle or Objective CTA for example.  On a C360 report, users can add or modify records to the table but they can not delete them. As a linked object on a CTA, users have the following actions however: Create New record Associate Existing record to the CTA (and then modify it) De-Link the Associated Low volume Record DELETE the associated Low Volume Record The last option actually deletes the record out of the object and is visible in data management: This opens the possibilities for end-users to completely remove a record from an object whether they intended to do that or not. While a confirmation dialogue box does come up, the de-link vs delete distinction is not one all end-users will always action on appropriately. At best, deleting a record in this way only negatively impacts the single user. At worse, it could cause major downstream problems. Please give admins the option to disable the ability to delete these records as a permission, part of the linked object configuration or something. As it is, this presents a blocker for us in adopting this feature.