Variant settings
The Settings menu gives you more control over your Flow's behavior.
Last updated
The Settings menu gives you more control over your Flow's behavior.
Last updated
The Settings section found in every variant allows you to control various aspects of your form, from how you'll handle returning responders to the copy they might see when they complete a flow.
These settings are defined per variant, and will not be universally applied across different variants.
The settings are split into three sections: Strings, Behavior, and Group Ranking API.
The Group Ranking API has it's own page in these docs. Click here to head there!
The text here will update the name of browser tab that your flow opens in.
By default, Formsort does not allow users to proceed through a flow without answering all the questions on screen (this setting can be toggled with an Optional flag). The Answer required text is the error copy that will be shown if they try to proceed through a partially-filled step.
The "answer required" error cannot be disabled, but it can be hidden. In the color variables menu of the Theme editor, there is an "error" variable. You can set the transparency value of this variable to 0%.
If there is no error variable, you can create one that will be responsive to coloring. Case sensitivity of the variable name matters!
This text will be shown at the bottom of the Content area, and is useful for things like disclaimers and legal notices.
The string here will show in italics at the end of a question label when it's flagged as optional. The default text shown is "optional".
The Behavior settings control flow behavior - keep reading to find out what they do!
When this flag is enabled, every time a responder returns to a flow they are treated as a new responder.
No previous answers are loaded, and Formsort will not keep a record of progress
A new responder UUID is generated at each visit
User is not pinned to a variant they may have previously seen
Any Formsort-related cookies will be cleared from the user's browser on re-load (See External variables for more information)
You can still force-set a particular responder UUID by passing the UUID in as a URL parameter, but this will not load any previous session related to the responder UUID. See Setting the responder UUID manually for more information.
When start each session as a new responder is disabled, returning responders will retain their responder UUID upon subsequent visits. This is default Formsort behavior. A user is considered a "returning responder" when they revisit a flow using the same browser they initially started their flow from.
See Reponder UUIDs for a closer look at how we create IDs for your users.
See the Returning Responder Behavior section for a detailed breakdown of the settings found in this section.
This setting:
Allows the ability to use the browser's forward and back buttons to navigate through the unlocked steps of a flow (not currently supported in embedded flows).
Allows navigation to unlocked steps using the Step Index in the URL, or Step ID if use step ID instead of step index is enabled.
A URL navigation example to navigate to the step at index 1: https://<client-ID>.formsort.app/flow/<flow-name>/variant/<variant-name>#1
As noted above, this setting, when enabled, will allow users to navigate to a specific step via the step ID of the step, rather than the step index of the step.
A URL navigation example to navigate to a step using it's ID: https://<client-ID>.formsort.app/flow/<flow-name>/variant/<variant-name>#<step-ID>
When Enable restart once flow completed is enabled, users will be given the option to restart a flow if they return to it after completing. Users will keep the responder_uuid generated during their initial visit, but Formsort will discard saved answers to allow them to start the flow over.
Answers are only cleared at the user end. Any answer payloads sent to your data stores will persist in your data store.
This is useful for forms that need to be filled out multiple times by the same users, but also forces users to fully complete a form before starting a new one.
If your flow is embedded into another page, this will create a link to close the embed once the flow is completed.
If autosave is enabled, it will cause the form to retain a responder’s answers should they leave and come back to the flow. In-progress answers are saved after 3 seconds have passed from a responder’s input. Answers will also be submitted to enabled integrations if "When the flow is finalized or abandoned" is enabled in submission frequencies.
