Monday, March 4, 2024
3 changes
1 change
Enhancements to existing features
This change lets country-specific localization and payroll demo data reuse the same demo company instead of creating duplicate companies. It simplifies demo environments and reduces the need for extra bridge modules just to align sample data across related apps.
Original PR description
The use case is the following: l10n_xx (usually depending on account) creates a company demo data l10n_xx_hr_payroll (not depending on account) creates another company The goal is to allow defining the data to a foreign module (obvioulsy in the common dependencies) like "base", so that each module can easily define the same company and use it without having the create another bridge module that contains only demo data. TaskID: 3714759
2 changes
Enhancements to existing features
A README file has been added to the SEPA Direct Debit payment module to document how the payment integration works, including technical implementation details. This helps users and developers understand the payment flow and makes it easier to maintain the module as payment standards evolve.
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/odoo/pull/153016 Forward-Port-Of: odoo/enterprise#57842 Forward-Port-Of: odoo/enterprise#56182
This update makes course sections more visually distinct from regular content by increasing their font weight in the backend interface. This helps instructors and administrators better organize and navigate course materials by making section headers stand out more clearly.
Original PR description
Purpose ======= Increase the bold of the sections in back end to better differentiate them from the content. Specifications ============== Adding !important next to the css bold style (value = 700) applied on the sections to make sure it takes the priority over the default list view sections "fw-bold" class (value = 500). Task-3759152 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr