diff --git a/README.md b/README.md
index 80c8db51eb..4c71ef4347 100644
--- a/README.md
+++ b/README.md
@@ -22,6 +22,7 @@ Available addons
addon | version | maintainers | summary
--- | --- | --- | ---
[base_technical_features](base_technical_features/) | 18.0.1.0.2 | | Access to technical features without activating debug mode
+[base_tier_validation](base_tier_validation/) | 18.0.1.0.0 | [![LoisRForgeFlow](https://github.com/LoisRForgeFlow.png?size=30px)](https://github.com/LoisRForgeFlow) | Implement a validation process based on tiers.
[date_range](date_range/) | 18.0.1.0.0 | [![lmignon](https://github.com/lmignon.png?size=30px)](https://github.com/lmignon) | Manage all kind of date range
[developer_menu](developer_menu/) | 18.0.1.0.0 | [![bealdav](https://github.com/bealdav.png?size=30px)](https://github.com/bealdav) | Menu Shortcut for developer usage
[sequence_check_digit](sequence_check_digit/) | 18.0.1.0.0 | | Adds a check digit on sequences
diff --git a/base_tier_validation/README.rst b/base_tier_validation/README.rst
index 4423652040..79dee6594c 100644
--- a/base_tier_validation/README.rst
+++ b/base_tier_validation/README.rst
@@ -7,7 +7,7 @@ Base Tier Validation
!! This file is generated by oca-gen-addon-readme !!
!! changes will be overwritten. !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
- !! source digest: sha256:a314a0bd0fe0c5f0639ac21d2cf5f66de9d1031487dc4a9bb3bc8692c74457dd
+ !! source digest: sha256:7b3ca7f03e3d92d3cdaeb8de45ef9b88d126b246ba08f2f16d0b17f0121d1c11
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
.. |badge1| image:: https://img.shields.io/badge/maturity-Mature-brightgreen.png
@@ -66,16 +66,16 @@ To configure this module, you need to:
**Note:**
-- If check *Notify Reviewers on Creation*, all possible reviewers will
- be notified by email when this definition is triggered.
-- If check *Notify reviewers on reaching pending* if 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 check *Comment*, reviewers can comment after click Validate or
- Reject.
-- If check *Approve by sequence*, reviewers is forced to review by
- specified sequence.
+- If check *Notify Reviewers on Creation*, all possible reviewers will
+ be notified by email when this definition is triggered.
+- If check *Notify reviewers on reaching pending* if 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 check *Comment*, reviewers can comment after click Validate or
+ Reject.
+- If check *Approve by sequence*, reviewers is forced to review by
+ specified sequence.
To configure Tier Validation Exceptions, you need to:
@@ -90,16 +90,14 @@ To configure Tier Validation Exceptions, you need to:
**Note:**
-- If you don't create any exception, the Validated record will be
- readonly and cannot be modified.
-- If check *Write under Validation*, records will be able to be
- modified only in the defined fields when the Validation process is
- ongoing.
-- If check *Write after Validation*, records will be able to be
- modified only in the defined fields when the Validation process is
- finished.
-- If check *Write after Validation* and *Write under Validation*,
- records will be able to be modified defined fields always.
+- If you don't create any exception, the Validated record will be
+ readonly and cannot be modified.
+- If check *Write under Validation*, records will be able to be modified
+ only in the defined fields when the Validation process is ongoing.
+- If check *Write after Validation*, records will be able to be modified
+ only in the defined fields when the Validation process is finished.
+- If check *Write after Validation* and *Write under Validation*,
+ records will be able to be modified defined fields always.
Known issues / Roadmap
======================
@@ -107,25 +105,25 @@ Known issues / Roadmap
This is the list of known issues for this module. Any proposal for
improvement will be very valuable.
-- **Issue:**
+- **Issue:**
- When using approve_sequence option in any tier.definition there can
- be inconsistencies in the systray notifications.
+ When using approve_sequence option in any tier.definition there can be
+ inconsistencies in the systray notifications.
- **Description:**
+ **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 updated **in the database** in 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.
+ 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 updated **in the database** in 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:**
+- **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.
+ 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.
Changelog
=========
@@ -147,69 +145,69 @@ Migrated to Odoo 14.
Fixes:
-- When using approve_sequence option in any tier.definition there can
- be inconsistencies in the systray notifications
-- When using approve_sequence, still not approve only the needed
- sequence, but also other sequence for the same approver
+- When using approve_sequence option in any tier.definition there can be
+ inconsistencies in the systray notifications
+- When using approve_sequence, still not approve only the needed
+ sequence, but also other sequence for the same approver
12.0.3.3.1 (2019-12-02)
-----------------------
Fixes:
-- Show comment on Reviews Table.
-- Edit notification with approve_sequence.
+- 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.
+- Add comment on Reviews Table.
+- Approve by sequence.
12.0.3.2.1 (2019-11-26)
-----------------------
Fixes:
-- Remove message_subscribe_users
+- Remove message_subscribe_users
12.0.3.2.0 (2019-11-25)
-----------------------
New features:
-- Notify reviewers
+- Notify reviewers
12.0.3.1.0 (2019-07-08)
-----------------------
Fixes:
-- Singleton error
+- Singleton error
12.0.3.0.0 (2019-12-02)
-----------------------
Fixes:
-- Edit Reviews Table
+- Edit Reviews Table
12.0.2.1.0 (2019-05-29)
-----------------------
Fixes:
-- Edit drop-down style width and position
+- Edit drop-down style width and position
12.0.2.0.0 (2019-05-28)
-----------------------
New features:
-- Pass parameters as functions.
-- Add Systray.
+- Pass parameters as functions.
+- Add Systray.
12.0.1.0.0 (2019-02-18)
-----------------------
@@ -252,26 +250,26 @@ Authors
Contributors
------------
-- Lois Rilo Validating some operations is a common need across different areas in a
@@ -434,8 +434,8 @@ Base Tier Validation
!! This file is generated by oca-gen-addon-readme !!
!! changes will be overwritten. !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
-!! source digest: sha256:a314a0bd0fe0c5f0639ac21d2cf5f66de9d1031487dc4a9bb3bc8692c74457dd
+!! source digest: sha256:7b3ca7f03e3d92d3cdaeb8de45ef9b88d126b246ba08f2f16d0b17f0121d1c11
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! -->
Configuration
be notified by email when this definition is triggered.
Configuration
@@ -472,8 +470,8 @@ Known issues / Roadmap
improvement will be very valuable.
Issue:
-When using approve_sequence option in any tier.definition there can -be inconsistencies in the systray notifications.
+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 @@ -505,8 +503,8 @@
Fixes: