New features
- Fill out and submit custom forms. The Custom Forms area in the primary navigation is now a working submission flow — not a placeholder. From Custom Forms > New, pick any published template and (optionally) attach a location or pool, then fill it out and submit. This closes the loop on the form template builder that shipped earlier this week.
- Dynamic rendering that respects conditional logic. Every field type from the builder — short/long text, number, date, dropdown, multi-select, checkbox, multiple choice, and signature — renders inline in the submission form. Show/hide rules and formula conditions are evaluated live as you type, so follow-up questions appear only when they apply to your answers.
- Repeatable sections. Templates that use repeatable sections (for example, one row per pool or per piece of equipment) now expose Add and Remove controls at submission time, so you can capture as many entries as the visit requires without leaving the form.
- Inline validation before submit. Required fields, number ranges, and other rules from the template are checked as you go. If anything is missing or out of range, the submit button is blocked and each affected field shows a targeted error message — no more guessing which field the form is unhappy about.
- Read-only receipts after submit. Once a submission goes through, the form switches to a read-only view of exactly what was captured, so you (and anyone with access) can revisit the record as evidence without risk of accidental edits.
Updates
- “Custom Forms” navigation now points to the real flow. The primary-nav Custom Forms entry used to lead to a placeholder — it now opens the live submission picker. See Navigation and user experience for where it lives.
- Forms status page refreshed. Forms and Exports Status now lists the submission runtime as live and calls out what’s still planned next (submission-time signature capture, notifications, recurring forms, approvals, public links, and completed-form exports).
- Server-side revalidation. Every create, update, submit, and discard action revalidates the submission against the template on the server as defense in depth, so submissions that reach the database are guaranteed to satisfy the template’s rules — even if a client-side check is bypassed.