Blog Sections Open
Reloading an eForm After Successful Submission
Some forms are meant to be submitted more than once in one session, so a permanent success state is less useful than reloading the form cleanly.
Most eForm examples assume that success ends the interaction: the form is submitted, the visitor sees a success message, and the form disappears. But some workflows need the opposite behavior. After a successful send, the form should appear again immediately so another entry can be added.
When This Makes Sense
- quick internal request forms
- repeated data-entry workflows
- simple lead capture forms used by staff instead of public visitors
The Main Options
- redirect back to the same page after success
- show a lightweight confirmation and re-render the form below it
- reset the form via JavaScript after a successful AJAX submission
The Safer UX Pattern
In many cases the best approach is to display a short success message and then immediately show a clean form again. That preserves user confidence without forcing a manual refresh.
The broader lesson is that “successful submission” does not always mean “hide the form forever”. The expected post-submit state depends on the business workflow, not on the default snippet example.
Making FormIt `isDate` Work with Russian Month and Weekday Names
Why localized date strings can fail FormIt validation and how to normalize the date format before running isDate checks.
Building Click-to-Open Submenus with Wayfinder
How to handle a navigation pattern where a top-level item opens its submenu on click instead of behaving like a simple direct link.