0.7.0
Released 8 September 2026.
Person accounts
Section titled “Person accounts”- Forms can now be mapped to person accounts. The field picker offers Person Account alongside Account, lists the fields available on it, and sets the form’s record type to match, so the two always agree.
- Mapping mistakes are caught before a form goes live. A form set up for business accounts that maps person account fields is now flagged when you publish, naming the fields to correct, rather than at the point someone tries to respond.
- Forms that write to both Account and Contact now save reliably on orgs that use person accounts together with the optional “reports to” setting.
Mapping
Section titled “Mapping”- Full-name fields can be mapped directly. Fields that hold a complete name are offered in the picker and marked “split into First / Last”, so a Full name question no longer needs the advanced option.
- Only fields that genuinely split are labelled that way, so the picker prompts correctly for the ones that still need an answer.
- You can choose not to link the records a form creates. Where two objects could be joined, the object model settings list each pair with the link pre-selected and an option to leave them separate.
- The Event registration starter now includes a required Company field, so registrations that become leads have everything Salesforce needs.
- New guidance for mapping a starter form. Starters arrive unmapped, and the admin guide now walks through pointing one at your own objects, including how to fill a required field that respondents never see.
A/B testing
Section titled “A/B testing”- Tests name the two versions being compared and show the traffic split you chose, so it is clear what is being measured.
- Starting and ending a test asks for confirmation, and the final completion counts are reported once when the test ends.
- A form with only one published version now explains how A/B testing works, instead of offering controls that have nothing to compare.
- Administrators who do not have access to response data can still start a test, and see it running without the completion counts.
Responses
Section titled “Responses”- The response export is now spreadsheet-ready. One column per question, headed with your own labels, with questions you have retired included and marked. Exports are no longer capped at 2,000 responses - larger exports run in the background with progress and a Cancel button - and each file is named for the form and the date.
- Exports are safe to open in any spreadsheet application, including exported translations, which can be edited and re-imported without loss.
Theming
Section titled “Theming”- Set one default theme for every form. A Default theme panel on the Admin Dashboard sets brand, text and background colours, font, corner radius and field spacing once, and every form without its own theme follows it. Forms with their own theme keep it, and Use package defaults clears the settings again.
- The panel is simpler to read, and the font list now distinguishes clearly between a font you have chosen and none at all. Forms already using the previous “System default” keep exactly the fonts they had.
Form Builder
Section titled “Form Builder”- Applying an edit and saving a draft are now clearly separate. The inspector’s button is Apply and confirms what it did; Save draft in the toolbar is what sends your work to Salesforce, and is easier to find.
- The toolbar no longer shifts as the status changes between Saved, Unsaved changes and Saving.
- A mapped field shows a Person Account badge where that is what the form writes, and longer mappings wrap instead of being cut off.
Upgrading
Section titled “Upgrading”Upgrade from 0.6.0. No configuration changes are required.
If your org uses person accounts, it is worth reviewing any form that maps both Account and Contact fields. Nothing needs changing - the improvement applies automatically.