[16.0] stock_release_channel: pre-migration as not installable #600
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 using stock_dynamic_routing, the moves are reassigned to a new picking (with StockMove._assign_picking()), and the original picking is cancelled if it contains no moves anymore. As we want to keep Note: maybe we should extend the assign picking mechanism to never assign a move in a picking with a different release channel (channel is empty or identical). As we extend it in stock_picking_group_by_partner_by_carrier, it should be a new dependency/glue module on it, or better, only extract the hook added by stock_picking_group_by_partner_by_carrier for the domain in a base module, used by both.
Reverts previous commit and re-assign the release channel in case the released transfer has changed / moves have been released partially. The rules result may change and we want them in the proper channel.
As these numbers are estimates (all moves even if not ready)
* Use new style of progress bars * Add progressbar for showing progress of transfers *before* the outgoing one (chained ones) * Improve CSS and labels
The "code" can be read only to base.group_system.
It will be used later the automatic release by commercial partner.
The initial automatic release allows to release a number of transfers N up to a max of X in progress transfers at a time. Introduce a selection of types of automatic release, with, alongside the former "Max", a new grouping by commercial partner. When using this automatic release, we take the first (by priority) transfer ready to release, and all the transfers with the same commercial partner, then release this whole group of transfers.
1. The Overall Progress of a Release Channel is always shown as
a fractional number. This required changing the Javascript
of the widget `progressbar` to add a new option to allow this.
The idea is to submit this change to Odoo.
2. The Overall Progress computation has been changed, to be now:
"Done Today" / sum("To Release", "To Do", "Done Today")
When order is confirmed, it triggers channel assign. If the user that confirms the order doesn't have the correct rights, then an error is raised. Resolves: 2562
So normal users can process a sale order.
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.
Migration wip here #493