Entry Revisions
Track changes to entries over time with revision history.
Entry revisions let you track changes to form submissions over time. Every edit creates a revision, allowing you to see what changed, when, and by whom.
How Revisions Work
When revisions are enabled:
- Initial submission creates the first version
- Each admin edit creates a new revision
- Previous versions are preserved
- You can view any historical version
Enabling Revisions
Revisions are enabled by default for new forms. To check or change:
- Go to form settings
- Find “Entry Revisions” section
- Toggle revision tracking on/off
Note: Disabling revisions doesn’t delete existing revision history.
What Creates a Revision
Actions That Create Revisions
- Admin edits to entry values
- Workflow updates to answers
- Bulk updates
Actions That Don’t Create Revisions
- Creating a new entry
- Viewing an entry
- Workflow runs (the run itself, though value changes do)
Viewing Revision History
Access History
- Open an entry
- Click the History tab
- See all revisions listed
Revision List Shows
| Information | Description |
|---|---|
| Revision number | Sequential version number |
| Timestamp | When the change was made |
| Author | Who made the change |
| Changed fields | Which fields were modified |
View a Specific Revision
- Click a revision in the list
- See the entry as it was at that point
- Compare with current values
Comparing Revisions
Side-by-Side Comparison
- Select two revisions
- Click Compare
- View changes highlighted
The comparison shows:
- Added values (green)
- Removed values (red)
- Changed values (yellow)
Understanding Diffs
For each changed field:
- Old value
- New value
- Who changed it
- When it changed
Restoring Previous Versions
Revert to Revision
- Open the revision you want
- Click Restore This Version
- Confirm the action
This creates a new revision with the old values, preserving the history.
Partial Restore
To restore only specific fields:
- Note the values from the old revision
- Edit the current entry
- Update only the fields you want
- This creates a new revision
Revision Data Structure
Each revision stores:
{
"revision_id": "rev_abc123",
"entry_id": "ent_xyz789",
"created_at": "2024-01-15T10:30:00Z",
"created_by": {
"type": "user",
"id": "usr_123",
"email": "[email protected]"
},
"answers": {
"name": "John Smith",
"email": "[email protected]"
},
"changed_fields": ["name", "email"]
}
Revision Authors
Revisions track who made changes:
User Edits
Shows the admin user:
- User name
- Email address
- User ID
Workflow Updates
Shows the workflow:
- Workflow name
- Trigger type
- Run ID
API Updates
Shows API context:
- API key name
- Request metadata
Use Cases
Audit Trail
Track changes for compliance:
- Who changed what
- When changes were made
- Original values preserved
Error Recovery
Undo mistakes:
- See what was changed
- Restore previous values
- Maintain data integrity
Change Review
Understand data evolution:
- Track how entries progress
- See workflow modifications
- Debug data issues
Best Practices
Revision Management
- Keep revisions enabled for important forms
- Periodically review revision settings
- Consider storage implications for high-volume forms
Documentation
When making significant edits:
- Use metafields to document why
- Keep a log of major changes
- Train team on revision usage
Access Control
Consider who can:
- View revision history
- Restore previous versions
- Make edits that create revisions