Formsort
Search…
Formsort
Formsort documentation
Building flows
Core concepts
Adding content
Using markdown
Steps
Settings
Logic
Style
Questions and content
Organizing using groups
Using answers in templates
Copy-paste of form content
Content types
Conditions and logic
Schemas
Redirects
Styling and themes
Publishing and versions
Handling data
Philosophy
Data retention
Responder UUIDs
Environments
Passing data in
Getting data and events out
Integration reference
Going live
Custom domains
Built-in analytics
Embedding
Split testing
Preflight checklist
Teams
Accounts
Event subscriptions
Powered By GitBook
Settings
Step-level settings.

Step ID

Since steps are easily re-arranged within the flow, it is useful to assign a step ID to a step to maintain stable references to steps, as their index within the flow or text labels may change. This is particularly useful in the context of analytics, where understanding how the same step performs across versions is important.
Step IDs are not required - if they are not set, the step index will be sent along with any analytics event payloads. When set, they are required to be unique.
To include Step ID in the form submission payload, add the current step id library variable.

Auto-advance after ms

If defined, Formsort will attempt to advance to the next step after the specified timeout. This allows making interstitial screens that show information to a responder without requiring them to provide any answers.
This will only succeed if the responder has provided valid answers to all of the questions on the current step, the questions are all optional, or the content on the step does not require answers, such as informational content.

Is savepoint

If your answer submission frequency is set to On savepoint, checking Is savepoint will ensure that the responder's answers are submitted to your destinations at the completion of this step.
Previous
Steps
Next
Logic
Last modified 10mo ago
Copy link
Contents
Step ID
Auto-advance after ms
Is savepoint