| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 723 |
| Technical Name |
praetorx_base |
| License | OPL-1 |
| Website | https://praetorx.net |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 723 |
| Technical Name |
praetorx_base |
| License | OPL-1 |
| Website | https://praetorx.net |
Praetorx Base - Foundation Module
v19.0.1.1.0 Odoo 19 OPL-1
Praetorx Base is a technical foundation module providing reusable patterns extracted from production Odoo implementations. Build robust, maintainable applications with proven patterns.
Key Features
🔄 Queue Job System
Background job processing via cron with state management.
- Process large datasets without blocking UI
- Automatic cron processing every minute
- State tracking: pending → processing → done/failed
- Error logging and retry capability
- Batch processing (100 jobs per run)
Model: praetorx.queue.job
✓ Validation Mixin
Structured validation with HTML-formatted summaries.
- Error vs warning classification
- Bootstrap-styled HTML summaries
- Helper methods: is_valid(), assert_valid()
- Batch validation support
- Field-level error tracking
Mixin: praetorx.validation.mixin
📋 Batch Processing Mixin
State machine pattern for parent-child workflows.
- Standard workflow: draft → validated → posted
- Cancellation with reset to draft
- Extensible validation hooks
- Button visibility auto-computed
- Deletion protection for posted documents
Mixin: praetorx.batch.mixin
📱 Split View OWL Component
Reusable master-detail UI pattern.
- Email-style interfaces (list + detail)
- Customizable master/detail widths
- Slot-based content injection
- Responsive layout
- Empty state handling
Component: SplitView
Quick Start
1. Install the module:
# Apps → Update Apps List → Search "Praetorx Base" → Install2. Add to your module dependencies:
{
'name': 'My Module',
'depends': ['praetorx_base'],
# ...
}3. Inherit the patterns you need:
class MyModel(models.Model):
_name = 'my.model'
_inherit = [
'praetorx.validation.mixin',
'praetorx.batch.mixin',
]Use Cases
- Accounting: Invoice/settlement batch processing
- Property Management: Operating cost settlements
- E-commerce: Order processing workflows
- HR: Payroll batch processing
- Manufacturing: Production order validation
Technical Details
All patterns are implemented as abstract models or mixins promoting:
- Code Reuse: Write once, use everywhere
- Consistency: Standard patterns across modules
- Maintainability: Changes propagate automatically
- Testability: Battle-tested in production
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