Configuration

To configure this module, you need to:

1. Go to Settings > Technical > Tier Validations > Tier Definition.
2. Create as many tiers as you want for any model having tier validation functionality.

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.

To configure Tier Validation Exceptions, you need to:

1. Go to Settings > Technical > Tier Validations > Tier Validation Exceptions.
2. Create as many tiers validation exceptions as you want for any model having tier validation functionality.
3. Add desired fields to be checked in Fields.
4. Add desired groups that can use this Exception in Groups.
5. You must check Write under Validation, Write after Validation or both.

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.

Known issues / Roadmap

This 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 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:

  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

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