-
-
Notifications
You must be signed in to change notification settings - Fork 532
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
9e1bdbd
commit dee43e0
Showing
4 changed files
with
79 additions
and
83 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -7,7 +7,7 @@ Base Tier Validation | |
!! This file is generated by oca-gen-addon-readme !! | ||
!! changes will be overwritten. !! | ||
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | ||
!! source digest: sha256:e0956b4261f41c7dbafeb78d2e0502dfaa3c83de1731a01709ebf9e1dbd142a1 | ||
!! source digest: sha256:9d45fb0cb0dd64489508d2963bbd948c59b466f16618469b6e86e3d606511aeb | ||
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | ||
.. |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,42 +90,40 @@ 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 | ||
====================== | ||
|
||
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,24 +250,24 @@ Authors | |
Contributors | ||
------------ | ||
|
||
- Lois Rilo <[email protected]> | ||
- Naglis Jonaitis <[email protected]> | ||
- Adrià Gil Sorribes <[email protected]> | ||
- Pimolnat Suntian <[email protected]> | ||
- Pedro Gonzalez <[email protected]> | ||
- Kitti U. <[email protected]> | ||
- Saran Lim. <[email protected]> | ||
- Carlos Lopez <[email protected]> | ||
- Javier Colmeiro <[email protected]> | ||
- bosd | ||
- Evan Soh <[email protected]> | ||
- Manuel Regidor <[email protected]> | ||
- Eduardo de Miguel <[email protected]> | ||
- `XCG Consulting <https://xcg-consulting.fr>`__: | ||
|
||
- Houzéfa Abbasbhay | ||
|
||
- Stefan Rijnhart <[email protected]> | ||
- Lois Rilo <[email protected]> | ||
- Naglis Jonaitis <[email protected]> | ||
- Adrià Gil Sorribes <[email protected]> | ||
- Pimolnat Suntian <[email protected]> | ||
- Pedro Gonzalez <[email protected]> | ||
- Kitti U. <[email protected]> | ||
- Saran Lim. <[email protected]> | ||
- Carlos Lopez <[email protected]> | ||
- Javier Colmeiro <[email protected]> | ||
- bosd | ||
- Evan Soh <[email protected]> | ||
- Manuel Regidor <[email protected]> | ||
- Eduardo de Miguel <[email protected]> | ||
- `XCG Consulting <https://xcg-consulting.fr>`__: | ||
|
||
- Houzéfa Abbasbhay | ||
|
||
- Stefan Rijnhart <[email protected]> | ||
|
||
Maintainers | ||
----------- | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters