Daily updates from Odoo
Wednesday, November 14, 2018
5 changes · master
New functionality added to Odoo
Selecting a product on an employee expense can now automatically apply the matching analytic account and tags based on existing default settings. This reduces manual entry, improves consistency in expense reporting, and helps costs be categorized correctly.
Original PR description
When a product is selected for an expense, an analytic account is automatically selected based on the default settings.
Enhancements to existing features
Point of Sale now automatically uses the default barcode rules when no specific setup is chosen. This reduces confusion for businesses that start using barcode scanners without enabling extra settings, while having little to no effect on users who do not scan barcodes.
Original PR description
Remove the barcode_scanner Boolean and always load the default nomenclature if non other is defined in pos.config. Because barcode scanners are seen as keyboard by the computer, they always work in the point of sale. Because of this some clients begin using them without activating the nomenclature in pos.config. Barcodes get only recognized if search-fields are selected this way, resulting in clients complaining about the workflow. Enabling the default Nomenclature by default will have almost no effect on the loading time of the point of sale and has no influence on the work flow if not using a scanner.
Archiving a warehouse now also archives its related stock locations, routes, and rules. This prevents inactive warehouses from leaving active related records behind, reducing operational inconsistencies in inventory management.
Original PR description
[IMP] stock: archive warehouse Archiving a warehouse didn't archive its related locations, routes and rules. So we now archive the related objects and add some constraints to avoid having an inconsistent state in stock with archived warehouse. TASK-ID: 30659
When employees select a product on an expense, the system now automatically applies the relevant default analytic account when one is configured. This reduces manual entry and helps keep expense reporting and cost allocation more consistent.
Original PR description
When a product is selected for an expense, an analytic account is automatically selected based on the default settings. Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Resolved issues and error corrections
Payroll calculations now support multiple workday or input lines with the same code, such as several holidays of the same type in one payslip period. This prevents payroll from silently counting only one entry and helps businesses produce more accurate payslips when payroll rules are updated accordingly.
Original PR description
Before this commit, inputs (workdays or inputs) could conform two lines having the same code (Example: two holidays of the same type in the payslip period) This commit returns recordsets, where…
Before this commit, inputs (workdays or inputs) could conform two lines having
the same code (Example: two holidays of the same type in the payslip period)
This commit returns recordsets, where previously singletons were returned.
This requires migration of python code hr rules as they need to implement
`mapped` where previously accessing values directly:
Eg.: sum(RecordSet.mapped('amount'))
However, this migration is only necesary for rules that would have required this
fix anyhow.
**Description of the issue/feature this PR addresses:**
- Calculation errors when dealing with multiple inputs sharing the same code
- This case occurs for example: If holidays of same type are taken multiple occasions during the payslip period.
**Current behavior before PR:**
- Only the first such line is taken into account
Desired behavior after PR is merged:
- A python rule, using `mapped` can be construed to fetch the sum of all lines
- This calculation error can be solved thereby.
**Note:** Please do not close, even if not immediately accepted (`wishlist` tag). This PR is meant to be carried along and actively maintained, until this semantic will be completed this way or another.
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
@xoe-labs