Atlas Forms
Navigate Action
The navigate action routes the browser to a URL without submitting the form. Use it to guide users to a related page, a next step in a multi-form flow, or an external resource — while leaving the current form data intact.
Navigate vs Cancel vs Link
| Action | Submits Data? | Validates? | Target |
|---|---|---|---|
| navigate | No | No | Any URL |
| cancel | No | No | Back / configured URL |
| link | No | No | Child form by record key |
| submit | Yes | Yes | onSubmit callback (may navigate) |
Schema Example
{
"type": "navigate",
"label": "View Audit Log",
"variant": "secondary",
"icon": "clock-rotate-left",
"config": {
"url": "/audit-log?formId=13001",
"target": "_blank"
}
}URL Templates
The url field supports simple template substitution using current form values:
{
"type": "navigate",
"label": "View Related Policy",
"config": {
"url": "/policies/{{values.policyId}}",
"target": "_self"
}
}The {{values.fieldId}} pattern is replaced at runtime with the current field value.
Target Options
| Target | Behaviour | Use Case |
|---|---|---|
_self | Navigate current tab (default) | In-app navigation |
_blank | Open in new tab | External links, documentation |
Navigate After Validation
If you need to validate the form before navigating (e.g., to pass values to the next page), combine navigate with submit or use a custom action instead. The pure navigate action does not validate.
Multi-Form Wizard Navigation
In a multi-form wizard (step 1 → step 2 → step 3), navigate actions power the step-to-step links. Values from step 1 are saved to the workflow context before navigation:
// Step 1 form: save + navigate to step 2
{
"actions": [
{
"type": "submit",
"label": "Continue to Step 2",
"variant": "primary",
"config": {
"successNavigateTo": "/wizard/step-2?sessionId={{meta.sessionId}}"
}
}
]
}