Tuesday, March 29, 2022
13 changes · master
Enhancements to existing features
The Belgian reports module now uses the full model name instead of an abbreviation in section 170/4. This makes the report easier to understand and reduces ambiguity for users reviewing Belgian financial reporting details.
Original PR description
Use full model instead of abbreviated model for section 170/4 [task-2511879](https://www.odoo.com/web#id=2511879&model=project.task)
This update aligns multiple Enterprise apps with Odoo's revised page and report rendering system. It is an internal compatibility improvement that helps keep accounting, payroll, HR, appointments, and localization features working consistently with the core platform changes.
Original PR description
Spreadsheet-related functions now must use valid names made only of letters, numbers, and dots. This removes an inconsistent naming shortcut and helps keep formula behavior predictable for users and maintainers.
Original PR description
Currently, one can add a new function to the functionRegistry by
providing a key containing an underscore and it will magically be
adapted so the actual key contains a dot (.) instead.
There a two issues with this:
1. The existence of this feature is only justified by the way we
organized our functions files: We export the function under some
variable and use those to populate the registry. Since variables
can not contain dots, we used underscore. The functionRegistry
should not be aware of such a specificity.
2. The goal is to propose a generic formula name, only containing
dots and alphanumerical characters. However, the current
implementation will only replace the first occurence of
an underscore, basically defeating the purpose.
This commit tries to address both issues by forcing a proper format of
alphanumeric and dot format to the keys of the registry.
Task 2715250The cohort reporting interface has been tidied up by replacing custom styling with standard layout and formatting helpers. This makes the screen easier to maintain while keeping the user experience consistent.
Original PR description
The goal of this commit is to reduce the CSS using the Bootstrap utility's class. Mini summary: * avoid using unit when the value is 0 (e.g. 0px) * text-align: center -> text-center * vertical-align: middle -> align-middle * margin: ? -> m-? * padding: ? -> p-? * border-radius: ? -> rounded * font-weight: ? -> font-weight-bold (for bold text) * border-?: ? -> table-bordered (border for table) * height 100% = top 0 and bottom 0 in position absolute * remove unnecessary comment Task ID: 2704984 Task ID: 2731616
Resolved issues and error corrections
This fixes Mexican electronic invoices so discounts that round to zero are no longer shown. It prevents tiny rounding amounts from appearing as a discount, making invoice documents clearer and more accurate for customers.
Code cleanup and technical improvements
The payment setup guidance for online sales has been relocated into the website sales dashboard, where users actually encounter it. This is a cleanup change that keeps related dashboard code together and should not change day-to-day behavior.
Original PR description
This PR cleans code following the stripe connect follow-up PR. The payment onboarding step in the website sale dashboard is moved where it's actually used. Follow-up task-2685160 References --------------- - Community: odoo/odoo#84789 - https://github.com/odoo/upgrade/pull/3256
Miscellaneous changes
Only play the incoming call ringtone in the master tab, avoiding to play several times at once the ringtone when multiple tabs are open. Task-2803370 Forward-Port-Of: odoo/enterprise#25628
Original PR description
Only play the incoming call ringtone in the master tab, avoiding to play several times at once the ringtone when multiple tabs are open. Task-2803370 Forward-Port-Of: odoo/enterprise#25628
see community https://github.com/odoo/odoo/pull/85110
The timesheet forecasting sales tests were updated to reflect corrected employee company and timezone handling. This helps keep automated checks reliable after related platform changes, with no expected direct impact on daily users.
Original PR description
Due to the changes in the community PR, the resource of the employee is now created directly with the right company (the one provided in create values, or the environment company, as specified in the default field value). This means that now, the resource.resource create receives the correct company and correctly extrapolates the calendar and tz (if not provided). Previously, when the company/user/calendar/tz were not provided, the resource tz default used the context/user tz/'UTC'. Which means that the employees created in the sale_timesheet test common (including manager_company_B used in the current test) had conflicting resource and resource calendar tzs, aka 'UTC' for the resource (last default value) and 'Europe/Brussels' for the resource calendar tz, leading to the previous result in the test values. Now that the timezone are the same, the test must be adapted accordingly. COM PR: https://github.com/odoo/odoo/pull/85601
1. Create a Fiscal Position that automatically applies for certain Vendors (eg: set for US, and Zip Codes in the 9xxxx range) 1. Open Documents App. 2. Upload/select a document in Finance workspace. (eg: Invoice from Azure Interior). 3. Add the associated Vendor. 4. Select the "Create Bill" Action. Fiscal position will be missing from the new vendor bill opw-2765778 Forward-Port-Of: odoo/enterprise#25309 Forward-Port-Of: odoo/enterprise#24788
Original PR description
1. Create a Fiscal Position that automatically applies for certain Vendors (eg: set for US, and Zip Codes in the 9xxxx range) 1. Open Documents App. 2. Upload/select a document in Finance workspace. (eg: Invoice from Azure Interior). 3. Add the associated Vendor. 4. Select the "Create Bill" Action. Fiscal position will be missing from the new vendor bill opw-2765778 Forward-Port-Of: odoo/enterprise#25309 Forward-Port-Of: odoo/enterprise#24788
…ecific Community-PR: https://github.com/odoo/odoo/pull/83752 Enterprise-PR: https://github.com/odoo/enterprise/pull/23891 task-id: 2751825 Forward-Port-Of: odoo/enterprise#24837 Forward-Port-Of: odoo/enterprise#23891
Original PR description
…ecific Community-PR: https://github.com/odoo/odoo/pull/83752 Enterprise-PR: https://github.com/odoo/enterprise/pull/23891 task-id: 2751825 Forward-Port-Of: odoo/enterprise#24837 Forward-Port-Of: odoo/enterprise#23891
When we click multiple times on the submit button, an appointment can be created a second time before the user can be redirected to the confirmed paged. In this case, the appointment is created but the user is redirected to the slot selection because it says that we already have an event planned (the appointment which has just been created) when the controller try to create a second one with the mutli-click. To avoid this we use the automatic system making handlers promise-ready (see ma
Original PR description
When we click multiple times on the submit button, an appointment can be created a second time before the user can be redirected to the confirmed paged. In this case, the appointment is created but the user is redirected to the slot selection because it says that we already have an event planned (the appointment which has just been created) when the controller try to create a second one with the mutli-click. To avoid this we use the automatic system making handlers promise-ready (see makeButtonHandler() function for more info) and return a Promise that is never resolved to prevent sending the form multiple times. task-2750701 Forward-Port-Of: odoo/enterprise#25646 Forward-Port-Of: odoo/enterprise#23975
Write and read rules for posts for social users where defined in two contradicting ways. This commits cleans these rules in favor of the choice introduced for v15.1 in commit 79302153: Users should be allowed to create/read/edit any post and delete only their own, unless they are managers. Task-2701601 Forward-Port-Of: odoo/enterprise#25034
Original PR description
Write and read rules for posts for social users where defined in two contradicting ways. This commits cleans these rules in favor of the choice introduced for v15.1 in commit 79302153: Users should be allowed to create/read/edit any post and delete only their own, unless they are managers. Task-2701601 Forward-Port-Of: odoo/enterprise#25034
When the default transaction code is being used the CBS export on the intrastat report, an error occurs. The reason is that the value gathered from the _fill_missing_values function, which was implemented on the CBS export function to bring it in line with the content of the report in a previous fix 3f1c8ce, is an integer, whereas the .join in the export function expects a string. Forward-Port-Of: odoo/enterprise#25649
Original PR description
When the default transaction code is being used the CBS export on the intrastat report, an error occurs. The reason is that the value gathered from the _fill_missing_values function, which was implemented on the CBS export function to bring it in line with the content of the report in a previous fix 3f1c8ce, is an integer, whereas the .join in the export function expects a string. Forward-Port-Of: odoo/enterprise#25649