Skip to main content
heather_hansen
heather_hansen
VIP ⭐️⭐️⭐️⭐️⭐️
June 17, 2025
New Idea

Create Ability to make fields mandatory based on CTA Status

Related products:CS Cockpit & Playbooks
  • June 17, 2025
  • 1 reply
  • 71 views

Need:
Ability to make a field required ONLY if a specific CTA status is used

Example:
We use CTAs for CSQLs, and we’d like to add a requirement to indicate why a particular status was used via a separate picklist. So, if the status used is Closed-Not Needed, we’d like to require another field for the owner to indicate why it’s not needed. That field should ONLY be required if that status is used. 

Additional thoughts - if we can’t make it required for only a specific status, the ability to have a dependent picklist based on Status would be also help resolve to a degree.

    1 reply

    alizee
    alizee
    VIP ⭐️⭐️⭐️⭐️⭐️
    November 5, 2025

    +1 on this request from a concept perspective.

    I’ll extend this requirement to TASKS too. It’d be useful if we were able to connect certain CTA and task statuses to a closing reason field that’d be mandatory if selecting those options. 

    Closing Status on CTAs an Tasks typically will contain those options:

    • Closed Success
    • Closed Unsuccessful/Incomplete
    • Closed No Action
    • Closed Duplicate

    Or something in that vein. 

    We’re looking at capturing a closing reason for ONLY some of these options, specifically anything that’s not “Success”, both at the CTA *and* the Task level. 

    However, at this org, we’re not quite ready to go for preset “closing reasons” in the form of a dropdown and would like to store that information in a string, so it can be analyzed and we can eventually, at some point, define picklist reasons, meaning the dependent fields should be possible to create as a String datatype. 

    The most expensive part of building is the mistakes. That's true in construction. Not so much in CSOps. So ask questions, make mistakes and learn. All views expressed here are my own.
    Terms & ConditionsAccessibility statement