Wednesday, March 3, 2021
12 changes · master
Enhancements to existing features
Customers created from the CRM kanban quick-create flow now receive the same salesperson and sales team assignment as customers created from the full lead form. This keeps ownership consistent across creation methods and helps sales teams avoid unassigned or misrouted customer records.
Original PR description
a customer created through the form view automatically gets assigned to the user (salesperson) but customer-created through the kanban quick create does not add the user after this commit, the salesperson will be assigned upon creating a customer from kanban quick create Task: https://www.odoo.com/web#id=2446969&action=4043&model=project.task&view_type=form&cids=2&menu_id=4720 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Payment processing failures will now include more specific error details in the logs. This helps support and operations teams understand why a payment-related issue occurred, making troubleshooting faster and more effective.
Original PR description
Description of the issue/feature this PR addresses: Better feedback in the logs Current behavior before PR: The log basically prints "Transaction post processing failed" but has zero added value. Desired behavior after PR is merged: By adding in the exception its details it gives a good idea of why this crashed. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Expense records now show a more explicit payment status, making it easier for users to understand whether an expense has been paid. The setup error message was also rewritten to clearly tell users where to specify the expense journal before creating accounting entries.
Original PR description
- Add "payment_status" field to be more explicit. - Turn error message "Expenses must have an expense journal specified to generate accounting entries." into "Specify expense journal in tab Other Info to generate accounting entries." Task: 2424870
Log output now highlights each worker process ID with a consistent color, making it easier to follow activity from a specific worker in multiworker setups. This helps operations teams review logs faster and troubleshoot issues with less confusion.
Original PR description
In multiworker mode it is hard to keep track of the log trace of a particular worker. We now color the PID using a different color per PID, as there are only 8 color available, we cycle throught them.
Product variants can now carry their own Intrastat commodity code instead of always inheriting the product template value. This improves reporting accuracy for businesses whose variants differ enough to require separate trade classification, while reusing the existing variant-field behavior.
Original PR description
Extract the way images are set on a product into a new method to allows having the same behavior with other variant fields. Now also used to set an Intrastat code varying from the template one. Task id #2369561 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Links to websites outside the current Odoo domain now open in a separate browser tab from readonly Pad widgets and backend HTML fields. This helps users keep their Odoo work open while safely navigating to external resources, while internal links continue to open in the same tab.
Original PR description
This commit aims to change the behaviour of <a> links in readonly pad widgets. If the <a> redirects to a page that isn't in the domain (hostname different of the current location hostname), we open it in a new browser tab by adding a target. Limitation : If you use the collaborative pad for a while and then go back to a web editor html field, you'll have to edit each link in order that the link opens a new tab by clicking on it. task-2377544 Description of the issue/feature this PR addresses: - Opens the external <a> links in new tab of the browser when clicked. Current behavior before PR: - All <a> links are opened in the current tab. Desired behavior after PR is merged: - Open external <a> links in new tab of the browser when clicked. - Open internal (from the domain point of view) links in the current tab when clicked. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Error pop-ups can now show a more specific title instead of the generic “Something went wrong.” This helps users better understand issues such as access problems without unnecessary confusion or alarm.
Original PR description
[IMP] base, web: custom title in error modal In a ancient age were the sole exception were `except_osv` and `except_orm`, every exception needed two arguments, an error title and an error message. With the introduction of dedicated exceptions in only the error message remained as the title was given by the exception type. It turns out most of the time the generic `UserError` exception is raised for missuses that don't fall in any other category and that the error modal the user see is entitled "Something went wrong" which is too much generic and unnecessary scary. We introduced a way to customize the modal title by providing a `title` argument when raising a odoo custom exception. -- [FIX] crash_manager: use given title on modal Via the browser, try to access a resource you don't have access to, an Access Error modal is open but the title was saying "Something went wrong" instead of "Access error". -- Task: 2206851
Certification preview pages now show the certification name in the browser tab followed by “Preview.” This makes it easier for users to identify the correct preview when working with certificates, especially across multiple tabs.
Original PR description
Purpose
title of the browser window was not set properly.
Specifications
need to improve the title of browser window ("[name_of_the_certification] Preview")
here: https://drive.google.com/file/d/1MarIkEFQRS8B06kOBZh_YBZMmuWQ3ejC/view
PR # 64013
task-id: 2341847
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prEmployee forms now track changes to the job field, making it easier for HR teams to follow role updates over time. This improves visibility and auditability of employee job history within the HR app.
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
Certification documents have been redesigned with a more modern look and clearer presentation. Certificates now show a consistent unique certification number and preview pages display the certification name in the browser tab, making them easier to identify and share.
Original PR description
PURPOSE Improve certification templates and make them more aligned with current state of the art certifications. SPECIFICATIONS Design has been completely redone to be more modern. Also displays dynamic certification number based on the ID of certification record for both modern and classic layouts. It consists in minimum 10 digits. It means that if the ID of the record is 5 it is displayed as 0000000005. Also improves the behavior by adding name of the certification in page title so that use can see the proper string on browser tab. For doing so, we create a new wrapper template that sets the title for the page, and use an iframe to loads the pdf file from existing controlloer (which returns response for the preview pdf). LINKS Task ID-2341847 COM PR #66028
Event users get clearer guidance on key actions, cleaner status handling when moving sessions between stages, and a more prominent link to discover more events in reminder emails. Demo pricing for event registration products is also adjusted so sample data better reflects normal business margins.
Original PR description
This commit aims at refining the UX for events, notably: - create a helper for the magic button on the event_track form, because without this the user won't be able to understand what the button does. - on stage update, the kanban state will be automatically set to "gray" beacause when changing stages it does not make sense to keep the previous kanban state especially when it is set to "green" or to "red". - make the cost of the event registration product demo data lower then the sale price as it is not normal to have a sale price lower then the cost. - change the style of the "discover all our events" marketing link in the event reminder email template in order to make it pop a bit more for the user as this is an important link Task-2451125 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Product variants can now use their own Intrastat commodity code instead of always inheriting the product template code. This helps businesses report trade statistics more accurately when variants of the same product are classified differently.
Original PR description
Variants of a product can have different commodity code, which is not currently supported by Odoo. This will allow for variants to use either the same code that its template (default behavior) or a case-by-case code. Task id #2369561