Searched and found this post showing “not planned”
But I think there is definitely a use case for requiring fields on CTA creation vs. only enforcing required on closure.
In my case, I’m trying to move our CS team to use CTAs for Risk tracking (to date they’re using Timeline only) but there is a requirement to track a sub-reason as well as Revenue at Risk (that may actually be a different $ amount than the total ARR tied to the customer account).
Using Timeline, you can make a field required when the activity is logged, forcing users to populate it before it can be created.
But the lack of this ability to do so in CTAs means Risk CTAs can get created without logging the At Risk Revenue Impact because it is not a required field, making it easy to forget.
I’m going to continue having a hard time convincing the use of CTAs for Risk tracking because between this request (and the ones below) Timeline does have a few more flexible features that make it appealing to our CS team as a quicker, more accurate way to record/track risks.
