New Idea
Conditional field logic (show/hide and required/optional) for Timeline activity fields
Summary
Admins should be able to make a Timeline activity field visible, hidden, required or optional based on the value of another field on the same activity. Today the only conditional behavior is dependent dropdowns, which limit the values inside a field. They can’t control whether a field appears or is required.
Proposed capability
- Conditional visibility: Show or hide a field based on another field’s value (at minimum dropdown, picklist and checkbox fields).
- Conditional required/optional: Make a field required or optional based on another field’s value.
- Consistent enforcement: Apply the rules in the Timeline UI, the Timeline API and MCP. AI Follow-Up activities currently log mandatory fields blank, so the rules should apply there too.
- Stretch goal: The same capability for CTA detail layouts, as requested in the Community threads.
Impact
- Better data quality without longer forms.
- A single activity type with consistent reporting.
- Smoother adoption as teams expand AI Follow-Up and brings in more teams.
- Add volume if you have it: [no-show activities per month / number of CSMs affected].