Monday, March 4, 2024
9 changes
3 changes
Enhancements to existing features
Sending a field service report now first lets the user choose the report layout before opening the send dialog. This gives teams more control over how customer-facing reports look and helps ensure the right presentation is selected before sharing.
Original PR description
**Prior this commit:** On the click of 'Send Report' button, the 'Send Report' dialog is opened directly. **Post this commit:** When you click the 'Send Report' button, the user is first allowed to choose the layout, and then the dialog is opened. **Task**-3754747
Payroll dashboard warnings now load in the background instead of delaying the whole dashboard. This improves the experience for payroll teams on large production databases by making the dashboard available sooner while warning checks continue separately.
Original PR description
The payroll dashboard loading time can be really slow on a production database due to the computation of different warnings, we fix that by loading them asynchronously using an rpc call task-3597092
Warehouse users can now create a backorder in advance directly from the barcode app's gear menu while processing a transfer. This makes it easier to split remaining items into a follow-up transfer without leaving the barcode workflow.
Original PR description
In this commit ================== In this commit, we added a new action split (visible in barcode when pressing the gear icon) which allows to create backorder in advance for a transfer. Related Community PR: https://github.com/odoo/odoo/pull/120095 TaskId-3266824
6 changes
Enhancements to existing features
This update makes the preparation display service exportable, allowing businesses and developers to customize its functionality without duplicating code. Previously, the service could not be modified, forcing users to copy the entire service code to make any changes. This improvement enables cleaner, more maintainable customizations.
Original PR description
Currently it's imposible to patch preparationDisplayService, so it's not possible to make any customizations and the only workaround is copying the whole service's functionality. By adding the export declaration the file can be imported and the service can be patched, which allows to make customizations to it's functionality.
This update improves how follow-up messages are displayed in Odoo by removing excessive spacing that appeared in customer communications and PDF documents. The change consolidates HTML formatting to use line breaks instead of multiple paragraph tags, resulting in cleaner, more professional-looking messages.
Original PR description
In the HTML used for the message, we have used multiples "p" html balise which made huge spaces in the chatter or the pdf. By simply putting them in a single "p" and use "br", the extra spaces are gone. task: 3708071 Forward-Port-Of: odoo/enterprise#57519 Forward-Port-Of: odoo/enterprise#55497
This update improves the Point of Sale system by changing the label from "VAT" to "Tax" to be more inclusive of different tax types used globally (such as GST). Additionally, tax information is now properly displayed on POS receipts in India, ensuring compliance with local regulatory requirements.
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
README files have been added to all payment acquirer modules to document how each payment provider is technically implemented. This helps developers and maintainers quickly understand the specific implementation details, payment flows, and webhook mechanisms for each acquirer, making it easier to maintain and update payment integrations as providers evolve their APIs.
Original PR description
Each payment acquirer has its own implementation specificities: some implement a 'payment with redirection' flow and others a 'direct payment flow'; sometimes the 'payment with redirection' flow is…
Each payment acquirer has its own implementation specificities: some implement a 'payment with redirection' flow and others a 'direct payment flow'; sometimes the 'payment with redirection' flow is even implemented as a 'direct payment' flow through an iframe; one payment acquirer could support webhooks while another does not and relies on another mechanism to fetch payment status updates... It can be tricky to guess where to look in the code to determine how a payment acquirer is implemented. On top of that, the online payments ecosystem evolves at a fast pace due to competition, buyouts, and legislation enforcement. Acquirers are thus frequently migrated to new APIs that might differ in implementation from the previous API. To help figure out the *which*, *why*, *how*, and *when* of payment API implementations, a README.md file is added to the main directory of all payment acquirer modules. They can be browsed in human-readable format on GitHub. task-2374916 See also: - https://github.com/odoo/enterprise/pull/56182 Forward-Port-Of: odoo/odoo#155960 Forward-Port-Of: odoo/odoo#153016
The payment form displayed in the customer portal has been visually improved to provide a better user experience. This enhancement makes the payment process more intuitive and professional-looking for customers making purchases online.
Original PR description
Improve visual of payment form in customer portal task-3640114 backport of odoo/odoo#150919 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update improves security by preventing Odoo configuration files generated on Windows installations from being accidentally committed to version control. On Windows systems without a specified config file location, Odoo creates an odoo.conf file in the root directory containing sensitive password information. By adding this file to gitignore, we ensure that passwords and other sensitive configuration data are never exposed in repositories.
Original PR description
On Windows installations there is a odoo.conf file generated in the root directory containing a hashed admin password. This only happens in Windows installations where the config file location is not specified. The code responsible can be found here: https://github.com/odoo/odoo/blob/d2ccea9a292c02dc6f4cfdb960d22caa0fd98fd5/odoo/tools/config.py#L414 Forward-Port-Of: odoo/odoo#156099