-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[16][IMP] rma : propagate cancelation #539
[16][IMP] rma : propagate cancelation #539
Conversation
Hi @florian-dacosta, Also the user @DavidFIB is an outdated profile, so you can tag @DavidJForgeFlow instead! |
Thanks for the feedback. I will add some tests about it, and once ok, will remove the WIP mark of the PR. |
1c03e23
to
6ae7556
Compare
6ae7556
to
f92559e
Compare
When canceling a rma order line, it will also cancel the previous (orig) steps. Following steps (dest) can be managed with the propagate cancel option of the stock rules. This commit also avoid canceling a whole picking which is problematic in case of the use of RMA groups
f92559e
to
f05e403
Compare
@DavidJForgeFlow @AaronHForgeFlow If you play the new test without the changes on Let me know what you think. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this makes sense. Cancelling only the stock moves related to the rma line should be enough. I will do a last check before the merge and hopefully merge it.
Hello @AaronHForgeFlow |
Hi @florian-dacosta sorry for the wait. I think this is ok to merge. However, we have a complex project that may be impacted by this change, and the person handling it is currently on vacation. Hopefully next week we can merge it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code review, from my side it makes sense 👍
@florian-dacosta Thank you for the fix and sorry for the wait, I am merging this now. I did additional functional tests. All good. |
Replace #429
With current code, in the case you create a RMA group with 2 rma lines, if you cancel one rma line, the whole picking related to the rma line is canceled, so the second rma line can't be done.
The goal of this PR is to avoid this, and also to manage the propagation of the cancelation on all origin stock moves related to the rma line.
For destination moves, it should be configurable on the stock rules.
Like commented in #429
I don't understand the use case covered with the current code. A example on how to reproduce a process where it is usefull would certainly help me!
I'll set the PR in draft for now, since the goal for now is more to discuss on how can we avoid the problematic of the rma group use while continuing covering the current use case (which I don't get)
@AaronHForgeFlow @DavidFIB