Friday, September 28, 2018
5 changes
Enhancements to existing features
Point of Sale settings now show barcode scanner-related options only when a scanner is configured through the PoS box. This keeps the setup screen cleaner and reduces confusion for users who do not use barcode scanning.
Original PR description
The default barcode nomenclature should indeed only appear if you defined that there is a barcode scanner connected to your PoS. So the only thing is that the text "barcode scanner ..." in the settings should only appear, if I say that I connected a barcode scanner to my posbox. After this commit - Barcode scanner will be display only if scanner is selected in posbox settings. This commit is related to task# 1871378. 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
This change makes project kanban records easier to customize for teams extending Odoo. It enables partners and developers to adapt how project cards behave without changing core code, supporting more flexible customer-specific workflows.
Original PR description
Description of the issue/feature this PR addresses: You are not able to make inheritance "KanbanRecord" object via "extend" or "include" functions. It’s because we cannot reach Class and only get access to the instance of that class. "extend" or "include" methods is available only for widgets that are returned by the main function. The update allows to get/inherit KanbanRecord object. Current behavior before PR: We cannot use "extend" or "include" for "KanbanRecord" object Desired behavior after PR is merged: Possibility to create a new record (via the extend() method) or modify an existing object (via the include() method). -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr @it-projects-llc
CRM configuration forms for stages, lead tags, and lost reasons now use the standard Odoo form layout. This makes these screens look cleaner and more consistent with the rest of the system, improving usability for teams managing CRM settings.
Original PR description
Description of the issue/feature this PR addresses: Create a neat form view for these menus Current behavior before PR: The form views have no `<sheet>` which results in a not really beautiful form view Desired behavior after PR is merged: A great looking form view like most views in Odoo. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The point of sale order line matching now starts from the most recent items, so products are added to the first relevant recent line instead of scanning the full order. This can make checkout behavior more efficient and better aligned with cashier expectations when similar products are already in the order.
Original PR description
Description of the issue/feature this PR addresses: more efficient iteration to get the orderline to add the product to Current behavior before PR: iterating from orderlines start till the end taking the last matching one Desired behavior after PR is merged: iterating starting from the end of the orderlines, taking the first matching -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Mexican localization now makes unit of measure settings accessible from the Invoicing menu. This helps businesses configure invoice requirements without needing to install the Sales app.
Original PR description
In Mexican Localization is necessary to configure the UoM for invoices. To avoid installing the sale module, We add the UoM menu in the `Invoicing` menu. 