Monday, December 7, 2020
15 changes · master
Enhancements to existing features
Portal users can now send chatter messages and immediately see them appear without the page refreshing. Attachments in portal messages also look more consistent with the backend and can be previewed in a document viewer, with fixes for access and download issues.
Original PR description
Description of the issue/feature this PR addresses: Task-ID: https://www.odoo.com/web?#id=2054662&action=327&model=project.task&view_type=form&menu_id=4720 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
The CRM quotation wizard no longer offers an option to continue without linking a customer. This simplifies the sales flow and helps ensure quotations are created with the required customer information.
Original PR description
PURPOSE Clicking on 'New Quotation' button on the lead, a wizard is opened, with three radio options out of which the last one (nothing) seems to be of no use. SPECIFICATION Remove the option 'nothing' from the wizard and it's related code. PR Task 2360863 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Companies can now choose between the standard EC Sales List and versions tailored to local country requirements. Belgium and Luxembourg intrastat taxes are enabled by default, making cross-border reporting easier and more consistent.
Original PR description
Adapt EC Sales List report to meet current company country requirements. User can now choose to display global report (same as previous EC Sales List report) or display company specific report meeting country specific requirements. Task: 2217469
Purchase orders can now be identified by whether they are standard procurement orders or commission-related orders. This supports more precise access rules, helping businesses control who can view or manage commission purchases separately from regular purchasing activity.
Original PR description
Aiming for more fine-grained access rules, this commit introduces a new field: purchase_type. Business flows dictate its value: - By default, a purchase order's purchase_type is: procurement. - In the context of commissions, purchase_type is: commission. Task: https://www.odoo.com/web#active_id=2276754&cids=1%2C3%2C5&id=2276754&menu_id=&model=project.task
The EC Sales List report now lets companies choose between the standard global view and a version tailored to their country’s reporting requirements. This helps businesses meet local compliance needs while keeping the familiar generic report available.
Original PR description
Adapt EC Sales List report to meet current company country requirements. User can now choose to display global report (same as previous EC Sales List report) or display company specific report meeting country specific requirements. Task: 2217469
Survey-related appraisal activities now include a direct link to the selected survey template. This makes it easier for employees or managers to open the right feedback survey from the activity description, reducing extra navigation.
Original PR description
**PURPOSE** Add a link in a Activity description is a standard behavior. The link is not added for survey activities. **SPECIFICATION** Adding a link to survey activities which directly redirects to selected survey template's URL. **LINKS** PR https://github.com/odoo/enterprise/pull/14189 Task- 2354467
Miscellaneous changes
Before this commit, refresh the forecast report can lead to error if this report refer to a product variant (`product.product`). As it lost to which model the report is supposed to refer, it take the one by default (`product.template`) which can lead to error (display a traceback if the ID doesn't exist or display the report for another product if the ID exists). How to reproduce: Open the Forecasted Report for a `product.product` (from the stat button or from the `sale.order.line` widget f
Original PR description
Before this commit, refresh the forecast report can lead to error if this report refer to a product variant (`product.product`). As it lost to which model the report is supposed to refer, it take the one by default (`product.template`) which can lead to error (display a traceback if the ID doesn't exist or display the report for another product if the ID exists). How to reproduce: Open the Forecasted Report for a `product.product` (from the stat button or from the `sale.order.line` widget for example) then refresh the page. task-2362313 issue #59924 Forward-Port-Of: odoo/odoo#60149
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 Forward-Port-Of: odoo/odoo#62178
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 Forward-Port-Of: odoo/odoo#62178
Forward-Port-Of: odoo/odoo#62679 Forward-Port-Of: odoo/odoo#62622
Original PR description
Forward-Port-Of: odoo/odoo#62679 Forward-Port-Of: odoo/odoo#62622
STEP: * install pos_cache * create some products (this step is not needed in demo database) * open POS BEFORE: error "TypeError: Object of type 'datetime' is not JSON serializable" AFTER: no errors WHY: * Since Odoo 12 date fields are not strings: https://github.com/odoo/odoo/commit/960360afe478a8f7b9c456721b5591154952a37d * Since Odoo 14 fields lists to read contains write_date: https://github.com/odoo/odoo/commit/c6397ab3b3654da336a4269a81d5d91016baf520 -- see models.js ---
Original PR description
STEP: * install pos_cache * create some products (this step is not needed in demo database) * open POS BEFORE: error "TypeError: Object of type 'datetime' is not JSON serializable" AFTER: no errors WHY: * Since Odoo 12 date fields are not strings: https://github.com/odoo/odoo/commit/960360afe478a8f7b9c456721b5591154952a37d * Since Odoo 14 fields lists to read contains write_date: https://github.com/odoo/odoo/commit/c6397ab3b3654da336a4269a81d5d91016baf520 -- see models.js --- opw-2410334 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 Forward-Port-Of: odoo/odoo#62952
In 376891294 the default purchase.order view tree was changed to have different view with dashboard. But the current view referenced: ('parent.state', 'not in', ('purchase', 'done')) which seems incorrect because an x2many view towards purchase.order could currently only be used for purchase.requisition (doesn't have purchase/done as state value) and stock.production.lot (doesn't have state field) or a customization that might not have state field. With this change, we copy what there wa
Original PR description
In 376891294 the default purchase.order view tree was changed to have
different view with dashboard.
But the current view referenced:
('parent.state', 'not in', ('purchase', 'done'))
which seems incorrect because an x2many view towards purchase.order
could currently only be used for purchase.requisition (doesn't have
purchase/done as state value) and stock.production.lot (doesn't have
state field) or a customization that might not have state field.
With this change, we copy what there was originally on this field.
opw-2381767
Forward-Port-Of: odoo/odoo#62903Steps to reproduc the bug: - set referral user right on user U - set U as "Referred by" on an applicant A - log as U and go to the referral app - click on ongoing referral Bug: Access right error U should see the applicants referred by him opw:2409589 Forward-Port-Of: odoo/enterprise#15143
Original PR description
Steps to reproduc the bug: - set referral user right on user U - set U as "Referred by" on an applicant A - log as U and go to the referral app - click on ongoing referral Bug: Access right error U should see the applicants referred by him opw:2409589 Forward-Port-Of: odoo/enterprise#15143
Before: The test 'click button scale in empty gantt with sample="1"' failed randomly. This was caused by the random generation of field values in SampleServer which can sometimes not generate dates for today's range. Now: In the above test, we patch SampleServer._getRandomDate to always return today/now. This makes the test deterministic as every record will be in today/now 's slot. Forward-Port-Of: odoo/enterprise#15011
Original PR description
Before: The test 'click button scale in empty gantt with sample="1"' failed randomly. This was caused by the random generation of field values in SampleServer which can sometimes not generate dates for today's range. Now: In the above test, we patch SampleServer._getRandomDate to always return today/now. This makes the test deterministic as every record will be in today/now 's slot. Forward-Port-Of: odoo/enterprise#15011
The CRC value put into the MDC tag of a message was not being padded to the right length. It should have been padded to 8 characters but was only being padded to 2. This means that if you had a CRC like f744682, no padding would happen to 0f744782, and an odd-length exception would get thrown by unhexlify. This could for example disrupt the sending of a TransactionRequest, which would cause a payment request to fail. Ticket: 2357144 Forward-Port-Of: odoo/enterprise#15062 Forward-Port-O
Original PR description
The CRC value put into the MDC tag of a message was not being padded to the right length. It should have been padded to 8 characters but was only being padded to 2. This means that if you had a CRC like f744682, no padding would happen to 0f744782, and an odd-length exception would get thrown by unhexlify. This could for example disrupt the sending of a TransactionRequest, which would cause a payment request to fail. Ticket: 2357144 Forward-Port-Of: odoo/enterprise#15062 Forward-Port-Of: odoo/enterprise#14902
Have a partner in need of actions (invoices with payment date far in the past) GO to Accounting>Customers>Followup Reports Tick all the partner lines as blocked Try to send the followup email/execute the followup action The system will perform the followup action, possibly sending a warning letter invoice with no lines. This commit make the followup actions skip invoices with blocked lines opw-2363814 Forward-Port-Of: odoo/enterprise#15075
Original PR description
Have a partner in need of actions (invoices with payment date far in the past) GO to Accounting>Customers>Followup Reports Tick all the partner lines as blocked Try to send the followup email/execute the followup action The system will perform the followup action, possibly sending a warning letter invoice with no lines. This commit make the followup actions skip invoices with blocked lines opw-2363814 Forward-Port-Of: odoo/enterprise#15075