Database and content
Build a form that saves visitor submissions
Div-idy can build a React form that sends visitor submissions to your project database. Tell the builder which fields to collect and what the receipt should say. Review submissions in the Database tool. Visitors can send a record, but cannot use this form workflow to read, edit, or delete saved submissions.
Which forms fit this workflow?
Contact requests, waitlists, event RSVPs, testimonials, feedback, and service inquiries fit the one-way submission model. A booking request can collect preferred dates, but its receipt should say the request was received. Receiving a record does not confirm availability, process payment, or reserve an appointment.
Search boxes, calculators, and category filters can work entirely in the browser. They need a database only if the requested workflow actually saves information for the project owner.
Describe fields, validation, and the receipt
- List each field and mark required fields clearly.
- Set reasonable text limits and explain any choices or dates.
- Request a visible saving state and disable the Submit button while saving.
- Show a receipt only after the database confirms success.
- Keep entered information on failure and provide an explicit retry control.
New React output uses Div-idy’s data.submit runtime method. Built-in connection details come from the current project; you do not need a separate database setup screen.
Example: collect workshop RSVPs
Build a mobile-friendly workshop RSVP page with name, email, workshop choice, and an optional note. Save each RSVP to the project database. Validate required fields, prevent double-click submission, and keep the form filled if saving fails. After a confirmed save, say “Your RSVP request was received.” Add a link back to the workshop information.
Verify the visitor and owner experience
Submit recognizable sample information and find the matching record in Database. Check required fields, invalid email formatting, a long message, the loading state, and the success receipt. Test the published page as a visitor as well as the private preview.
Decide how you will handle received requests. A saved database record does not automatically send an email, add a calendar event, or connect an external customer-management system.
Keep the collected data within scope
Submissions support up to 12 KB per record and 4,000 characters per text field. This endpoint is for compact non-sensitive form data, not file uploads, passwords, payment details, medical records, or secrets.
For editable public catalogs or articles, use owner-managed content. For access boundaries, read project data permissions.