Odoo Changelog — 2024-02-29

Thursday, February 29, 2024

3 changes · master

Improvements(3)

Enhancements to existing features

Remove activity ids from chatter arch

Enterprisemasteraccount_accountantaccount_assetaccount_batch_paymentaccount_budgetaccount_followupaccount_online_synchronizationaccount_sepa_direct_debitapprovalsdocumentshelpdeskhr_appraisalhr_contract_salaryhr_payrollhr_referrall10n_in_reports_gstrl10n_uk_bacs

This update simplifies how activity information is handled in form chatter areas across many Odoo apps. It removes unnecessary activity identifiers from screen definitions and prepares view data to carry extra model information when needed, helping keep the interface infrastructure cleaner and easier to maintain.

Original PR description

**Before this PR:**
- Each model in models from `get_views` return data, only contains a dict of fields. The structure of models is like:

```py
models: {
    resModel1: {contains resModel1 fields},
    resModel2: {contains resModel2 fields},
    ...
}
```

**After this PR:**
- Adding `fields` in form of `key: value` to each model in `get_views`, makes it possible to add extra data about model beside `fields` if it's needed.

```py
models: {
    resModel1: {
      fields: {contains resModel1 fields},
      extra_data: ...
    },
    resModel2: {
      fields: {contains resModel2 fields}
      extra_data: ...
    },
    ...
}
```
- All the `activity_ids` (descendants of `oe_chatter`) are removed from the view arch

[Related Odoo PR](https://github.com/odoo/odoo/pull/154710)

#chatter#activities#views#maintenance

[IMP] hr_recruitment_reports: ux

PR #53416

Enterprisemasterhr_recruitment_reportsMEDIUM

Recruitment reports now open the related applicant record directly instead of showing a generic report form. This makes it easier for recruiters to review candidate details and move through the report with fields arranged more logically.

Original PR description

This commit add a form view to replace the auto-generated one. The purpose is to have a better UX for the user to make them able to go to the applicant and order the fields in a way that make more sense to them to enhance the navigation experience.

task-3613046

#recruitment#reports#user-experience#navigation

[IMP] hr_payroll: filter salary attachments by selected companies

PR #54817

Enterprisemasterhr_payrollMEDIUM

Salary attachments can now only be created for employees who belong to the companies currently selected in the multi-company view. This helps prevent payroll records from being created for the wrong company context and keeps payroll work focused on the relevant companies.

Original PR description

Prevent the creation of salary attachments for employees working in companies not selected in the multi-company widget. This enhancement ensures that salary attachments are relevant and specific to the currently focused companies.

Task-3693473

#payroll#multi-company#salary attachments

**Before this PR:** - Each model in models from `get_views` return data, only contains a dict of fields. The structure of models is like: ```py models: { resModel1: {contains resModel1 fields}, resModel2: {contains resModel2 fields}, ... } ``` **After this PR:** - Adding `fields` in form of `key: value` to each model in `get_views`, makes it possible to add extra data about model beside `fields` if it's needed. ```py models: { resModel1: { fields: {contains resModel1 fields}, extra_data: ... }, resModel2: { fields: {contains resModel2 fields} extra_data: ... }, ... } ``` - All the `activity_ids` (descendants of `oe_chatter`) are removed from the view arch [Related Odoo PR](https://github.com/odoo/odoo/pull/154710)

This commit add a form view to replace the auto-generated one. The purpose is to have a better UX for the user to make them able to go to the applicant and order the fields in a way that make more sense to them to enhance the navigation experience. task-3613046

Prevent the creation of salary attachments for employees working in companies not selected in the multi-company widget. This enhancement ensures that salary attachments are relevant and specific to the currently focused companies. Task-3693473