FormWork FormWork

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:

  1. Initial submission creates the first version
  2. Each admin edit creates a new revision
  3. Previous versions are preserved
  4. You can view any historical version

Enabling Revisions

Revisions are enabled by default for new forms. To check or change:

  1. Go to form settings
  2. Find “Entry Revisions” section
  3. 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

  1. Open an entry
  2. Click the History tab
  3. See all revisions listed

Revision List Shows

InformationDescription
Revision numberSequential version number
TimestampWhen the change was made
AuthorWho made the change
Changed fieldsWhich fields were modified

View a Specific Revision

  1. Click a revision in the list
  2. See the entry as it was at that point
  3. Compare with current values

Comparing Revisions

Side-by-Side Comparison

  1. Select two revisions
  2. Click Compare
  3. 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

  1. Open the revision you want
  2. Click Restore This Version
  3. Confirm the action

This creates a new revision with the old values, preserving the history.

Partial Restore

To restore only specific fields:

  1. Note the values from the old revision
  2. Edit the current entry
  3. Update only the fields you want
  4. 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