Currently, when using Automation to send Update Requests, there is no way to enforce mandatory (required) fields for users completing the request. This creates data quality issues, as users can submit incomplete updates, even when certain fields are critical.
Proposed Enhancement
Add the ability to mark specific fields as mandatory within an Update Request generated by an Automation workflow.
- Admins/builders should be able to select which fields are required
- Users should not be able to submit the update unless those fields are completed
- This setting should apply only to the Update Request (not necessarily the column’s global validation)
Business Use Case
- Ensuring required status updates, dates, or approval fields are always completed
- Reducing follow-up emails and manual data validation
- Improving data accuracy for reporting, dashboards, and downstream automations
Current Workarounds
- Manual review and follow-ups
- Additional automations to detect blanks
- Training users to complete fields (not reliable)
Impact
This enhancement would significantly improve data integrity, automation reliability, and user accountability, especially for enterprise-scale workflows and governance-heavy environments.
