Account Banking NL ClieOp
account_banking_nl_clieop · OCA/bank-payment
Health
35/100
poor
-
Security25/25No findings
-
Activity0/25Last human commit 123 months ago
-
Required by5/250 modules depend on it
-
Maturity5/25In 1 Odoo series since 7.0
Heuristic over the facts below, not an audit · How it's computed
Required by
0
Modules depending on it
External deps
0 pip · 0 bin
Python packages / system binaries
License
AGPL-3
No conflicts with its dependencies
Folder size
0.08 MB
Module directory on disk
Code analysis
10 migration notes
2 models
3 views
0 HTTP endpoints
Migration considerations
- Migrating to 11.0: the workflow engine (`trg_validate`) was removed: rewrite as state-field transitions. migration-workflow-call · source
- Migrating to 19.0: only `__manifest__.py` is recognized: a module with `__openerp__.py` is not detected at all. migration-openerp-manifest · source
banking_export_clieop_wizard— Class 'banking_export_clieop_wizard' still inherits from the old-style `orm.TransientModel` API: rewrite it against `models.Model`/`models.TransientModel`/`models.AbstractModel` - the old `osv`/`orm` API was removed entirely in modern Odoo. migration-old-api-base · sourcebanking_export_clieop_wizard— Class 'banking_export_clieop_wizard' declares `_columns` as a plain dict: old-style field/default declarations, replace with `fields.X(...)` class attributes and `default=`. migration-old-style-fields · sourcebanking_export_clieop_wizard_view— Migrating to 17.0: `attrs=`/`states=` are rejected in views: convert them to Python expressions in `invisible`/`readonly`/`required`, keeping the original AND/OR logic. migration-view-attrs-states · sourceclieop_export— Class 'clieop_export' still inherits from the old-style `orm.Model` API: rewrite it against `models.Model`/`models.TransientModel`/`models.AbstractModel` - the old `osv`/`orm` API was removed entirely in modern Odoo. migration-old-api-base · sourceclieop_export— Class 'clieop_export' declares `_columns` as a plain dict: old-style field/default declarations, replace with `fields.X(...)` class attributes and `default=`. (2 occurrences in this file) migration-old-style-fields · sourceview_banking_export_clieop_tree— Migrating to 18.0: the `tree` view type was renamed to `list` (`<list>` roots, `view_mode`). migration-view-tree-tag · source- Migrating to 10.0: the `openerp` namespace was renamed to `odoo`; only a deprecated `openerp.addons` alias remained. (`openerp.osv`) (2 occurrences in this file) migration-openerp-import · source
- Migrating to 10.0: the `openerp` namespace was renamed to `odoo`; only a deprecated `openerp.addons` alias remained. (`openerp.osv`) (6 occurrences in this file) migration-openerp-import · source
Migration review checklist, not a compatibility verdict. "Migrating to X.0" applies once you upgrade to that version; "Since X.0" means this version already ignores or rejects that code. Methodology
Description
Module to export payment orders in ClieOp format.
ClieOp format is used by Dutch banks to batch national bank transfers.
This module uses the account_banking logic.
Dependencies
Code analysis
Extracted from the source by best-effort static analysis (no code is executed); details may be incomplete.
Views touched 3
| XML ID | Name | Model | Type | Status |
|---|---|---|---|---|
banking_export_clieop_wizard_view |
banking.export.clieop.wizard.view | banking.export.clieop.wizard | form | New |
view_banking_export_clieop_form |
account.banking.export.clieop.form | banking.export.clieop | form | New |
view_banking_export_clieop_tree |
account.banking.export.clieop.tree | banking.export.clieop | tree | New |
HTTP endpoints 0
No HTTP endpoints found for this module.
Models touched 2
New fields (0)
No new fields.
Public methods (1)-
get_daynr(self, cr, uid, context=None)Return highest day number
New fields (0)
No new fields.
Public methods (5)-
cancel_clieop(self, cr, uid, ids, context)Cancel the ClieOp: just drop the file -
check_orders(self, cr, uid, vals, context)Check payment type for all orders. Combine orders into one. All parameters harvested by the wizard will apply to all orders. This will in effect create one super batch for ClieOp, instead of creating individual parameterized batches. As only large companies are likely to need the individual settings per batch, this will do for now. Also mind that rates for batches are way higher than those for transactions. It pays to limit the number of batches. -
create(self, cr, uid, vals, context=None)Retrieve a sane set of default values based on the payment orders from the context. -
create_clieop(self, cr, uid, ids, context)Wizard to actually create the ClieOp3 file -
save_clieop(self, cr, uid, ids, context)Save the ClieOp: mark all payments in the file as 'sent', if not a test