Daily updates from Odoo
Monday, October 23, 2017
5 changes
Enhancements to existing features
Mailing list managers can now merge selected lists into a new or existing list while avoiding duplicate recipients and excluding opted-out contacts. Duplicating a mailing list also copies its recipients, reducing manual work and helping teams manage audiences more reliably.
Original PR description
Description of the issue/feature this PR addresses: - It should be possible to merge mailing lists and remove duplicates when doing it. - When duplicating a mailing lists, the contacts are not copied. Current behavior before PR: - Currently we not able to merge mailing list and when duplicating mailing list, the contacts are not copied in duplicate mailing list. Desired behavior after PR is merged: - Now we able to merge mailing list with or without removing contacts (Recipients). - Now when duplicating mailing list, the contacts are copied in duplicate mailing list. ## I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr - Add file mail_merge_mailing_list.xml and mail_merge_mailing_list.py for wizard merging mailing list. Task : https://www.odoo.com/web#id=23490&view_type=form&model=project.task&action=327&menu_id=4720 Pad : https://pad.odoo.com/p/r.0fbe7e92b6fd5ec2c80845066bdc16de
This improves how website pages keep track of the template and view being rendered, even after the page response is processed. It helps related business features, such as CRM tracking, identify the correct page without extra lookups, improving reliability and efficiency behind the scenes.
Original PR description
This commit is related to enterprise commit adding crm_track option to @routes. Before this commit: 1. We could not get template's name after dispatch() had been called. Indeed, it will remove the…
This commit is related to enterprise commit adding crm_track option to @routes. Before this commit: 1. We could not get template's name after dispatch() had been called. Indeed, it will remove the template name from the response (response.flatten()) to make it not considered as 'qweb' anymore (is_qweb()). We need the template in some case. Eg: In case of website_crm_score, after the dispatch() we still need the template's name to retrieve the @route's view being rendered to check if it was trackable or not. 2. To make an RPC that directly READ or WRITE to a record, we need its ID. In case of a page with a main object other than ir.ui.view, we would need to make extra RPC to get the view's id of the page based on the view's name that we got on the HTML data attributes. Now: 1. On response's INIT, we store a copy of the template's name. 2. We set the view's ID on HTML data attributes clientside. 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
Expense sheets now show account and product information directly on expense lines, making reviews clearer for managers and finance teams. The update also adds currency symbols and totals in the line footer so amounts are easier to verify at a glance.
Original PR description
Description of the issue/feature this PR addresses: - expense sheet usability feedback Task:https://www.odoo.com/web#id=28701&view_type=form&model=project.task&action=333&active_id=131&menu_id=4720 Pad:https://pad.odoo.com/p/r.c4b7cbee191cbf2e50f53faee295f6f6 Current behavior before PR: - Account and product fields are not present. Desired behavior after PR is merged: - Adding Account and Product fields. - Add currency symbol in expense lines. - Display total in footer of expense lines. ## I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Adds warning prompts when confirming or validating sales, purchases, invoices, and stock documents involving partners with configured warnings. This helps staff catch important customer or vendor notes before completing key business workflows.
Original PR description
Task : https://www.odoo.com/web#id=34118&view_type=form&model=project.task&action=333&active_id=131&menu_id=4720 Pad : https://pad.odoo.com/p/r.984bdc1e042fce5c4b6198eec33b03d0 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Users can now remove a custom app background in Odoo Studio and return it to the standard Odoo look. The background change controls were also moved and polished in the app switcher, making customization easier to manage.
Original PR description
Before this commit, Unable to reset custom background to Odoo default once you set. With this commit, Add Reset Background option to reset already set custom background to Odoo default.