Italiano
Questo modulo aggiunge la spunta Richiedi fattura nella pagina dell’indirizzo all’interno del flusso di checkout, il suo valore è l’opposto di Usare ricevute nel partner.
Per gli utenti non autenticati, il valore predefinito della casella Richiedi fattura è sempre vuoto.
English
This module adds the Request invoice check in partner’s address form of checkout flow, its value is the opposite of Use receipts in partner.
For unlogged users the default value for Request invoice flag is always empty.
Table of contents
Configuration
Italiano
Il comportamento dipende da come è configurato il partner associato all’utente autenticato, ad esempio:
Se il partner associato all’utente che ha effettuato il login ha la spunta Usare ricevute abilitata, la spunta Richiedi fattura sarà disabilitata;
Se il partner associato all’utente che ha effettuato il login ha la spunta Usare ricevute disabilitata, la spunta Richiedi fattura sarà abilitata;
English
The behavior depends on how the partner associated with the logged in user is configured, for example:
If the partner associated with the logged in user has the Use receipts flag enabled, the check Request invoice will be disabled;
If the partner associated with the logged in user has the Use receipts flag disabled, the check Request invoice will be enabled;
Known issues / Roadmap
Italiano
Per gli utenti non autenticati il valore predefinito della casella Richiedi fattura è sempre vuoto, dovrebbe dipendere dalla casella Usare ricevute nel partner dell’utente pubblico.
English
For unlogged users the default value for Request invoice flag is always empty, it should depend on the Use receipts flag in the partner of the public user.
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
Simone Rubino <simone.rubino@agilebg.com>
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/l10n-italy 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-l10n-it-website-sale-corrispettivi 12.0.1.0.1
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_l10n_it_website_sale_corrispettivi-12.0.1.0.1-py3-none-any.whl | Python 3 | none | any | Details for odoo12_addon_l10n_it_website_sale_corrispettivi-12.0.1.0.1-py3-none-any.whl |
Release files / odoo12_addon_l10n_it_website_sale_corrispettivi-12.0.1.0.1-py3-none-any.whl
| Download URL | odoo12_addon_l10n_it_website_sale_corrispettivi-12.0.1.0.1-py3-none-any.whl |
|---|---|
| Size | 28.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
32df68b1a4b129129020249487150bc13fa780dad7b2e77975c3773cb5d15e54
|
|
BLAKE2b-256 checksum How to use checksums |
2900955ab3d98ee042277af36b4cfbfccd37ee104296f61fd888b59d2abb47a7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/30.4.0 requests-toolbelt/0.8.0 tqdm/4.24.0 CPython/3.5.3
|
Security for odoo12-addon-l10n-it-website-sale-corrispettivi 12.0.1.0.1
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.
