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
  • What do environments do?
  • Editing environments
  • Creating new environments
  • Saving and propagating changes
  • Deploying your variants to different environments

Was this helpful?

  1. Handling data

Environments

Configure integrations.

PreviousResponder UUIDsNextLoading different environments

Last updated 1 year ago

Was this helpful?

What do environments do?

In Formsort, environments are spaces you can deploy your variants to for different purposes, and the variant environment it is deployed to will correspond to the environment set up in .

For example, you want to test the changes your team is making to a variant in a mocked "live" environment, but also do not want these changes available to your users. In this case you'll want to set up a staging environment to run testing. First, you'd configure the staging environment endpoints (see editing environments below) to make sure you can receive test answers; then, you'll deploy your variant to the staging environment.

Non-production environments are only available to clients that are on the plan. Enerprise clients will by default have access to two environments: production and staging, plus the option to create as many as are necessary.

  • Production should always be used for the "live" version of a flow. are counted when users load and interact with flows deployed to the production environment.

  • Staging can be used to integrate with mock or test versions of your integrations, to create a production-like version of a flow that only talks to non-production systems. This is ideal for preventing production data contamination. It is optional to use staging, but for complex forms it is useful to have. Flowstarts do not count in this environment.

  • You can if you need them. Flowstarts do not count in any new environments created. Test away!

Editing environments

Environments are defined per flow, and are shared across all of that flow, to ensure data integrity between variants.

From the flow index page, the Integrations tab will show the environments editor for your integrations.

Here it is possible to edit all aspects of integrations:

  • create a new integration environment (e.g. create a "dev" environment)

  • configure setup for a new integration target

  • make updates to existing integration targets

Since adjustments are made on a per-environment basis, your production environment will likely have a different integration configuration than your staging environment.

Creating new environments

Clicking Edit... on the top right of the environment editor shows a list of the current environments and allows the addition of new environments. You will see that a production and staging environment are added by default.

Click +Add environment if you'd like to create a new environment. You can also delete environments in this menu.

Once you've added a new environment, you will see it's availability in the dropdown list of environments.

Saving and propagating changes

When changes have been made to any of the integrations, you will be prompted to save them, regardless of which environment you are in.

Deploying your variants to different environments

For instance, if integration changes have been made in your staging environment, make sure to deploy or redeploy any variants you are using to staging.

After saving the changes you've made to your integrations, your live variants need to be to the matching environment so that the changes can be propagated to your flow.

When you're ready to test, proceed to . Happy testing!

๐Ÿ’พ
redeployed
Loading different environments
integrations
Enterprise
Flowstarts
variants
create new environments
Newly-created dev environment is available.
Save your changes