Tuesday, July 22, 2025
5 changes · 18.0
Enhancements to existing features
Employees can now manually check in and check out from attendance kiosk mode when working across multiple companies. The kiosk also limits manual employee selection to the companies the user is allowed to access, making attendance tracking more usable and accurate in multi-company setups.
Original PR description
Description of the issue/feature this PR addresses: Current behavior before PR: Manual check-in / check-out on attendance kiosk mode is not allowed Desired behavior after PR is merged: - Give possibility to user to make check-in / check-out on attendance kiosk mode - Display employees for allowed company on manual selection mode in the kiosk
Users can now resend modified vendor bills for Bizkaia Batuz reporting without cancelling and recreating the bill first. This simplifies corrections for customers and auditors while keeping the previous valid submission if the resend is rejected.
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
This update allows employees to manually check in and check out from attendance kiosk mode in multi-company setups. It also limits the employee list in manual selection mode to companies the user is allowed to access, making kiosk use clearer and safer for organizations with multiple companies.
Original PR description
Description of the issue/feature this PR addresses: Current behavior before PR: Manual check-in / check-out on attendance kiosk mode is not allowed Desired behavior after PR is merged: - Give possibility to user to make check-in / check-out on attendance kiosk mode - Display employees for allowed company on manual selection mode in the kiosk --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This change makes the contact form easier to adapt for different business needs, such as new contact categories or multi-level company structures. Existing behavior is intended to stay the same, while partners and implementers gain more flexibility to tailor how contacts, addresses, and parent-child relationships appear.
Original PR description
Description of the issue/feature this PR addresses: The current contact UI is partly inconsistent regarding the child/parent behavior and also it is not flexible extensible regarding new contact…
Description of the issue/feature this PR addresses: The current contact UI is partly inconsistent regarding the child/parent behavior and also it is not flexible extensible regarding new contact types like "Home office Contact", which is a "Contact" but has a different Address, and also an "Delivery Address" is in my opinion not an individual, but neigther a company. Therefore I suggest to de-couple the different topics and add new variables. These variables can be customized by overwriting the "_compute_contact_type" method according to the users needs. e.g. you could add a new individual type "home office contact" which is an individual, but also has an editable address. By changing can_be_child to True on Company contacts, you could create multi-level company structures. In this patch, the current behavior is not changed, but gives better possibilities for customizations. Current behavior before PR: The forms are hardly customizable regarding new contact types. Desired behavior after PR is merged: The UI can be more customizable and using is_address_readonly, is_individual, can_be_parent and can_be_child instead of linking the type directly. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The expiration message shown in the Enterprise home menu now better reflects the updated timing, where expiration is tied to a date 15 days after the next invoice date. This helps customers understand when action is needed and encourages earlier payment instead of waiting until the last minute.
Original PR description
Previously, the database expiration date was set to the same date as the expiration field, which is now defined as 15 days after the next invoice date. Issue: Users tend to wait until the last minute to pay. This improvement aims to better handle expiration timing and encourage timely payments. TaskID: 4384877