Partner Tier Validation
Adds an approval workflow to Partners. The default rule requires new company Contacts to be approved before they can be used.
The rule can be extended to new non-company contact, but beware that may cause issues with automatically created new contacts, such as the ones generated when processing incoming emails.
If the ‘Is Company’ or ‘Parent’ field changes then the contact is Request for approval.
For this, the new Contact record is kept as “Archived” until it is approved.
Table of contents
Installation
This module depends on base_tier_validation. You can find it at OCA/server-ux
Usage
Before using, check Contact Stages configuration to ensure that the default stage has the “Related State” field set to “To Approve”. For example, having the “Draft” stage the default ensures this.
A validation exception needs to be defined if you want to be able to change the stage after validation and then make the contact available.
A regular user creates a new Contact and sends it for approval:
Create a Contact triggering at least one “Tier Definition”. The Contact will be in Draft state and marked as Archived until approved.
Click on Request Validation button.
In the Reviews section, at the bottom of the form, inspect the pending reviews and their status.
The approver reviews Contacts to approve:
Navigate to the Contacts app, and select the filter “Needs my Approval”
Open the Contact form to approve. It will display a “This Records needs to be validated” banner, with “Validate” and “Reject” options.
The approver can change the stage to “Active”. This will make the record available to be used.
The Approve/Reject actions do not automatically change the State. This could be a future improvement.
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
-
Antonio Yamuta <ayamuta@opensourceintegrators.com>
Daniel Reis <dreis@opensourceintegrators.com>
Urvisha Desai <udesai@opensourceintegrators.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.
Current maintainer:
This module is part of the OCA/tier-validation 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 odoo-addon-partner-tier-validation 19.0.1.0.0.3
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 | Reset |
|---|---|---|---|---|
| odoo_addon_partner_tier_validation-19.0.1.0.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Release files / odoo_addon_partner_tier_validation-19.0.1.0.0.3-py3-none-any.whl
| Download URL | odoo_addon_partner_tier_validation-19.0.1.0.0.3-py3-none-any.whl |
|---|---|
| Size | 32.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c3fb27b37d18cf609f7ef6a7100d34e673d4004496666c36e6067f13bf7e5f0e
|
|
BLAKE2b-256 checksum How to use checksums |
162ae554ba9876c7ae4d80a25b263bc422693808c317dec564db65c3c2efc209
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|
