Submit actions control what happens after a user successfully submits a form. They enable you to create workflows by directing users to specific pages, showing confirmation messages, or triggering external redirects based on form data.
What You'll Learn
- How to create and configure submit actions
- Ways to manage multiple conditional redirects
- Methods for building form completion workflows
- Techniques for implementing confirmation messages
- Best practices for user navigation flows
- Solutions for common submit action challenges
Basic Configuration
Default Submit Action
- Every form includes one default action
- Cannot be removed or have conditions
- Serves as fallback when no other rules match
Available Actions
1. Confirmation Message
- Display custom confirmation text
- Optional form reload link
- Auto-reload functionality
- Fade transition effects
2. Page Redirects
- Existing page navigation
- Parent page return
- External URL redirect
- New child page creation
Action Management
Creating Actions
- Access Form Settings
- Select "Actions & Rules"
- Choose "Submit Actions"
- Click "Add Rule"
Editing Actions
- Modify conditions
- Change redirect targets
- Update confirmation messages
- Reorder action sequence
Action Organization
- Drag-and-drop reordering
- Copy existing actions
- Multiple conditional paths
- Priority management
Conditional Logic
When Criteria
- Field-based conditions
- Multiple condition support
- All conditions must be true
- Not available for default action
Rule Processing
- Top-to-bottom evaluation
- First matching rule executes
- Default action as fallback
- Condition verification
Implementation Examples
Common Workflows
1. Record Creation Flow
* Submit new record
* Show confirmation
* Return to record list
2. Multi-step Process
* Complete current step
* Redirect to next form
* Track progress
3. Thank You Sequence
* Submit final data
* Show confirmation
* Redirect to completion page
Best Practices
Action Structure
- Keep default action simple
- Order rules from specific to general
- Use clear confirmation messages
- Maintain logical navigation flow
User Experience
- Provide clear next steps
- Confirm successful submissions
- Enable form resubmission when appropriate
- Maintain context in redirects
Troubleshooting
Common Issues
- Conflicting action rules
- Unexpected redirects
- Missing confirmations
- Condition evaluation errors
Solutions
- Verify rule order
- Check condition logic
- Test all submission paths
- Validate redirect targets
Technical Notes
Limitations
- One default action required
- Default action cannot have conditions
- Multiple conditions require all true
- Same-trigger rules use last match
Related Resources
- [Form Element Guide]
- [Page Navigation Setup]
- [Condition Building]
- [Workflow Design]
Tip: Plan your submit action sequence before implementation to ensure a logical flow for users.
Note: The default submit action serves as a fallback and will trigger when no other conditions match.