Daily updates from Odoo
Monday, June 3, 2019
16 changes · master
New functionality added to Odoo
CRM users can now enrich leads using the customer email domain, automatically filling in missing company and contact details when data is available. The feature helps sales teams save time on research, logs results in the lead chatter, and supports enrichment from both individual lead forms and list views.
Original PR description
Purpose: Allow the user to enrich a lead based on the domain of the email adress of the client. Following fields will be populated if found using clearbit and if they are not yet populated: -…
Purpose:
Allow the user to enrich a lead based on the domain of the email adress of the client.
Following fields will be populated if found using clearbit and if they are not yet populated:
- description
- partner_name
- reveal_id
- website
- street, street2, zip, city, country_id, state_id
- phone (using the first number found in clearbit)
- mobile (using the second number found in clearbit, else the same as phone)
A message will also be logged in the chatter.
If no data is found using clearbit no credit is used and a message will be logged,
If the user has no credits he will be redirected to buy credits for the service.
It is possible to enrich using a new secundary button on in the header of a lead,
or using the 'enrich' action in listview.
This commit includes:
- a new botton in leads
- a new action in listview
- a new message tempalate to log when no data is found in clearbit
- additions to crm_lead to be able to enrich
TaskId: 1931856Enhancements to existing features
The portal opportunity page now keeps stage labels on a single line by adjusting their placement based on available space. This makes opportunity cards cleaner and easier to read, especially when many stages are shown.
Original PR description
Description of the issue/feature this PR addresses: Portal opportunity stages Current behavior before PR: Stages are in column next to Opportunity title. When there are too many, the stages don't remain on one line --> ugly Desired behavior after PR is merged: Stages should appear on one line : under Opportunity title if element is wider than 440px, next to it if element is under said width. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Point of Sale sessions are now easier to navigate, with direct access to related orders and a more prominent Sessions menu. New PoS configurations also get better default stock operation settings per warehouse, reducing manual setup and improving inventory consistency.
Original PR description
**Description of the issue/feature this PR addresses** 1. Add a stat button on PoS session forms linking to the details of the orders. 2. Put the 'Sessions' menu item in first position of the 'Orders' menu. 3. Set 'PoS Orders' as the default operation type (picking type) for newly created PoS configs. **Task ID** : 1970513 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
CRM lead generation now uses industry categories instead of technology tags, aligning it with the broader Lead Generation experience. The available tags have also been reduced to keep choices more relevant and easier to use.
Original PR description
In order to be consistent with Lead Generation, we need to use Industry tags instead of technology tags. Task ID: 1941555
Customers can now adjust their rating and add written comments after clicking a rating smiley in an email. The feedback experience has also been refreshed and moved into the portal experience, reducing website-specific dependencies and making it more consistent for portal users.
Original PR description
TASK: https://www.odoo.com/web?#id=1936849&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720 PAD: https://pad.odoo.com/p/r.fc7aec1f1cb5bd15d9c7b4a7cb055012 - The page where you land after clicking on the smiley in the e-mail for rating, now you can also change smiley and can write comment as well. - UI of the feedback page and the page after submitting the feedback in improved. - 'website_rating' is now 'portal_rating'. - There is no dependency of 'website_mail'. - 'portal_rating' is dependent on 'portal' and 'rating'.
Odoo Studio users can now click the image shown at the bottom of a kanban card while editing a view. This makes it possible to remove or manage that image directly, reducing frustration when customizing kanban layouts.
Original PR description
Task: https://www.odoo.com/web?debug#id=1997542&action=327&model=project.task&view_type=form&menu_id=4720 pad: https://pad.odoo.com/p/r.8e1327f486c6f5ce42a92c84790cdf42 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
In Odoo Studio's report editor, selecting or expanding an item in the sidebar now selects the matching element in the report preview. This makes it clearer which part of the report is being edited and reduces confusion when changing report properties.
Original PR description
Task : https://www.odoo.com/web#id=1986834&action=333&active_id=1519&model=project.task&view_type=form&menu_id=4720 Pad : https://pad.odoo.com/p/r.4928518afca2661d89516ae2e4e01bf5
Studio now visually dims areas where a dragged search view component cannot be dropped. This helps users understand valid placement options immediately and reduces trial and error while customizing search views.
Original PR description
Currently, when we drag a component in search view, it can not be dropped everywhere. For example, a 'filter' component can not be dropped inside 'Group by' and 'Autocompletion Fields' section. But user can not see any visual indication about which component can be dropped where. This commit indicates 'undroppable' zone by adding 'text-muted' class to such tables, as soon as the draggable component touches the view. task-1978762
Gantt views can now use date and datetime fields to apply visual decorations, similar to list views. This helps teams highlight records based on timing rules, making schedules easier to scan and prioritize.
Original PR description
Just like a List view, you can use `date` and `datetime` type field to evaluate `decoration` attributes.
Resolved issues and error corrections
This update reduces false alarms in inventory-related automated checks by allowing a tiny timing difference when comparing dates. It helps keep development and release validation stable without changing how users work with inventory.
Original PR description
The comparison of two datetimes is never exactly perfect. This commit adds one second tolerance in those two tests to ensure any false positive result is avoided 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
The stock demo data setup now starts inventory using the correct process. This prevents errors when the stock module is reinstalled with demo data, making setup and testing more reliable.
Original PR description
The demo data inventory didn't call the right method (`action_start` instead of `_action_start`), so, if user tried to re-install stock module, the `ensure_once` check will fail when reinstall the demo data.
Payslip reports now keep the correct amounts for work days instead of showing them as zero. The report also avoids repeating the work days name, making payroll documents clearer for employees and payroll teams.
IoT action requests now show a more accurate warning when an error occurs, including cases related to SSL issues. This helps users and support teams understand the problem faster instead of seeing only a generic connection failure message.
Original PR description
Before this commit when we make a action request and that the answer is an error we only return a connection problem message. Task: 1973942
This fix prevents errors when processing payments without an active payment line and ensures receipt content is placed in the correct section for printing. It helps reduce failed or incomplete ticket printing for point-of-sale users using IoT devices.
Original PR description
We check if a selected_paymentline is not undefined before retrieving the status We replace the class name pos-sale-ticket by after-footer. Because this class don't exist in XmlReceipt
Code cleanup and technical improvements
Website-related scripts in Enterprise modules are now aligned with a platform change that delays JavaScript loading until it is needed. This helps pages become usable sooner while keeping existing document and web client behavior unchanged.
Original PR description
See https://github.com/odoo/odoo/pull/32181
Miscellaneous changes
This pull request appears to merge the latest master branch changes into the repository. No specific business feature, bug fix, or affected Odoo module is described, so the impact is likely limited to keeping code aligned and up to date.
Original PR description
Master 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