ITA - Gestione cespiti - Importazione storico in background
Italiano
Questo modulo permette l'uso delle code per l'importazione dello storico dei cespiti.
English
This module adds job queue support to import assets history.
auto_awesome What this module does
AI-generated from the code · Odoo 14.0Lets you import the historical data of Italian fixed assets in the background, so the import runs as a queued job and you get a notification when it finishes or fails.
This module changes how the asset history import wizard works: instead of running the import immediately, the import is sent to a background job queue.
- When you confirm the import in the wizard, the file is not processed right away. A job is created and you immediately see a notification saying "Job queued".
- The actual import then runs in the background through the job queue. When it finishes, you receive a notification: a success message if assets were imported, a warning if nothing could be imported, or an error message if something went wrong.
- The background job is configured with a retry pattern, so if it fails it is automatically retried after increasing delays (about 90, 180, 270 and 360 seconds).
- A dedicated job channel named
asset_history_importis created to organise these jobs.
The module extends the existing asset history import wizard (wizard.asset.history.import) and relies on the job queue and web notification features. It touches the Italian fixed asset localization area and the job queue configuration.
Models and fields (1)
- wizard.asset.history.import · extends an existing model
Text generated by AI (DeepSeek) from reading the Odoo 14.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 14.0
Confirmed on 2026-11-03 in branch 14.0 of OCA/l10n-italy.
terminal Installation and usage
No verified informationInstallation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.