Daily updates from Odoo
Wednesday, June 13, 2018
4 changes
Enhancements to existing features
This update makes it easier for businesses and partners to customize restaurant point-of-sale screens and action buttons. It enables tailored workflows without changing the core system, helping restaurants adapt the POS to their specific operational needs.
Original PR description
Description of the issue/feature this PR addresses: You are not able to make inheritance "action_button" and "screens" POS Restaurant objects 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 action_button and screens POS Restaurant objects. Current behavior before PR: We cannot use "extend" or "include" for "action_button" and "screens" POS Restaurant objects Desired behavior after PR is merged: Possibility to create a new screen widget or action button (via the extend() method) or modify an existing screen widget (via the include() method). -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Sales order lines can now use a customizable product description instead of always relying on the default product name. This gives businesses more flexibility to tailor descriptions shown on quotes and orders without changing the underlying product record.
Original PR description
Introduce new method _product_name() called from product_id_change()
Point of Sale now displays discounts when the related pricelist option is enabled. This helps cashiers and customers see applied savings more clearly during checkout, improving price transparency.
Original PR description
Task : https://www.odoo.com/web#id=1853454&action=333&active_id=1251&model=project.task&view_type=form&menu_id=4720 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
Maintenance equipment can no longer be deleted while related maintenance requests still exist. Users must first remove the equipment from those requests, ensuring the change is logged and the request history remains clear.
Original PR description
…change Description of the issue/feature this PR addresses: Any equipment can be deleted without taking care of the existing requests for this equipment. Current behavior before PR: Deleting an equipment removes the equipment from the existing requests linked to this equipment, but we have no clue on what happened looking at the existing requests. Desired behavior after PR is merged: Deleting an equipment will throw an error if requests are existing for this equipment. To remove an equipment, the user should first remove the equipment from its requests, what will trigger a log in mail.thread. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr