Bring back the classic Edit & Save workflow
Every existing record opens read-only with a persistent mode badge, labeled Edit / Save / Discard buttons, live change tracking and save confirmations — so accidental edits and “did it actually save?” confusion are gone for good.
Since Odoo v16, form views open directly in editable mode and Save/Discard hide behind a small unlabeled icon, while Edit moved into a dropdown menu. A stray keystroke or click on an open record can silently mutate production data, and users often cannot tell whether their change actually committed.
Existing records open read-only with an unmistakable mode badge and a labeled Edit button. Once editing, Save and Discard are explicit, changed fields are listed live, and confirmation dialogs guard every commit — restoring the safe, deliberate workflow teams relied on before v16.
Everything the competition left out
Every capability below is implemented in the module.
Read-only by default
Existing records open read-only, so viewing a record never risks changing it. New records still open ready to fill in, exactly as before.
Explicit Edit / Save / Discard
Labeled buttons replace the buried, unlabeled controls Odoo hid away, so the intent to change a record is always a deliberate click.
Persistent mode badge
A always-visible Readonly / Editing badge in the form header means you never have to guess which state a record is in.
Field-level change tracking
A live “Modified: …” list names every field changed in the current session, so you know exactly what you are about to save.
Confirm before you save
A confirmation dialog stands between a click and a committed change, then acknowledges the save — toggleable if you prefer a faster flow.
Confirm before you discard
A separate confirmation protects in-progress edits from being lost to a stray Discard click, also toggleable per your preference.
Keyboard shortcuts
Alt+E to edit, Alt+S to save, Alt+J to discard — built for operators who spend all day in forms and want their hands on the keyboard.
Per-model configuration
Choose manual or instant mode per model from a simple rules list, so fast-moving models can stay instant while sensitive ones stay protected.
Per-group instant-edit bypass
Add power users to the Instant Edit Mode group and they keep the fast, auto-save workflow while everyone else gets the safer default.
How it works
Open a record
The form opens read-only with a Readonly badge, so browsing records is always safe.
Click Edit
The badge switches to Editing and the Save / Discard buttons appear in its place.
Make your changes
Every modified field is added to a live “Modified: …” list as you type.
Save or Discard
A confirmation dialog guards the commit, then the form returns to its Readonly badge automatically.
See it in action
Six views covering the readonly / edit workflow, the save confirmation, and the settings that control it.
Existing records open read-only with a persistent Readonly badge and a labeled Edit button — no accidental typing risk.
After clicking Edit, the badge switches to Editing and Save / Discard buttons appear, with modified fields listed live.
A confirmation dialog appears before changes are saved, so nothing commits by accident.
Global settings control the default mode, confirmations, badge, change indicators and keyboard shortcuts, with a before/after explanation built in.
Per-model rules let admins choose manual or instant mode for each model individually.
Each per-model rule is a simple record: pick the model and its edit mode.
Frequently asked
Does this affect new, unsaved records?
No. New records still open in edit mode as usual — the read-only default only applies to existing records you open to view.
Can some users skip the confirmation workflow?
Yes. Add a user to the Instant Edit Mode group and their forms behave like stock Odoo (auto-save, no readonly step), while everyone else keeps the safer manual workflow.
Can I apply the manual workflow to only some models?
Yes. The Per-Model Rules list lets you set manual or instant mode per model, so fast-moving models can stay instant while sensitive ones stay protected.
Will I know if my changes were actually saved?
Yes. Saving shows a confirmation dialog and a “Changes saved” notification, and the form automatically returns to its Readonly badge once the save completes.
Get in Touch
Have questions or need customization? Every purchase includes 30 days of free support — we are here to help.
Visit Our Website
www.cerevantix.comExplore our apps, services, and portfolio.
Empowering growth through technology.
Restore the classic readonly Edit / Save / Discard workflow to every Odoo form, with a mode badge, live change tracking and save/discard confirmations built in.
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Lines of code | 457 |
| Technical Name |
cerevantix_show_edit_save_button_on_form_view |
| License | OPL-1 |
| Website | https://cerevantix.com |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module