CTA Boolean Fields should display as Checkboxes in CTA Layout

+1 definitely feel like this makes for a better experience. 

100% agree - visualizations should always be geared to the perspective of the end user.  

and technically speaking, a Boolean can’t have three options so it’s not even a proper implementation. If Gainsight wants a...trinary? field type to capture true/false/no one bothered to fill it out great, but a Boolean isn’t it.

All, our design team is working on improving this experience. It makes sense NOT to have a dropdown for a boolean option. We will definitely change this. Thanks for the feedback.

Hi,

Is there a status on this one? We are facing a similar issue and would really like a Boolean checkbox for our process. 

Thank you,

Because there are two schools of thought around whether or not boolean fields should be displayed as checkboxes or not and since Gainsight has gone back and forth several times over the years, why not let the customer decide how they want this done for their own environment?  Give us the option to have them displayed either as checkboxes or a lov in the Administration→ General area or someplace similar.

@sverbanic Options! That would be great. We as admins are often forced to adapt once of those schools of thought for many areas in the platform...sharing this in the Global Gainsight Admins Slack as I am sure there will be lots of chatter about this very phenomenon. 

I’m actually coming to this from the other direction. As the current UI shows three options for this field on the CTA, my teams have requested that the field is NULL by default — to allow it to be configured “close mandatory”, thus requiring an explicit choice by the user before closing the CTA.

Rules Engine doesn’t support setting the value to NULL when creating a CTA even though the UI suggests it’s possible.

I don’t mind which way it’s fixed really but it’s currently ambiguous and confusing — both in the end-user UI and in the admin CTA detail view layout config.

Unless they are creating the CTA and closing it in the same action, then ‘close mandatory’ won’t pick it up :)

Yes, exactly! Because of the yes/no/none options, users are requesting something that’s not possible because the UI suggests that it could/should be