Configuring revision fields
The Revision Field in Unifize enables version control within the checklist of a process record. It allows users to create and manage multiple versions of data while maintaining full traceability. Whether you're managing documents, specifications, or any process that evolves over time, revision fields help enforce structure, accountability, and audit readiness.
What is a Revision Field?
A Revision Field lets users:
Create a new revision (version) of a document or linked field.
Retain historical versions for traceability.
Mark a revision as the “current” version.
Carry forward selected data fields to the next revision.
Trigger automation based on revision events.
When to Use It
Use revision fields in processes where:
Data or documents change over time
You need to track and audit each version
Only one version should be considered "current"
Each version may go through independent review or approval
Common use cases:
Document Control (SOPs, specs, drawings)
Product Revision History
Test Protocols and Validation Records
CAPAs or Non-Conformances with follow-up iterations
How to Add a Revision Field
Open the process in Process Builder
Add a new field in a checklist section
Set the Field Type to Revision
Name the field (e.g., “Version Tracker”)
Save the process
Note: Only one Revision Field can be used per process.
Configuring Revision Permissions
Click the gear icon on the Revision Field to define:
Who Can Create a New Revision
All participants
Record owner
Specific users or roles
Users pulled from a user field
Who Can Mark a Revision as Current
Anyone
Only owner or specific roles
When in a specific status (e.g., “Approved”)
Additional options:
Make comments mandatory before creating a new revision
Auto-navigate to the newly created revision
Display visual indicators for current revision vs archived ones
Default Fields Carried Forward
You can define which checklist fields should carry over when a revision is created. This helps reduce data entry and preserve context.
To configure:
Select checklist fields under “Fields to copy forward”
Choose whether field values should remain editable in the new revision
Automations on Revision Changes
You can set up automations for key revision events:
When a new revision is created
When a revision is marked current
When a previous revision is archived
Use these triggers to:
Add/remove participants
Send notifications
Update record-level fields
Set deadlines or reminders
Best Practices
Use revision fields where traceability is critical
Pair with approval fields to control which revision becomes current
Name revisions clearly (e.g., /1C, /2C, /3C)
Use filters or reports to track current vs archived revisions
Avoid creating multiple revision fields in a single process
The Revision Field brings structured version control into any Unifize workflow. With the ability to create, track, and govern changes through revisions, teams can ensure compliance, reduce duplication, and maintain a clean audit trail across all records.
For advanced configuration, see:
Last updated