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
  • Deployment workflow
  • Variant Revision UUID
  • Pinning
  • Superceding past revisions of a variant
  • Check variant caching

Was this helpful?

  1. Building flows
  2. Publishing and versions

Deploying

Deploying a Formsort flow to the world.

PreviousPreview windowNextHistory

Last updated 1 year ago

Was this helpful?

Deployment workflow

To deploy a flow, making your changes visible to responders who are sent to it, click Deploy at the top right of the flow editor.

If you've already published the flow you are editing, the button will instead show Redeploy.

Here you can:

  • add a note about the deployment changes

No in-studio changes to flows or variants will be "live" until the variant is re-deployed to the production environment. This includes Theme changes, changes to logic and variables, and changes to integrations.

Variant Revision UUID

Pinning

We refer to this as "pinning" a user, and it allows for logical and visual continuity of the end user experience while also providing more useful cohorts for analysis: deploying a new version will not affect the experience of responders that are in-flight on an older version.

Preventing pinning

Pinning can be circumvented two ways:

  • By loading a form in your browser's incognito window. No responder_uuid or variant_revision_uuid is stored in an incognito session.

Pro-tip: If you are trying to test the most up-to-date revision of your form but keep getting old revisions loaded because you are pinned, navigate to the form in an incognito window!

Superceding past revisions of a variant

By enabling supercede past revisions of variant? when you publish, you will force responders who started on an older revision of your variant onto the newest revision being published.

Superceding on deployment is useful for pushing fixes to content or logic errors or updating content and styling. Keep in mind, however, that superceding will not bring responders who have visited a different variant onto the newest revision of a variant that is "superceding on deployment".

Currently, when a flow is superseded, a returning responder will have to start from the beginning.

We may change this in the future, providing more control over what to do with returning responder data, but keep this in mind for now.

Check variant caching

It is possible to check which flow variant and variant revision is cached, by poking around your browser. It takes a little digging, but it's a pretty simple process!

With your live flow pulled up in a regular browser window (not incognito), right click + inspect.

When the sidebar window opens, click Console, paste in the following code, and press Enter.

localStorage.getItem('LOCALSTORAGE_VARIANT_UUIDS_KEY') || sessionStorage.getItem('STORAGE_VARIANT_UUIDS_KEY')

You will see that a variant label is returned, as well as the variant_revision_uuid and the environment the variant was deployed to.

Depending on how many flows have been cached, you may see several different variants listed!

choose which your changes will be deployed to

enable of existing variants

customers have access to alternate deployment environments by default - Production and Staging - with the option to create more.

Once the form is deployed, a new variant revision uuid will be created. If you have any configured , a Variant revision published event will be sent to that endpoint.

Whenever a variant is deployed or redeployed to any (production, staging, etc...), a 36-character variant_revision_uuid is created for that deployment to identify the state the variant is in. These variant revision UUIDs can be found in the tab of the .

A variant_revision_uuid is cached in a responder's browser once they load a form and begin interacting with it, exactly like a . This forces the the same variant and variant revision to be loaded upon return visits, which ensures the responder will see the same content, style, and logic as they did when they first visited.

To bring returning responders on to the most up-to-date revision of your variant, see below.

By enabling

If you would like ensure returning responders do not load deprecated variants, see our redirect to URL section in .

๐Ÿ—๏ธ
environment
Enterprise
subscriptions
ResponderUUID
superseding
superseding existing versions
environment
start each session as a new responder
History
variant
archiving flows
The deploy menu