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
  • Flows
  • Editing flows
  • Archiving flows
  • Viewing archived flows
  • Variants
  • Duplicating variants
  • Archiving variants
  • Un-archive flows and variants

Was this helpful?

  1. Building flows

Flows and variants

PreviousAllow responders to read and accept your company policiesNextFlow starts

Last updated 9 months ago

Was this helpful?

Flows

A flow collects information to fulfill a specific goal within your organization: for example, a new user application flow, a collecting-feedback flow, a matching-to-an-agent flow. A flow may have multiple versions - called - which exist to try different designs on your form function; like an A/B test!

Editing flows

You can edit the Display name of your flow. This only updates the name of the flow as it appears in your studio - it will not update the URL slug associated with your flow.

Archiving flows

To archive a flow, select the flow in the list and click Archive. This will remove it from the list of visible flows, and prevent new and returning responders from being able to access the flow. This can be thought of as deleting the flow, however archiving allows you to re-activate the flow in the future, if necessary.

Archiving a flow will by default archive all the variants inside of it.

Redirect to URL

When archiving, setting a Redirect to URL will ensure that new or returning responders attempting to access the archived flow will be redirected to the URL of your choosing.

Redirecting traffic in this way is useful when:

  • There are links out in the wild that still point to an archived flow.

If no Redirect to URL is set, the user will be shown a "failed to load" screen.

See our section on Split Testing for more information on iterating on flows and variants, and archiving old versions when it's time to deprecate.

Viewing archived flows

To view an archived or deleted flow, change the filtering options to the right of the flow table's search to make archived and deleted flows visible.

Variants

Variants exist within a flow, and are generally used to make small variations to the same flow content. Think of variants as a form A and form B in an A/B test, which allows you to constantly measure and iterate on your flow to ultimately improve the responder experience.

Duplicating variants

The Duplicate feature allows you to duplicate variants so that you can make variations on a flow. These changes can be wildly different from one another in terms of style and content, but should still have the same goal and collect the same information as the other variants in the same flow.

To make a copy of a variant, you can either:

  • Select Duplicate from the dropdown while in the variant list section (seen in pic above).

  • Click Save as at the top right when you have a variant open.

In either case, you will be presented with a modal that will give you three options:

  • Add the duplicate to the list of variants in your current flow.

  • Move the duplicate into another flow in your Studio.

  • Use the duplicate to create an entirely new flow.

You will also need to give the duplicate a new name, and if desired, assign a new URL slug as well.

Archiving variants

Setting a Redirect to URL works the same as well - any users who have previously accessed this variant will be redirected to the new variant upon returning, or any users with the specific link to this variant will be directed to the new URL if they try to access that link.

Un-archive flows and variants

To unarchive a flow or variant, change the filtering options to the right of the table's search to make archived items visible.

Hovering over an archived item will reveal a "restore" icon. Click the icon.

The "undo archive" process can be used for restoring archived flows and variants, when in either menu.

Due to the ability for Formsort to restore archived flow and variants, names for archived entities cannot be re-used.

Returning responders have an archived cached in their browser, which will attempt to load the archived flow on their return visit.

Additionally, the editor for a flow can be found in this section - since the different variants within a flow will all function to collect the same data, it makes sense to send the data to the same place for all variants!

Not happy with the current URL slug of your flow? If you are not planning on using a , use this duplication process to create a new URL slug.

Variants may be archived by selecting a variant and choosing Archive. This will have a similar effect to what happens to archived flows described : no users, returning or new, will be able to access the variant.

You can view your archived variants with the "Hide/Show archived" hamburger menu at the top right. It's a similar process to viewing .

๐Ÿ—๏ธ
Integrations
Custom Domain
above
archived flows
variants
variant UUID
The top-level view in your Studio, and the list of flows
The variant list for the Follow-Up-Flow
"Show archived" to make archived items visible