Daily updates from Odoo
Monday, March 11, 2024
6 changes · master
Enhancements to existing features
This update adapts many Enterprise apps to Odoo's new path-based web navigation. It makes default app pages and internal links work more reliably with the updated web client routing, reducing broken or inconsistent navigation after the platform change.
Original PR description
*: account_consolidation, appointment, approvals, data_merge, documents, documents_spreadsheet, frontdesk, helpdesk, hr_appraisal, hr_payroll, hr_referral, industry_fsm, industry_fsm_sale, iot,…
*: account_consolidation, appointment, approvals, data_merge, documents, documents_spreadsheet, frontdesk, helpdesk, hr_appraisal, hr_payroll, hr_referral, industry_fsm, industry_fsm_sale, iot, knowledge, marketing_automation, marketing_automation_crm, mrp_plm, mrp_workorder, quality_control, quality_mrp_workorder, room, sale_renting, sale_subscription, sign, social, social_youtube, spreadsheet_edition, stock_barcode, timesheet_grid, web_enterprise, web_mobile, web_studio, whatsapp The corresponding community commit overhauls the client-side routing in the web client to use path-based routing. This commit adapts some things in enterprise to benefit from this new feature. Notably it: - adds the "path" field on the default action for most apps - fixes some urls to start with a "/", these relative urls will no longer work since the path can contain more than one segment task-3557575 Co-authored-by: Samuel Degueldre <sad@odoo.com> Community: https://github.com/odoo/odoo/pull/142007
The India payroll payment advice screens have been made easier to use by reorganizing list fields, simplifying the name input, and highlighting the main creation action. This helps payroll users create and review payment advice more quickly and with less confusion.
Original PR description
We have done the following points: ----------------- - Rearrange the fields on the advice list view. - Remove the name title and add a placeholder. - Make the primary advice creation button. task-3679450
This update removes obsolete internal module markers from JavaScript files in accounting-related frontend code and tests. It does not change product behavior, but keeps the codebase cleaner and easier to maintain.
Original PR description
As the /* odoo-module */ statement isn't required anymore in both `static/src` and `static/tests` folders we can remove them.
Users can no longer create new company records directly from selected Planning and Helpdesk screens. This helps prevent accidental or duplicate company setup by requiring company creation through the proper process.
Original PR description
Disable on the fly creation for companies in some views: - `planning.slot.form`: Planning > List View > View Button - `helpdesk.team.form`: Helpdesk > Configuration > Helpdesk Teams > New - `resource.resource.tree`: Planing > Configuration > Materials task-3507965
Room booking notifications now include the specific room they relate to. This prevents booking pages for different rooms opened at the same time from reacting to each other’s updates, reducing inconsistent room booking displays.
Original PR description
Purpose: -------- The bus service uses a single websocket connection that is shared across multiple tabs. Therefore, sending a notification to one tab actually sends it to every tab. Currently, the notification type is the same regardless of which room sends it. Therefore if 2 (or more) different room frontend views are opened at the same time, they will both handle the same notification, even though it was only concerning one of the rooms, leading to inconsistent states. This commit adds the room id in the bus notifications types. This allows for the roomBookingView component to only listen for the notifications intended for its room. Task-3698135
The calendar event form now hides the appointment type field when it is not already set. This encourages users to configure appointment details through the dedicated Appointment Types flow, helping avoid confusing or inconsistent event setup.
Original PR description
While creating a calendar event record, different field duration, reminders, etc are expected to be filled with values **(when we select appointment type in the form view)** same manner as we create appointment type records via the front end. It's more effective to fill such field values directly from the Appointment Types (via the front end). so the appointment_type_id field is hidden when we create a calendar event record via form view. Task-3768152