Monday, July 22, 2019
5 changes · master
Enhancements to existing features
Odoo removes an obsolete language setting that no longer affects how translations work. This cleans up language management and translation-related processes without changing day-to-day user workflows.
Original PR description
The technical field `translatable` of a res.lang has become useless Task id=2034552 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Salespeople will no longer receive an email simply because a customer opens a quotation. This reduces mailbox clutter while keeping the important order confirmation notifications unchanged.
Original PR description
Purpose of this commit, When a quotation is viewed by the customer, salesperson will no more receive an email that customer has viewed the quotation. Task link - https://www.odoo.com/web#id=1950368&action=327&model=project.task&view_type=form&menu_id=4720 Pad link - https://pad.odoo.com/p/r.778efed9a4442b91460d05e2dedeeb74 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update modernizes how the base system records creation and update timing by using the platform’s standard tracking fields instead of older custom columns. It supports ongoing cleanup of legacy internal models and should have no visible impact on everyday users.
Original PR description
Instead of date_init/date_update, let the ORM use its own fields
Resolved issues and error corrections
This update corrects several typos and wording issues in the SMS feature. It helps make SMS-related screens and messages clearer and more polished for users, without changing core functionality.
Original PR description
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
Code cleanup and technical improvements
The Documents app now stores workflow tag conditions in a simpler structure, making rules easier to maintain and less prone to confusion. Tag names also show their category/facet alongside the tag, helping users distinguish similar tags when configuring or reviewing document workflows.
Original PR description
Refactoring of the tag conditions for workflow rules, after this commit they are stored in two many2many fields instead of contained in a `critera_tag_ids` record. The second commit adds a name_get to `documents.tag` to display the facet name. Task: #1975015