Friday, January 25, 2019
11 changes · master
Enhancements to existing features
Event pages and registration flows have been redesigned to be clearer and easier to use, especially on mobile devices. The update introduces a card-based layout, cleaner navigation, and more flexible page options so businesses can better tailor event pages to their needs.
Original PR description
\* base, portal, website, website_event_sale, website_event_track - The previous event registration form was not clear on mobile - Review some layouts to match the new design general idea, using cards (see forum refactoring of #29235) - Use correct bootstrap components (like a menu instead of a breadcrumb on event pages) - Review options to be able to disable the left / right column and choose the exact options you want to appear in them task-1858034
Survey setup is clearer by separating who can access a survey from whether login is required. Survey links now use access tokens instead of visible IDs, making invitation-only surveys less discoverable and improving the signup-to-survey flow.
Original PR description
Purpose of this merge is to improve access mode and authentication management introduced at 9771fdfe8f658fd0f3c270173a3d19b614ec8997 . Purpose of this cleaning is to simplify options and make them clearer. Instead of a selection with 4 entries we propose to use two fields on survey model : * access_mode: everyone with a public link can access and answer; or only invited people; * login required: whether people have to login to answer or not; All main use cases are covered with combination of those two options. In this merge we also refine survey routes now using an access token defined on survey model instead of its ID. It allows to keep surveys somehow private especially for surveys on invitation only. Some fixes related to last changes are also done in this merge. Some improvements in survey templates are also provided to ease their update. This merge is linked to task ID 1932508 and PR #30508.
Creating a customer from an opportunity now carries over key contact and address details automatically, reducing manual entry and mistakes. The opportunity screen also shows clearer quotation and sales order counts, helping sales teams find the right records faster.
Original PR description
If the user is creating a res.partner from the partner_id m2o on crm.lead, prefill contact information from the opp in it (email, phone, mobile, street, street2, etc.). If 'contact_name' is set on…
If the user is creating a res.partner from the partner_id m2o on crm.lead,
prefill contact information from the opp in it
(email, phone, mobile, street, street2, etc.).
If 'contact_name' is set on crm.lead, the created res.partner should have:
> is_company = False
> name = contact_name (from crm.lead)
> company_name = company_name (from crm.lead)
If 'contact_name' is not set on crm.lead, the created res.partner should have:
> is_company = True
> name = company_name (from crm.lead)
various improvements and fixes:
- View quotations was incorrect
-> should be real quotation view and not SO view
- Cotation count was incorrect
-> Should only include Quotations with state='draft' or state='sent'
- SO button should be visible if number of SO > 0 and not the total amount
Task ID : https://www.odoo.com/web?#id=1908622&action=327&model=project.task&view_type=form&menu_id=4720
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prMobile users will no longer swipe between records in form views because that interaction was slow and less clear. Navigation now relies on the pager, while swipe remains available for tabs only when they do not fit on one screen.
Original PR description
The swipe between the form view is taking too long to load, and the pager is a more clean option to switch between form view. Moreover, the swipe on tabs is not clear anymore. - Deactivate swipe between form view - Swipe should only be available on tabs when tabs are too long to fit in one screen. Related task: 1924764
Event-related website pages have been redesigned to better match Odoo’s updated visual style. The changes improve the look and consistency of event, ticketing, and session pages, making them clearer and more polished for visitors.
Original PR description
* base, portal, website, website_event_track
Purchase orders now calculate received quantities for kit products using the same logic already used for sales deliveries. This gives teams a clearer view of what has actually been received when kits are bought, reducing manual checks and inventory confusion.
Original PR description
This PR generalize the method made for computing the quantity delivered in a sale order in order to be used for the quantity received of a kit in a purchase order. TaskID: 1929518
Belgian payroll fleet calculations now use the latest legal values for CO2 tax and taxable benefit calculations. The fleet module also recognizes LPG as a fuel type, improving accuracy for companies managing vehicles and payroll obligations.
Original PR description
Specification ============= - Adapt the formula used in the code with the current legal value. - Add the LPG fuel type in standard fleet module. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Manufacturing users can now set a start date when planning work orders, so production can be scheduled or rescheduled for the first available time after that date. Unplanning now removes linked work orders and is blocked once work has started, helping prevent accidental changes to active production.
Original PR description
Add possibility to schedule Work Orders in the future or re-schedule them. - Move some code from `mrp_workorder` in Enterprise to `mrp` in Community (odoo/enterprise#3420) - Add a test for the planning of WO - Add a field on Work Orders: Start Date. The WO needs to be planned at the first available after this time. - Unplan deletes all linked WO and cannot be called if WO have already started -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Belgian payroll now includes dedicated salary structures for double holiday pay and 13th-month payments. This makes these common compensation elements easier to calculate and report accurately, while replacing earlier estimated values in the salary package setup.
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
Follow-up reports sent by post now leave a clear note in the customer chatter, making it easier to track what was sent. The process also checks for invalid addresses before sending, helping teams avoid failed letters and resolve delivery issues sooner.
Original PR description
Add message in chatter when sending a followup report with Snailmail to improve failed letters usability Linked to PR #29685
The Belgian salary package configurator now uses values from the dedicated salary structure for double holiday pay and thirteenth month calculations instead of relying on idealized estimates. This should make salary package information more accurate for employees and HR teams, with added tests to help prevent regressions.