counterparty-address-optional-ui-triage
Counterparty Address: Optional Config vs Mandatory-Looking UI
What This Skill Debugs
Customers report that counterparty address during contract creation (especially after Add new counterparty) shows required-field markers (asterisks), while validation still allows skipping the step or saving with incomplete data when the Creator Party Questionnaire marks Party Information → Counterparty Address as Optional.
This is primarily a product/UX consistency issue, not a backend outage. Engineering discussion in the Dec 2025–Jan 2026 incident concluded that some behavior was intentional (required markers apply to partial address entry rules), but the add-new-counterparty flow cannot mirror the clearer “Add address” pattern used elsewhere—creating confusion and a platform-level UX backlog to align copy, banners, and when asterisks appear.
Known customer example (do not hardcode in new tickets): Prompt Health, WSID 274685, cluster US — see SPD-39313, Rootly #2699, Slack #incident-20251217-low-prompt-health-counterparty-address-marked-as-mandatory-but (C0A466WLML5).
When to Use / Not Use
| Use this skill | Use a different skill |
|---|---|
| UX mismatch: asterisks vs ability to skip / partial save on counterparty address | questionnaire-hidden-variable-data-loss — integration-sourced questionnaire values cleared on edit |
| Clarifying two different settings (workflow vs modal / questionnaire) | hubspot-sfdc-conditional-overpersistence — wrong persistence of hidden conditional fields at creation |
| Customer not blocked but confused; need talking points and Jira context | email-delivery-triage — counterparty not receiving email |