Daily updates from Odoo
Navigate
Branch
Tuesday, October 30, 2018
11 changes
New functionality added to Odoo
Users can now create a signature request for several recipients and guide each person through signing directly, without requiring them to open an email link. Once everyone has signed, the completed document is still emailed to the relevant participants, and a related field-name issue in Sign was corrected.
Original PR description
1/ Allow multiple signers to sign without emails ==================================== Purpose ------------ It's already possible to send a signature request and to sign directly if you're one of the signers. It's not possible to make a signature request to 2 people (Customer-salesman for example) and to make both people sign without clicking on the email the customer received. Specification ------------------- Add a new feature "Sign Directly" in which you choose the recipients, but intead of sending the emails, it opens the signature request for the 1rst signer, then opens it again for the second, etc. And finally when everyone has signed the document, send the result by email to the customer/salesman. 2/ Fix field renaming introduced in 50bb012 ==================================== The field type has been renamed into item_type, but not everywhere.. Fix the remaining occurence. TaskID: 1891958
Enhancements to existing features
The user-defined defaults form now uses the standard Odoo form layout, making it cleaner and easier to read. This brings the screen in line with the look and feel of other Odoo forms for a more consistent user experience.
Original PR description
Description of the issue/feature this PR addresses: Create a neat form view for this menu Current behavior before PR: The formview has no `<sheet>` which results in a not really beautiful form view. Desired behavior after PR is merged: A great looking form view like most views in Odoo. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The Lunch app’s form views now include clearer structural sections, making them easier to maintain and adapt. This supports future customization work without changing the visible business workflow for users.
Original PR description
Description of the issue/feature this PR addresses: Add `<sheet>` to form views and add name to `<group>` elements. Current behavior before PR: There are no `<sheet>` tags defined on the form views and the hard to `xpath` elements have no names set. Desired behavior after PR is merged: Set `name` elements on most critical view parts to `xpath` and add `<sheet>` to missing form views. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The documentation now uses a more practical, real-world example to explain model inheritance delegation. This should make the concept easier for readers to understand and apply, reducing confusion for developers learning the framework.
Original PR description
The model inheritance concept was explained with abstract example which is often confusing. Change to a real world example that will be better understood.
This update improves how Odoo processes groups of related records by handling most operations together instead of one by one. Businesses should see better performance in screens and workflows that create or modify many linked items at once, with no expected change in day-to-day behavior.
Original PR description
For performance reasons, do almost all command operations in batch.
Recruitment form screens are updated with a more consistent structure so they are easier to maintain and customize. This helps future changes to hiring workflows be applied more reliably without changing what end users do today.
Original PR description
Description of the issue/feature this PR addresses: Add `<sheet>` to form views and add name to `<group>` elements. Current behavior before PR: There are no `<sheet>` tags defined on the form views and the hard to `xpath` elements have no names set. Desired behavior after PR is merged: Set `name` elements on most critical view parts to `xpath` and add `<sheet>` to missing form views. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The budgetary position form has been updated to use a clearer page structure and named sections. This makes the form easier to maintain and customize without changing what business users see or do.
Original PR description
Description of the issue/feature this PR addresses: Add `<sheet>` to form view and add name to `<group>` element. Current behavior before PR: There are no `<sheet>` tags defined on the form view and it is hard to `xpath` as elements have no names set. Desired behavior after PR is merged: Set `name` elements on most critical view parts to `xpath` and add `<sheet>` to missing form view. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The analytic defaults form layout is updated to make it easier to customize and maintain. This helps future changes or partner-specific adjustments be applied more reliably without changing business behavior.
Original PR description
Description of the issue/feature this PR addresses: Add `<sheet>` to form view and add name to `<group>` element. Current behavior before PR: There are no `<sheet>` tags defined on the form view and it is hard to `xpath` as elements have no names set. Desired behavior after PR is merged: Set `name` elements on most critical view parts to `xpath` and add `<sheet>` to missing form view. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The accounting group form now uses the standard form layout container. This makes the screen more consistent with other Odoo forms and helps ensure a cleaner user experience.
Original PR description
Description of the issue/feature this PR addresses: Not perfectly created view. Current behavior before PR: The form views have no `<sheet>` set. Desired behavior after PR is merged: The form views have a `<sheet>` set. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Code cleanup and technical improvements
This change reorganizes the website editor code that activates snippet editing tools. It should make the editor easier to maintain and reduce the risk of future issues, without changing day-to-day behavior for users.
Purchase order lines now calculate received quantities using the same approach as sales deliveries. This makes receipt tracking more consistent across purchases, stock, and manufacturing flows, and easier to adapt for future business needs.
Original PR description
The received quantity on Purchase Order line can be compared to the delivered qty on Sales Order line. It is now time for both to share the same mecanism (introduced in 3bf8a62e0dd99f7dad42718f895abf4fd53f996f). This commit sets `qty_received` as a computed field. The value can be computed based on - manual value; for services (all the time), and consummable product when stock is not install. - stock moves; for stockable and consummable products when stock is installed. This is now easier to extend the way the received quantity need to be computed (like in sale). Task #1850689 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