Report Async
The new menu “Report Center” is the central place to host your reports in one place. From here, there are 2 ways to launch the report,
Run Now - run report immediately as per normal.
Run Background - put the report execution to queue job.
By using the queue job, option 2 is great for long running report. The report file will be saved for later use, with the option to send report by email as soon as it is ready.
Notes:
Only user with Technical Feature rights can manage the report.
Every internal user will have right to execute the report allowed for his/her groups.
The files created are owned and viewable only by the person who run the report.
Job queue manager can also see all jobs for each reports.
Table of contents
Usage
Menu: Dashboard > Report Center
As Technical Feature users, you can manage reports for Report Center.
Report: choose the report (a window action). Although the option show all window actions it only make sense for window actions that launch reports.
Allow Async: check this, if you want the report to run in background too, suitable for report that return file as result, i.e., pdf/xlsx/csv/txt.
Email Notification: if checked, once the background process is completed, email with link to download report will be sent.
Groups: select user groups allowed to use this report. If left blank, all user can use.
As normal user, you can run your reports from Report Center
Run Now button: to run report immediately as per normal.
Run Background button: to run report asynchronously. Fall back to run now, if not report that produce file.
Job Status: show status of the latest run job. If job fail, exception error will also shown
Files: show all files being produced by the job as run by the user.
Jobs: show all jobs triggered by this report as run by the user. Only job queue manager have access to this button.
Bug Tracker
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
Kitti U. <kittiu@ecosoft.co.th>
Maintainers
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
Current maintainer:
This module is part of the OCA/reporting-engine project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
1 maintainer
Metadata
1 maintainer
Release files for odoo12-addon-report-async 12.0.2.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| odoo12_addon_report_async-12.0.2.0.0-py3-none-any.whl | Python 3 | none | any | Details for odoo12_addon_report_async-12.0.2.0.0-py3-none-any.whl |
Release files / odoo12_addon_report_async-12.0.2.0.0-py3-none-any.whl
| Download URL | odoo12_addon_report_async-12.0.2.0.0-py3-none-any.whl |
|---|---|
| Size | 41.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4c4f94f3cbf0cf4232f893110aea2264ea2a36f78e2ee4af8a4ce9ea9a2d9625
|
|
BLAKE2b-256 checksum How to use checksums |
e568354ee08eec079a258d99a6f5733abd1a6cdd1a6732a538cf16b38c7a9be1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.3
|
Security for odoo12-addon-report-async 12.0.2.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
