EspoCRM’s upcoming version 9.1 introduces a powerful new feature: Saved-state conditions for making fields read-only. This enhancement allows administrators to define dynamic logic based on the saved state of a record, improving data integrity and workflow automation.
How Saved-State Conditions Work
The saved-state conditions feature operates differently from standard dynamic logic:
- Conditions are checked against the saved state of a record, not the current form values
- Logic isn’t applied while editing a record before saving
- Conditions don’t apply when creating new records
- Works consistently across frontend, backend, and mass-update operations
Practical Use Case
A common scenario would be making a Resolution field read-only when Status equals Completed:
- Once Status is saved as Completed, Resolution becomes read-only
- Changing Status on the form won’t immediately affect Resolution field
- Only after saving the Status change will Resolution become editable again
Benefits for Business Processes
This feature helps organizations:
- Enforce data consistency in critical workflows
- Prevent accidental changes to completed records
- Maintain audit trails without complex custom development
For businesses looking to implement these advanced workflow controls in EspoCRM, our team offers expert implementation services. Contact us to discuss how we can help optimize your CRM setup.
