Package: odoo-addon-base-tier-validation
Validating some operations is a common need across different areas in a
company and sometimes it also involves several people and stages in the
process. With this module you will be able to define your custom
validation workflows for any Odoo document.This module does not provide a functionality by itself but an abstract
model to implement a validation process based on tiers on other models
(e.g. purchase orders, sales orders, budgets, expenses…).Note:To be able to use this module in a new model you will need
some development.Seepurchase_tier_validationas an example of implementation.Table of contentsConfigurationKnown issues / RoadmapChangelog17.0.1.0.0 (2024-01-10)14.0.1.0.0 (2020-11-19)13.0.1.2.2 (2020-08-30)12.0.3.3.1 (2019-12-02)12.0.3.3.0 (2019-11-27)12.0.3.2.1 (2019-11-26)12.0.3.2.0 (2019-11-25)12.0.3.1.0 (2019-07-08)12.0.3.0.0 (2019-12-02)12.0.2.1.0 (2019-05-29)12.0.2.0.0 (2019-05-28)12.0.1.0.0 (2019-02-18)11.0.1.0.0 (2018-05-09)10.0.1.0.0 (2018-03-26)9.0.1.0.0 (2017-12-02)Bug TrackerCreditsAuthorsContributorsMaintainersConfigurationTo configure this module, you need to:Go toSettings > Technical > Tier Validations > Tier Definition.Create as many tiers as you want for any model having tier validation
functionality.Note:If checkNotify Reviewers on Creation, all possible reviewers will
be notified by email when this definition is triggered.If checkNotify reviewers on reaching pendingif you want to send a
notification when pending status is reached. This is usefull in a
approve by sequence scenario to only notify reviewers when it is
their turn in the sequence.If checkComment, reviewers can comment after click Validate or
Reject.If checkApprove by sequence, reviewers is forced to review by
specified sequence.Known issues / RoadmapThis is the list of known issues for this module. Any proposal for
improvement will be very valuable.Issue:When using approve_sequence option in any tier.definition there can
be inconsistencies in the systray notifications.Description:Field can_review in tier.review is used to filter out, in the systray
notifications, the reviews a user can approve. This can_review field
is updatedin the databasein method review_user_count, this can
make it very inconsistent for databases with a lot of users and
recurring updates that can change the expected behavior.Migration to 15.0:The parameter _tier_validation_manual_config will become False, on
14.0, the default value is True, as the change is applied after the
migration. In order to use the new behavior we need to modify the
value on our expected model.Changelog17.0.1.0.0 (2024-01-10)Migrated to Odoo 17. Merged module with tier_validation_waiting. To
support sending messages in a validation sequence when it is their turn
to validate.14.0.1.0.0 (2020-11-19)Migrated to Odoo 14.13.0.1.2.2 (2020-08-30)Fixes:When using approve_sequence option in any tier.definition there can
be inconsistencies in the systray notificationsWhen using approve_sequence, still not approve only the needed
sequence, but also other sequence for the same approver12.0.3.3.1 (2019-12-02)Fixes:Show comment on Reviews Table.Edit notification with approve_sequence.12.0.3.3.0 (2019-11-27)New features:Add comment on Reviews Table.Approve by sequence.12.0.3.2.1 (2019-11-26)Fixes:Remove message_subscribe_users12.0.3.2.0 (2019-11-25)New features:Notify reviewers12.0.3.1.0 (2019-07-08)Fixes:Singleton error12.0.3.0.0 (2019-12-02)Fixes:Edit Reviews Table12.0.2.1.0 (2019-05-29)Fixes:Edit drop-down style width and position12.0.2.0.0 (2019-05-28)New features:Pass parameters as functions.Add Systray.12.0.1.0.0 (2019-02-18)Migrated to Odoo 12.11.0.1.0.0 (2018-05-09)Migrated to Odoo 11.10.0.1.0.0 (2018-03-26)Migrated to Odoo 10.9.0.1.0.0 (2017-12-02)First version.Bug TrackerBugs are tracked onGitHub 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 welcomedfeedback.Do not contact contributors directly about support or help with technical issues.CreditsAuthorsbrain-tec AGForgeFlowContributorsLois Rilo <lois.rilo@forgeflow.com>Naglis Jonaitis <naglis@versada.eu>Adrià Gil Sorribes <adria.gil@forgeflow.com>Pimolnat Suntian <pimolnats@ecosoft.co.th>Pedro Gonzalez <pedro.gonzalez@pesol.es>Kitti U. <kittiu@ecosoft.co.th>Saran Lim. <saranl@ecosoft.co.th>Carlos Lopez <celm1990@gmail.com>Javier Colmeiro <javier.colmeiro@braintec.com>bosdEvan Soh <evan.soh@omnisoftsolution.com>MaintainersThis 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.Currentmaintainer:This module is part of theOCA/server-uxproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.