| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 286 |
| Technical Name |
cm_sa_so_confirm_guard |
| 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 | 286 |
| Technical Name |
cm_sa_so_confirm_guard |
| License | OPL-1 |
| Website | https://cm.sa |
| Versions | 17.0 18.0 19.0 |
Confirm-Time Field Guard
Require a field only at the confirm button, not on every draft.
Some fields only matter at confirm time: a customer PO number on a sale order, an internal reference on a vendor bill. Marking them required=True is too aggressive and blocks drafts, imports, and quotations, and Studio onchange code breaks on the next upgrade. Confirm-Time Field Guard lets sales ops and accounting teams require any set of fields at action_confirm, action_post, or button_validate, declaratively, with no code.
Confirm-Time Field Guard
Make any field conditionally required at the confirm, post, or validate button, with no Studio and no inheritance.
What it does
Some fields only matter at confirm time: a customer PO number on a sale order, an internal reference on a vendor bill, a destination location on a stock picking. Marking them required=True on the model is too aggressive, it blocks drafts, imports, and quotations.
Odoo core offers no conditional-required primitive, and Studio's approach requires writing onchange code per model, which breaks on the next upgrade.
What this module adds:
- Per model: declare which action method to guard (
action_confirm,action_post,button_validate, or any custom button). - Declare the fields that must be filled at that action.
- Optional domain so the rule only applies to a subset (e.g. orders above a threshold).
- Custom error message per rule.
- Multiple rules on the same method grouped into a single wrapper that runs them in order.
- No Studio required, rules are pure data you can ship between databases.
Who benefits
Sales ops, accounting teams, warehouse managers, and operations leads at SMB and mid-market companies who need conditional field discipline at key workflow transitions.
How it works
_register_hook wraps the configured methods on the model class itself at registry load. No core-model inheritance, no monkey-patching of imported modules. 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