Safely change published forms
Extend fields, change required details and protect existing submissions from regressions
Published forms are part of a running process. Every field change can affect mappings, email templates, response columns or downstream workflows. The good news: saving only creates a new version – visitors keep seeing the live version until you set the new one live.
Capture dependencies
Note the form, public URL, mappings, confirmation email, document template and analytics. Don't judge existing submissions only in the editor.
Keep changes small
Change one field or rule at a time and secure it as a version with Save. Label and helper text are less risky than field type, field name or mapping.
Check required status
A new required field can block old links and mobile flows. Only enable it if all target groups can provide the value.
Send a test submission
Test in the preview on desktop and mobile: valid value, empty value, wrong format, upload and abort. Preview submissions are marked as Preview. Don't use real customer data.
Check the publication
Publish with Set live, load the public URL and check a test submission in the target process. Only then inform the team and external users.
Don't change field name and mapping without a plan. A visible rename (label) is something different from replacing the technical field; a renamed field name creates orphaned mappings.
Fallback plan
If something goes wrong, open the Version History, select the last working version and click Set Live. Alternatively, take the form offline with Take offline. You correct data that has already come in separately.
How is this guide?