| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 581 |
| Technical Name |
cm_sa_reset_auditor |
| License | OPL-1 |
| Website | https://cm.sa |
| Versions | 17.0 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 581 |
| Technical Name |
cm_sa_reset_auditor |
| License | OPL-1 |
| Website | https://cm.sa |
| Versions | 17.0 18.0 19.0 |
Reset-to-Draft Auditor
Make every reset-to-draft carry a reason, and put it all in a report.
Sale orders and invoices get reset to draft and quietly edited, and controllers cannot easily see who did it or why. Odoo logs the state change in chatter but never asks for a reason, never restricts the button, and produces no report, leaving a hole exactly where auditors look hardest. This module wraps reset-to-draft on any model: a required reason at click time, an optional group restriction, and a full audit log with a pivot dashboard.
Reset-to-Draft Auditor
Require a reason, restrict to a group, and log every reset-to-draft on sale orders, invoices, POs, pickings, or any model.
What it does
Controllers know that sale orders and invoices get reset to draft and quietly edited, but cannot easily find out who, when, or why. Odoo logs the state change in chatter but does not require a reason, does not restrict the button to privileged users, and does not produce a report.
Core has no gate on reset-to-draft, so the audit trail has a hole exactly where auditors look hardest.
What this module adds:
- Wrap the reset-to-draft method on any model at registry load.
- Per rule, configure the model (
sale.order,account.move,purchase.order,stock.picking, a custom model). - Configure the method being wrapped (default
action_draft). - Require a reason: click Reset, the wizard asks why, the write only happens on submit.
- Optional required group: only members can reset.
- Optional domain so the rule only applies to a subset.
- Every reset writes a
cm_sa.reset_audit.logrow with user, reason, timestamp, and a link back to the record. - Dashboard pivots by user, model, week, and rule.
Who benefits
Controllers, internal auditors, and compliance officers at mid-market and enterprise companies subject to document-audit reviews.
How it works
_register_hook wrapper at registry load, TransientModel wizard, and an idempotent audit log. No core-model inheritance, no JS. TransactionCase tested on Odoo 17, 18, and 19. Safe to install, safe to uninstall.
What the module looks like
Real screenshots from a live Odoo 19 install. Every view is standard Odoo chrome, no bespoke widgets to learn.
Common questions
Does it inherit or patch core Odoo models?
_register_hook to wrap the target method at registry load, and the wrapper unwinds cleanly at uninstall. No schema changes to core tables, no monkey-patches, no Studio surgery.Does it work on Odoo Community, or only Enterprise?
Can I uninstall it cleanly if it does not fit?
What support do I get after buying?
Can Cube Master customise it for my company?
Beyond this module, Cube Master also builds:
We are a full technology house. The Odoo utility you are reading about is one part of what we ship. If your back office, website, or app team needs more, we have the team for it.
More from the Cube Master catalogue
We ship 33 single-feature utilities at the same price point. If this one solved a pain for you, the others probably will too.
About Cube Master
We blend mastery with creativity - نمزج الإتقان بالإبداع
Cube Master is a Saudi technology house based in Al-Mubarraz. We design, build, and run business systems for customers across the Gulf and beyond: end-to-end Odoo ERP rollouts, custom AI workflows, corporate websites, and mobile apps. Strategic technology partners with Microsoft, AWS, Odoo, and Umbraco.
The Odoo utility you are reading about is one small piece of what we ship. If you need any of the above for your company, talk to us.
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