Skip to main content

Support a tier validation process for Contacts

Project description

Beta License: AGPL-3 OCA/partner-contact Translate me on Weblate Try me on Runboat

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 regular user creates a new Contact and sends it for approval:

  1. Create a Contact triggering at least one “Tier Definition”. The Contact will be in Draft state and marked as Archived until approved.

  2. Click on Request Validation button.

  3. In the Reviews section, at the bottom of the form, inspect the pending reviews and their status.

The approver reviews Contacts to approve:

  1. Navigate to the Contacts app, and select the filter “Needs my Approval”

  2. Open the Contact form to approve. It will display a “This Records needs to be validated” banner, with “Validate” and “Reject” options.

  3. The approver can change the state to “Active”. This will automatically unarchive the record and make it 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

Authors

  • Open Source Integrators

Contributors

Maintainers

This module is maintained by the OCA.

Odoo Community Association

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:

dreispt

This module is part of the OCA/partner-contact project on GitHub.

You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distributions

No source distribution files available for this release.See tutorial on generating distribution archives.

Built Distribution

File details

Details for the file odoo_addon_partner_tier_validation-16.0.1.0.1-py3-none-any.whl.

File metadata

File hashes

Hashes for odoo_addon_partner_tier_validation-16.0.1.0.1-py3-none-any.whl
Algorithm Hash digest
SHA256 bf0056d9863b1a25369c0b11744e5647b3cd4df03bba188055e4acc0ae09c904
MD5 a52e85132f4582504f1a90b9d7876ced
BLAKE2b-256 11ace600d4fcf1b5e75d293ed3e6bc449b8383c6b02a9f595006233e94252e12

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page