Voxel sale order
This module allows you to import sales orders from Voxel. Imports are queued in jobs running in the background.
Table of contents
Configuration
To configure this module you have to belong to the access group ‘Voxel manager’ under ‘Technical Settings’, then:
Go to Settings > Users & Companies > Companies, open the companies you want to enable Voxel communication and set ‘Enable Voxel’ field to True.
In the login list, add the corresponding login for connecting with Voxel to import sales orders. The final URL from where sales order will be imported is ‘<Login URL>/Outbox’.
Save the form and edit it again, find ‘Sale Order login’ field and select the login to be used in the imports.
If you have the right access, go to Settings > Technical > Automation > Scheduled Actions, find the record named ‘Edi Voxel: Get voxel sale order’ and Adjust the data corresponding to that scheduled action, such as the frequency with which that action will be executed.
Note:
This module enqueue the imports in jobs in the background. To do that it uses queue_job module, so a configuration is required according to that. The jobs for impots are queued in the channel root.voxel_import.
Usage
To use this module, you don’t need to do anything. Automatically every so often a ‘scheduled action’ will be executed that will try to import from Voxel the sales orders that have not been imported previously.
Imports will be performed for the companies that have the ‘Voxel’ field checked (See configuration section).
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 smashing it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
-
Ernesto Tejeda
Pedro M. Baeza
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.
This module is part of the OCA/edi 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 odoo13-addon-edi-voxel-sale-order-import 13.0.1.0.7
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 |
|---|---|---|---|---|
| odoo13_addon_edi_voxel_sale_order_import-13.0.1.0.7-py3-none-any.whl | Python 3 | none | any | Details for odoo13_addon_edi_voxel_sale_order_import-13.0.1.0.7-py3-none-any.whl |
Release files / odoo13_addon_edi_voxel_sale_order_import-13.0.1.0.7-py3-none-any.whl
| Download URL | odoo13_addon_edi_voxel_sale_order_import-13.0.1.0.7-py3-none-any.whl |
|---|---|
| Size | 37.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9f70e18ddc8eb60d06e69f642661cca8bd0c7995b43c62bdab7569878de39085
|
|
BLAKE2b-256 checksum How to use checksums |
365229faae66a0ec3e650951129823e84b87755f0b61fc739493b6a3d9477798
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.5
|
Security for odoo13-addon-edi-voxel-sale-order-import 13.0.1.0.7
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.
