LogoLogo
Back to studio
  • Formsort documentation
  • โฉQuickstart
    • ๐ŸŸขGet started with Formsort
    • ๐ŸŽCore concepts
    • โ„น๏ธQuestion and content reference
    • ๐Ÿ“•Key terms
    • ๐Ÿž๏ธCreate your first flow
    • ๐Ÿ“–Add content and collect answers
      • ๐ŸคณCapture demographic data
      • โ„น๏ธAdd informational content
      • ๐Ÿ” Review your variable schema
    • ๐ŸŽจCreate a theme
      • Set brand guidelines
    • ๐ŸคนPersonalize your flow
      • ๐ŸŒŸTemplate your variables
      • ๐Ÿง Add conditional logic
      • ๐Ÿ’ซUsing conditional logic with Calculated and API variables
      • ๐Ÿ”šEnd the flow
    • ๐Ÿ”€Set up integrations
    • ๐Ÿš€Go live
      • Auditing your flow for content, functionality, and design
    • ๐Ÿ’ผCommon use cases
      • ๐Ÿ’”Disqualify responders
      • ๐Ÿ—“๏ธAdd a scheduling option
      • ๐Ÿ“„Allow responders to read and accept your company policies
  • ๐Ÿ—๏ธBuilding flows
    • Flows and variants
      • Flow starts
    • Adding content
      • Groups
      • Steps
        • Settings
        • Logic
        • Style
      • Questions
        • General Settings
        • Style
        • Address
        • Comparison
        • Confirmation
        • Date
        • Date & Time
        • Email address
        • File upload
        • Grid choice
        • Iframe
        • Image upload
        • Number
        • Payment
        • Phone number
        • Postal code
        • Question group
        • Region
        • Select
          • Providing choices via API or calculation
        • Signature
        • SSN
        • Text questions
        • Yes/No
      • Content
        • General Settings
        • Statement
        • Image
        • Video
        • Next button
        • Divider
        • Map
      • Endings
      • Using markdown
      • Using variable templating
        • Template formatting functions
      • Copy-pasting form content
      • Content library
    • Conditions and logic
      • Logical operator reference
      • Advanced logic
    • Variables (answers)
      • Variables from questions
      • Externally provided variables
      • Calculated variables
      • API lookups
      • System Library variables
      • Orphaned variables
    • Schemas
      • JSON Schemas
      • Validating flow schemas
    • Redirects
    • Styling and themes
      • CSS Reference
      • Overriding theme styling
      • Custom CSS overrides
      • Content area
      • Animations and transitions
      • Form Layout
      • Typography
        • Adobe Fonts
        • Hosting custom fonts
      • Color variables
      • Dimension variables
      • Question containers
      • Assets
      • Form Buttons
        • Select buttons
      • Inputs and dropdowns
      • Checkmarks
      • Tables
      • Sliders
      • Divider lines
      • Progress bar
      • Comparison cards
    • Variant settings
      • Form behavior for returning responders
      • Group ranking API
    • Publishing and versions
      • Preview window
      • Deploying
      • History
  • ๐Ÿ’พHandling data
    • Philosophy and data retention policy
    • Viewing form answers
    • Responder UUIDs
    • Environments
      • Loading different environments
    • Passing data in
      • URL parameters
      • POST body
      • Embed query parameters
    • Custom validators
    • Form answers and events
      • Analytics events
      • Signed requests
      • Event payload shape
      • Submission frequencies
      • Runtime error reporting
      • Admin API
      • Flow content data format
    • Integration reference
      • Amplitude
        • Amplitude cross domain tracking
      • BigQuery
      • FullStory
      • Google Analytics
        • Updating from Universal Analytics to GA4
      • Google Cloud Storage
      • Google Sheets
      • Google Tag Manager (GTM)
        • JavaScript triggered by flow events
      • Hubspot
      • Jornaya
      • Optimizely
      • PostgreSQL
      • Redshift
      • Rudderstack
      • S3
      • Salesforce
      • Segment
        • Segment Setup
        • Segment cross domain tracking
      • Stripe
      • TrustedForm
      • Webhooks
        • Zapier
  • ๐Ÿ“บGoing live
    • Custom domains
    • Built-in analytics
    • Embedding
      • Web-Embed API
        • React-embed
      • Adding authentication
      • Embedding forms in iOS and Android
      • Setting up a dev environment
    • Split testing
    • Preflight checklist
  • ๐ŸขTeams
    • Accounts
      • Roles and permissions
    • Events subscriptions
    • Workspace domain detection
Powered by GitBook
On this page
  • Document Title
  • Answer required text
  • Footer Text
  • Optional question label
  • Behavior
  • Enable URL navigation
  • Use step ID instead of index
  • Enable restart once flow completed
  • Enable close once flow completed
  • Enable autosave

Was this helpful?

  1. Building flows

Variant settings

The Settings menu gives you more control over your Flow's behavior.

PreviousComparison cardsNextForm behavior for returning responders

Last updated 5 months ago

Was this helpful?

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. to head there!

Document Title

The text here will update the name of browser tab that your flow opens in.

Answer required text

Hiding the "answer required" text

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!

Footer Text

Optional question label


Behavior

The Behavior settings control flow behavior - continue reading to find out what each setting does!

Returning responder behavior

Enable URL navigation

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

Use step ID instead of index

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>

Enable restart once flow completed

Answers are only cleared at the end of the responder session. 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.

Enable close once flow completed

If your flow is embedded into another page, this will create a link to close the embed once the flow is completed.

Enable autosave

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 flag). The Answer required text is the error copy that will be shown if they try to proceed through a partially-filled step.

This text will be shown at the bottom of the , 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 . The default text shown is "optional".

See for a detailed breakdown of the settings found in the "returning responder behavior" dropdown. This section includes a description of Start each session as a new responder setting.

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 generated during their initial visit, but Formsort will discard saved answers to allow them to start the flow over.

It's worth noting that users will not see this screen if there is a set at the end of the form.

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.

๐Ÿ—๏ธ
Optional
Content area
optional
Form behavior for returning responders
responder_uuid
redirect
submission frequencies
Click here
The variant settings menu
The form behavior section