Pack operations will not appear in a transfer wizard or bar code interface anymore, but
in the picking form itself. Some wizards are still needed however to ask whether a
backorder needs to be created and whether we need to do an immediate transfer
The biggest change in the model is in the picking where the locations of the picking
are not a related anymore, but need to be set. That is why the tests need to be changed.
This allows also to have pickings without moves initially and just move one pack e.g.
Locations won't be visible on stock moves in a picking either. (as they should be those of the picking)
In order to avoid confusion, the pack operations are created immediately when stock is reserved and we
are not waiting until the wizard or the bar code interface is launched anymore.
The recompute button previously in the barcode interface will only appear when the reservation changed
and the user indicated in the pack operations that something was moved already. Otherwise it will
recompute the pack operations. That way the reservation on the stock moves, is reflected by the pack operations.
Return pickings are not confirmed automatically when confirming the return wizard.
That should make it possible to choose another location for the return. (Don't return in output e.g.)
Barcode scanning is not in this commit.
POS users/managers should not have any access
to the account.move/account.move.line, since
they are not accountants.
Regarding the bank statements, they should only
have access to the ones coming from the POS
specifically.
opw-628000
Allow to add a step between address and payment form to allow to customize the
checkout form.
Only fields prefixed with x_ value are allowed. So it's to the user to implement
automated action if they want write on a default field not prefixed by x_.
If you filter the list of products with category, we don't display all the attributes,
but only the list of attributes impacted by the current sub-select of products.
Don't call update_cart at each click, but wait until 500 ms before that json
call is trigerred.
If poeple click 3 times quickly on the plus, that will avoid to sent three
requests with set_qty 1, set_qty 2, set_qty 3, but only one with set_qty 3.
Based on / fix#6102
If we are in dev mode, _read_template has no cache, so impossible to clear the cache.
Some code call directly the _read_template, it's why the condition is duplicated (fe4df440a0)
sale_crm : prevent the creation of SO from lead form view (avoid bypassing process)
website_quote : "View Quotation" on SO form view should not be a state button, so it is now replaced by a link near the field
The datetime widget use the "keypress" event to detect if it has been
changed. Unfortunately, some keys, such as backspace, do not fire a
keypress event. This commit listen instead on the 'change' event, which
should fire when the input has changed.
from demo to data. Indeed when installing the HR module people
expects some basic data for their daily management: sales
and administration are basic departments used in every
company.
This reverts commit 79c338dcb352be3d40118f998a76e1b7576a35da.
This commit has been done hastily without review. Moreover it
mixes changes related to different stuff.
The commit is then reverted to allow a propre review and cleaning
of the branch.
sha-odoo