Over the past few weeks we have released several improvements to Forms based on user feedback, including new features for form management, enhanced export formatting, richer case and location integration, and critical bug fixes.

New Features

Delete Form Submissions — Users can now delete individual form submissions directly from the submissions list. A confirmation dialog prevents accidental deletions. This addresses the issue of duplicate or incorrect submissions polluting report data.

Duplicate Form Confirmation on Cases — Adding a form to a case that already has that form will now display a confirmation prompt, preventing users from accidentally creating duplicate form entries.

Form Submissions on Locations — Form submissions can now roll up to the Location level. A new "Show on Locations" toggle in the Form Builder lets you control which forms appear on Location screens. If a Form has both Show on Cases and Show on Locations, submissions made from a case are visible on the associated location, and edits sync across both views. Forms with Show on Locations can also be added directly to a location without a case association.

Pre-populate Case Data in Forms — Forms can now be configured to automatically capture Case data on creation (e.g., Case ID, display name, Owner Team, etc.) when added to a Case. This context is stored with the submission and included in exports, reducing manual data entry as well as making it easy to trace submissions back to their originating case.

In-Progress Status for Forms on Cases — Forms on cases now show a more granular status progression: Started → In Progress → Completed. Saving a draft form for the first time automatically transitions it to In Progress, making it easy to distinguish between untouched and partially completed forms.

Submitter Data on Submissions — Form submissions now capture the name of the logged-in user who submitted the form. Anonymous submissions are labeled accordingly.

Improvements

Improved CSV Export Formatting for Multi-Value Fields — Multi-value fields (multi-select, checkbox groups, multiple dates, etc.) are now exported as clean comma-separated values instead of raw JSON arrays with brackets and quotes. This restores compatibility with downstream reporting tools and macros.

Human-Readable Date/Time in Exports — Datetime fields in CSV exports now use a user-friendly format (e.g., 4/6/2026 16:51 PST) localized to the exporting user's timezone, replacing the previous ISO 8601 format.

Updated Pre-Populate Fields on Cases — The list of available pre-populated case fields has been refreshed. New fields include Customer Name, Location Name, Owner Team Name, and Owner User. Legacy field-service metadata fields have been removed, labels have been cleaned up.

Cascading Form Deletion — Deleting a form now properly cleans up all related resources, including form submissions, action executions, and action registrations across Journeys and Cases.

Bug Fixes

Signatures now save correctly — Fixed an issue where both drawn and typed signatures were deleted upon saving or submitting a form.

Pre-populated fields persist — Fixed a bug where pre-populated form fields in Journeys would appear empty when re-opening the form task after saving.

Export date range corrected — Fixed a timezone-related issue where exporting form submissions with today as the end date excluded today's submissions.

Multi-select picklists work on Cases — Fixed multi-select dropdowns failing to open when a form was displayed in the Case modal.

Resolved intermittent "No submission ID found" errors — Fixed an issue where forms added to a case would intermittently fail to open, displaying "No submission ID found" or "Unable to display form." The form action now supports synchronous start to ensure the submission ID is reliably returned.

Clear button visible on multi-select fields — Fixed the clear (X) button on multi-select fields not rendering when the "Can Clear" option was enabled in the form builder.

Required field validation no longer triggers on load — Fixed a bug where required fields on forms opened from a Case immediately displayed validation errors before the user interacted with them. Validation now only triggers after the user enters and modifies a field.

Form submission pagination fixed — Resolved an issue where changing pages on the form submissions list had no effect.