Required CTA field on creation

Hi Alex,

Thanks a lot for sharing this use-case. Are these mandatory fields required for all CTA types or only for specific ones? Also how would this work when updating a CTA? (Do you mean that these fields cannot be empty at any point of time?)

Regards

@alex_legay please reply to @aditya_marla 

I’ll defer to @lesliesmith to confirm the below.

It may be dependent on the type but I suppose giving the option to have it to for each type would be the most flexible.

In the specific scenario, I think it be always required even when updating the CTA.

Got it….so basically the fields cannot be empty at any point of time

I just ran into this myself. Use case is that the CTA is being used to request help from another internal team within Gainsight. We want to make additional fields required just on this CTA type so that the team gets all of the info that they need to fulfull the request, but we can’t do that.

This would be great to have along side “Close Mandatory”. For objectives, we want to require a custom field for “initial value” and for “target value” at the time of creation, but there is no way to enforce that

We would also like to be able to require fields on Objectives to track target values and value information.

Is there an update on this? I have a use case where my org would like to make a custom field that is not visible by default in the Default view section of a CTA required to ensure this field is not missed.

It would be great to see this feature added to the roadmap, we also have a use case where we want to use a CTA to be created to assign work to another teammate to request SME engagement support to the CSM and need certain custom fields to be mandatory upon creation