Thursday, September 7, 2023
15 changes · master
Enhancements to existing features
Accounting now includes validation helpers for structured payment references used in Belgium, Finland, Norway, Sweden, and ISO formats. This improves payment communication accuracy and supports more country-specific banking requirements for SEPA-related workflows.
Original PR description
Add helper functions to check structured communication references for ISO (existing), Belgium, Finland, Norway and Sweden. [task-3284330](https://www.odoo.com/web#id=3284330&cids=1&menu_id=4720&action=333&active_id=967&model=project.task&view_type=form) Related to https://github.com/odoo/enterprise/pull/41629 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Event attendees can now open tickets directly in a responsive web page and download tickets more easily from emails and confirmation pages. The ticket layout is simplified for better printing and clearer attendee details, reducing friction after registration or purchase.
Original PR description
The tickets are reworked, made easier to print and have their structure reworked for qr code addition (in ENT branch). Also they are easier to download as buttons are added to do so. 1. Design…
The tickets are reworked, made easier to print and have their structure reworked for qr code addition (in ENT branch). Also they are easier to download as buttons are added to do so. 1. Design Tickets have their background removed in order to ease their printing. More room is given to details, the design is simplified. New SIMPLIFIED TICKET The confirmation email will now contain a link "See tickets" leading to a new version of the full page ticket, called "simplified". It does not generate / download PDF but rather leads to a rendered qweb html page, with design working properly on different screen sizes. The design is a tweaked version of the full_page ticket template. It allows user to see their ticket directly without needing a pdf viewer. 2. Download Tickets Buttons "Download / See Tickets" Buttons are added in - Email Templates (Ticket and Badge) - The SO confirmation (if payment). All tickets, per event. - The registration confirmation (if no payment). All tickets in the same PDF. They are for the same event. In order to access tickets, a route event/tickets_dl is added in the controller. It takes an event_id, registration_ids and a hash based on those plus the database secret using tools.hmac. The groundtruth hash is obtained for given registration ids in the method _get_tickets_dl_access_hash on event.event. The route is used in all places listed above. The hash must be valid and attendees must exist. No condition on payment is set in tickets_dl as we want the download tickets link to work for non-free tickets as well at the end of the sale process, and as the sale order could not be linked to any invoice at that stage (if automatic invoices is not set in the settings), registrations being 'not paid' at that point. This could be cleaned in further work as different states are to be clarified. The route must be public as it must work even for public users. (from email or as public user registering on front-end) 3. Email Templates In order to have similar mail templates for badge and tickets, Registration Badge content is duplicated from Registration Confirmation and slightly tweaked, replacing existing body. Also, the info of the payment / order moved from full page ticket to the body of the confirmation email. 4. Sending Tickets On Payment In order to ease the process to find tickets when they are linked to the sale order, they are now sent on payment. When an invoice is paid, we check on potential linked sale order lines if there are linked event registrations. If so, a message is posted on the SO record, sent to the associated partner, with pdf attachments: 1 per event, with all tickets. A comment message is used so that the tikets and comment can be found on the portal chatter of the SO as well, for portal users. PR ENT - https://github.com/odoo/enterprise/pull/41164 PR UPG - https://github.com/odoo/upgrade/pull/5007 Task-3061851
The accounting dashboard wording is updated so cash journals use clearer terminology instead of language that could be confused with bank statements. This helps users distinguish cash and bank journal concepts more easily in day-to-day accounting workflows.
Original PR description
To avoid confusion between the concepts of journal cash and bank , I propose a change in terminology for the type of journal cash. 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
Products created or linked through POS combos are now available in the Point of Sale by default, reducing setup steps for staff. The update also prevents combo-related products from being disabled in POS, helping avoid broken combo offers during sales.
Original PR description
Products can be created directly from the `pos.combo` view. Before this PR, such products would not be automatically available in the POS app. This PR makes it so products linked to combos are available in POS by default. We also introduce an additional check that makes it so products associated to combos cannot be disabled in the pos. Task: 3481899 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Live chat sessions embedded on websites now use guest visitor records instead of broader public-user handling. This makes visitor conversations cleaner and more consistent across live chat, mail, CRM live chat, and website live chat flows.
Original PR description
*: mail, test_discuss_full, website_livechat. part of task-3332628 enterprise: https://github.com/odoo/enterprise/pull/45767 upgrade: https://github.com/odoo/upgrade/pull/5049
The website editor now lets users drag and drop content blocks within editable areas, making it easier to place new content between blocks that cannot be edited directly. This improves page editing workflows for cases like separators or template blocks where cursor placement was previously difficult.
Original PR description
- [REF] web_editor,mass_mailing,website: make `closestElement` support `predicate` - [REF] web_editor: prepare absolute containers for the movable node - [IMP] web_editor: drag and drop nodes within the editable PURPOSE The main reason is that when there are two block side by side that are not editable (eg. the `HR` tag, the `/template` block), it is impossible to set the cursor in between to add more content. task-2984709 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Users can now adjust the order of product attributes after adding them to a product. This makes product setup more flexible and helps businesses present product options in the preferred sequence.
Original PR description
Currently the user cannot modify the order as he adds new attribute to the product .In this commit he will be able to do that task-3451377 Desc
Sales and inventory settings now include Shiprocket as a third-party shipping connector. This makes it easier for businesses using Shiprocket to discover and configure shipping integration options from Odoo settings.
Original PR description
Shiprocket added in settings as a third-party shipping connector. task-3071078 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Chat windows can now be scrolled with common keyboard keys such as Page Up, Page Down, Home, and End. This makes conversations easier to navigate and improves accessibility for users who rely on keyboard controls.
Original PR description
Before this PR, it was not possible to scroll a chat window using page down/page up, home or end keys. This is because the thread component that is scrollable cannot became an activeElement. This PR fix this by adding a tabindex="0" on the scrollable element. Task-3468978
This update removes an old helper that was only used by legacy web tests. The affected tests have been moved to the newer WOWL approach, reducing maintenance overhead without changing business-facing behavior.
Original PR description
This util was used in : - owl_dialog_tests - field_one2many_tests - relational_fields_tests - gantt_tests (enterprise) These files are now converted to WOWL. 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 receipts are now easier to read by showing the expense name alongside the filename and improving how receipt previews are positioned. This helps employees and approvers quickly identify and review receipts without visual overlap or hidden titles.
Original PR description
The goal of this PR is to improve the readability of expense receipts on hr_expense and hr_expense_sheet. This PR do the following: - Add the expense name next to the filename - Vertically center the receipt on both model (was previously done in hr_expense but not for the sheet) - Make sure the title doesn't get hidden by the image (was previously done in hr_expense but not for the sheet) Also, to achieve the first point we had to modify the attachment so that we can retrieve easily the information of which line the attachment is attached. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Point of Sale screens now use one shared number pad component instead of several separate versions. This makes the interface more consistent across POS, IoT payment flows, and restaurant preparation displays, while reducing maintenance effort and improving test reliability.
Original PR description
pos*: pos_iot, pos_restaurant_preparation_display
At the moment, the point_of_sale module has 3 different implementations of numpads. This is absurd. In this PR we unify them all into a single numpad component.
One of the reasons why there are multiple numpads is because each requires a slightly different set of buttons. The new `Numpad` component provides a simple API which allows the consumer to specify what the buttons should be.
This is done by proving the `buttons` prop, which has the following type:
```js
buttons: {
type: Array,
element: {
type: Object,
shape: {
value: String,
text: { type: String, optional: true },
class: { type: String, optional: true },
disabled: { type: Boolean, optional: true },
},
},
}
```
In this PR we also provide a simple set of helper functions for the tours and adapt all of the existing tests accordingly.
[Odoo: odoo/132245
](https://github.com/odoo/odoo/pull/132245)Task: 3470346Live chat visitors in the Helpdesk website flow are now treated as guests when interacting with chatbots and support ticket creation. This improves consistency for anonymous website users and helps ensure support conversations can be converted into tickets more reliably.
Original PR description
part of task-3332628 community: https://github.com/odoo/odoo/pull/129770/files
SEPA payment files now recognize structured payment references and place them in the correct section of the file. This improves compatibility with banking standards in supported countries and reduces the risk of payment processing issues caused by incorrectly formatted references.
Original PR description
When creating SEPA files to perform payments, we did not check for structured references and always put the reference in the `Ustrd` field in the SEPA xml file. This change makes sure we check whether the reference of a move is a structured reference (ISO CF, BE, CH, FI, NO or SE), and if so, add the reference in the right `Strd` field along with the correct tags for that type of structured reference. [task-3284330](https://www.odoo.com/web#id=3284330&cids=1&menu_id=4720&action=333&active_id=967&model=project.task&view_type=form) Related to https://github.com/odoo/odoo/pull/122835
Event tickets and foldable badges now include QR codes alongside existing barcodes, making them easier to scan with smartphones. Ticket layouts have been adjusted to fit both codes, and sample tickets now show a default QR code.
Original PR description
As qr codes are simpler to scan on smartphones, they are added alongside the existing barcode on event full page tickets as well as foldable badges. Space on tickets is reworked and redistributed to do so. The example tickets on events are also given a default qr code. The qr code is based on the barcode and represents the same registration number. The route /report/barcode is used to generate the codes. It allows users to access their tickets even if they are not logged in. UPG PR - https://github.com/odoo/upgrade/pull/5007 COM PR - https://github.com/odoo/odoo/pull/120933 Task-3061851