Friday, August 10, 2018
9 changes · master
New functionality added to Odoo
This change adds an identifier in the Accounting settings screen so related enterprise features can be inserted in the right place. It is a small internal improvement that supports smoother configuration extensions without changing day-to-day accounting workflows.
Original PR description
When entering a description on a vendor bill, select automatically the account based on previous history. Task: 1872205 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Enhancements to existing features
Server actions can now work with selected records in a more direct and consistent way. This is a small internal improvement that makes customization code easier to write and maintain, without changing everyday user workflows.
Original PR description
Before this commit, you needed to do something like this to construct a "`self`": `self = record and record or model | records and records or model` after this commit you can just do: `for item in record | records:` It's just cosmetics and more akin to the new RecordSet api. Maybe the right thing to do on master? -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Resolved issues and error corrections
Pricelist tests now consistently use the euro currency, even if other installed modules have changed the sample data. This helps make test results more predictable and reduces failures caused by unrelated localization settings.
Original PR description
Before this another module, notably of kind localization could have altered the demo data. This commit ensures the price list is always standardized on EUR. This is one step towards making test executions idempotent and reduce side effects. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Server actions can now use common decimal calculation helpers when running automated Python logic. This helps businesses avoid rounding-related mistakes in comparisons, especially where company-specific precision rules matter.
Original PR description
Before this commit, in python code server actions, there was no (convenient) way to do a float comparison taking into account a digital precision supplied from the environment. This commit includes the most commonly used float arithmetic utilities from the `tools` package to te evaluation context. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Marketing campaigns can no longer be created using the mail blacklist as the target audience. This helps avoid contacting people who have opted out of mass mailings and keeps campaign setup aligned with consent expectations.
Original PR description
Task : https://www.odoo.com/web#id=33224&action=333&active_id=965&model=project.task&view_type=form&menu_id=4720 As Mail Blacklist is a list of recipient that doesn't want to receive mass mailing anymore, it does not make sens to allow to create a marketing campaing on this model.
The subscription form now places the Start Date on the left and the Date of Next Invoice on the right. This matches the natural reading order, making key subscription dates easier to scan and understand.
Original PR description
Start Date on the left and Date of Next Invoice on the right of the form view
The help text for a configuration option was corrected to avoid implying that a command installs every module. This reduces confusion for administrators and support teams when setting up or maintaining Odoo instances.
Original PR description
This is quite misleading, `-i all` does NOT install all modules Either this doc is wrong, then the semantic "all" is quite confusing, or the implementation itself is flawed and `-i all` is meant to install all modules, then it should be fixed there.. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The HR demo data now gives the administrator's employee record the same name and image as the related user account. This keeps sample employee information consistent and avoids confusion when reviewing or demonstrating HR records.
Original PR description
<b> Issue:</b> https://www.odoo.com/web?#id=1872292&action=333&active_id=1278&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
This fixes a Point of Sale report issue where the same information could appear twice because both an original field and its stored related copy were shown. The change keeps reports cleaner and reduces confusion for users reviewing sales data.
Original PR description
…ated stored to this field @mart-e You're the one for the PoS ?