Skip to main content

Hide playbooks in NXT

  • April 9, 2020
  • 5 replies
  • 64 views
hardik_mota
Forum|alt.badge.img+4

Hi Team,

One of the customer is looking to hide playbooks in NXT tenant?

Use case here : Playbooks were built as part of the original implementation; they are very generic and function more as guidelines. User would like to keep the guidelines as reference as user builds his own specific playbooks for actual CSM use.

Best,

Hardik

Hardik
    jean.nairon
    phani_kumar
    sai_ram

    5 replies

    john_apple
    Forum|alt.badge.img+5
    • john_apple
    • Expert ⭐️
    • April 9, 2020

    Hi @hardik_mota - they can create a new CTA Type (e.g. Not in Use), then assign all those built-in playbooks to the new type. Lastly, go back to Call to Action Configuration and make that type inactive. The admin can still see the playbooks on the backend but the end user wouldn’t even have the option to see the Type when creating CTAs

    phani_kumar
    sai_ram
    gunjanm
    sai_ram
    Forum|alt.badge.img+1
    • sai_ram
    • Expert ⭐️⭐️
    • April 16, 2020

    @john_apple Thanks for the workaround!

    john_apple
    CurtisValentine
    Forum|alt.badge.img

    @hardik_mota - I’ve used @john_apple’s trick as well. The inactive trick works well. 

     

     

     

     

    sai_ram
    sai_ram
    Forum|alt.badge.img+1
    • sai_ram
    • Expert ⭐️⭐️
    • September 16, 2020

    @hardik_mota - I’ve used @john_apple’s trick as well. The inactive trick works well. 

     

     

     

     

    @All, awesome, I like the workaround. 

    phani_kumar
    Forum|alt.badge.img+3
    • phani_kumar
    • Gainsight Employee ⭐️⭐️
    • September 16, 2020

    Hi @hardik_mota - they can create a new CTA Type (e.g. Not in Use), then assign all those built-in playbooks to the new type. Lastly, go back to Call to Action Configuration and make that type inactive. The admin can still see the playbooks on the backend but the end user wouldn’t even have the option to see the Type when creating CTAs

    Nice workaround @john_apple.

    Tested and working as expected.

    sai_ram
    gunjanm
    Terms & ConditionsCookie settingsAccessibility statement