Skip to main content

Make CTA types inactive without re-assigning closed CTAs

  • August 10, 2018
  • 7 replies
  • 207 views
meenal_shukla
Forum|alt.badge.img+5
When we want to de-activate an old CTA type, we need to re-assign the old CTAs to a different (active) CTA type before we deactivate them. But this is a weird behaviour since you would want to keep the old/closed CTAs as it is for reporting purposes. Why do we need to reassign all the CTAs to a different CTA type even when they are closed in order to deactivate a type?
Outplay. Outwit. Outlast.
    jean.nairon
    faust_belarmino
    meenal_shukla

    7 replies

    aditya_marla
    • aditya_marla
    • Helper ⭐️⭐️⭐️
    • August 21, 2018
    Hi Meenal,

    Thanks for sharing this. Agree that there should not be a need to change anything in already existing CTA types when you want to make it as inactive (inactive should only prevent users from using the CTA type in the future).
    Today, before allowing a user to make a CTA type as inactive we check whether it is being used in rules OR if any CTA's exist with the CTA type. We will need to change this behavior when making a status as inactive (and remove the second validation...the check to see whether the CTA type is being used in Rules engine will still be present). Will keep you posted as and when we take this up
    faust_belarmino
    jessie_brainerd
    Forum|alt.badge.img
    • jessie_brainerd
    • Contributor ⭐️⭐️⭐️
    • September 17, 2019
    I would request that this same functionality be extended to CTA Reasons. CTA Reasons are often created to fill a specific (sometimes short term) need, but once that CTA Reason exists with any CTAs associated with it, open or closed, the Reason cannot be deactivated.

    katie_b
    faust_belarmino
    heather_hansen
    faust_belarmino
    Forum|alt.badge.img
    • faust_belarmino
    • Helper ⭐️⭐️
    • September 23, 2019
    Yes! I agree!

    faust_belarmino
    Forum|alt.badge.img
    • faust_belarmino
    • Helper ⭐️⭐️
    • September 23, 2019
    @aditya_marla Are there any updates with this request?? We'd like to clean up and optimize our CTA configurations but this lack in functionality is really limiting our ability to configure and clean up the CTAs the way we want to.

    heather_hansen
    Forum|alt.badge.img+14
    • heather_hansen
    • VIP ⭐️⭐️⭐️⭐️⭐️
    • September 24, 2019
    I'd add Statuses to this too. Especially ones that close the CTA. :)

    faust_belarmino
    sai_ram
    Forum|alt.badge.img+1
    • sai_ram
    • Expert ⭐️⭐️
    • September 24, 2019
    Changing this to an enhancement request, instead of a problem.

    R
    Forum|alt.badge.img
    • rakesh_lingala
    • Helper ⭐️⭐️⭐️
    • June 19, 2020

    Hello Everyone! 

    Happy to announce that your request has been considered and implemented as part of the v6.14 release.  Previously, it was only possible to deprecate or make existing Cockpit picklists such as CTA Types/Reasons/Status/Priority/Snooze and Success Plan Templates/Types/Objective Categories inactive. Gainsight now supports deprecating and making Playbooks inactive.

    Along with making Playbooks inactive, Gainsight also made some minor behavior changes to the following Cockpit and Success Plans assets while making them inactive:

    • CTA Picklists
    • Success Plan Templates
    • Success Plan Types
    • Success Plan Objective Categories

    This feature is implemented in only the NXT version.

    Thanks for posting!

    Terms & ConditionsCookie settingsAccessibility statement