-
-
Notifications
You must be signed in to change notification settings - Fork 95
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
Add modules stock_packaging_usability and stock_packaging_usability_ul #3
Add modules stock_packaging_usability and stock_packaging_usability_ul #3
Conversation
Hi, Alexis, thanks for this contribution. Let me tell you about some remarks:
|
@pedrobaeza I decided to have 2 separated modules (even if it required more work for me) because the first module is designed for those who don't use the object product.ul and just want the same features as v7 ; the second module is for those who also want to use the object product.ul. I don't care about the module name. If all reviewers agree with your proposal for a new module name, i'll change it. |
OK, I understand that it's not the same. The only flaw I see then is to know what is "the current pack". Can you add a readonly field in the screen to show this data? About ul, I would insist to put it on one module, because it's only a data that can be ignored if you don't work with it. Even I think you can control its visibility with the option of "Track logistic units" on Configuration. |
@pedrobaeza I am surprised by your insistance on merging the 2 modules. Of course, we could use a group to know if we display the pop-up to select product.ul or not. But I made the effort to put this in 2 different modules because I thought that some companies that don't want to use product.ul and only want the same features as v7 wouldn't like to install a module that adds features that they don't want/need. There is no group "Track logistic units" in v8 ; I guess you refer to the group with XMLID "stock.group_tracking_lot" which is called "Manage Packages" in v8. The problem is that this group is required to track the packages, but you may want to track packages and not use the object product.ul. So we would need to create a new group "Manage Logistic Units" that would be created by our module. |
I see better to say "Put in last pack", but what happens when there is no last pack? I insist to merge both because the functionality is too short for a module, and it's perfectly compatible. Yeah, the group I mean is that, and is labelled in general configuration as "Use packages: pallets, boxes, ... " |
I prefer "Put in current pack", because irl, the pack below your hands is "the current pack". |
#. module: stock_packaging_usability_ul | ||
#: field:stock.select.ul,create_uid:0 | ||
msgid "Created by" | ||
msgstr "Created by" |
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.
Please leave translation empty if not translated
👍 Fully operationnal for our mail-order service. |
👍 I also prefers "Put in current pack" for the fact that we should or not merge the module both solution seem correct for me. So I am ok with the current one |
Add modules stock_packaging_usability and stock_packaging_usability_ul
This contribution includes 2 modules that work together (that's why I put them in the same PR):
stock_packaging_usability: it restores the button "Put in current pack" which was native in v7 but is not present in v8, and it adds a button "Put residual in new pack" which puts all the lines that are not already in a pack in one single new pack
stock_packaging_usability_ul: it depends on the module stock_packaging_usability and extends it behavior: when you go "put in new pack" or "Put residual in new pack", it will ask you to choose a product.ul (logistical unit) that will be set on the new pack.