Update tier_validation.py #870
Open
Conversation
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
When adding a validation in a model that in its confirmation process makes an update to a field other than the _state_field, it was left in a loop that needs a validation, when the validation was already applied previously, that is, there is no validation only when This is the field defined in the _state_field, this was tested in a custom module that was added for the validations prior to carrying out an inventory write-off with the stock.scrap model. Additionally, it is detected that the sequences are skipped every time you click on the confirm button and it has not yet been approved, which is not corrected in this push.
|
Hi @LoisRForgeFlow, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When adding a validation in a model that in its confirmation process makes an update to a field other than the _state_field, it was left in a loop that needs a validation, when the validation was already applied previously, that is, there is no validation only when This is the field defined in the _state_field, this was tested in a custom module that was added for the validations prior to carrying out an inventory write-off with the stock.scrap model. Additionally, it is detected that the sequences are skipped every time you click on the confirm button and it has not yet been approved, which is not corrected in this push.