Odoo Changelog — 2016-03-25

Friday, March 25, 2016

2 changes · master

New Features(2)

New functionality added to Odoo

[ADD]website_quote:add sequence Field with handle widget

Coremasterwebsite_quote

Sales teams can now choose the display order of suggested products on website quotations. This makes quotations easier to tailor, helping present optional items in the most relevant order for customers.

Original PR description

Task:https://www.odoo.com/web?#id=21482&view_type=form&model=project.task&action=327&menu_id=4720
Pad:https://pad.odoo.com/p/r.b0Q947626UPC4gdg

#quotations#suggested products#ordering

Add template tracability for account and taxes

PR #11435

CoremasteraccountMedium

Accounting records for accounts and taxes can now keep a clear reference to the template they came from. This helps localization teams and partners apply future updates more safely and accurately, without relying on fragile matching by names or codes.

Original PR description

Description of the issue/feature this PR addresses:
There is no clear and unequivocal way of identifying a corresponding template to it's record in the case of acocunt.tax and account.account. With this situation, we potentially have a loss of state on those recrods when it comes to actualisations. actualisations can be necesary, wehn localisations or partners want to overcharge ex post !!! some basic functionality of the public l10n modules with some more advanced logic. Just comparing names, codes, etc is not enough. We need clarity and reliability.

Current behavior before PR:
In the current use case, you need to rely on potentially unreliable heuristics to identify corresponding templates.

Desired behavior after PR is merged:
You can rely on a clear textual identifier on the records, which store the string of the template's external id in an extra field. Like this you have the full flexibility to construct a variety of reliable update paths. copy = false is preventing undesired updates on user creted records, when the user is using the copy tactic t create new records.
## 

I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Description of the issue/feature this PR addresses: There is no clear and unequivocal way of identifying a corresponding template to it's record in the case of acocunt.tax and account.account. With this situation, we potentially have a loss of state on those recrods when it comes to actualisations. actualisations can be necesary, wehn localisations or partners want to overcharge ex post !!! some basic functionality of the public l10n modules with some more advanced logic. Just comparing names, codes, etc is not enough. We need clarity and reliability. Current behavior before PR: In the current use case, you need to rely on potentially unreliable heuristics to identify corresponding templates. Desired behavior after PR is merged: You can rely on a clear textual identifier on the records, which store the string of the template's external id in an extra field. Like this you have the full flexibility to construct a variety of reliable update paths. copy = false is preventing undesired updates on user creted records, when the user is using the copy tactic t create new records. ## I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr