Tuesday, September 28, 2021
5 changes · master
Enhancements to existing features
Survey administrators can now view and edit the completion description field in the survey backend. This restores control over the message or description shown after a survey is completed, helping teams better tailor respondent follow-up communication.
Original PR description
Description of the issue/feature this PR addresses: Add (back) the edition of description_done field on surveys Current behavior before PR: description_done field is not displayed on backend and therefore user cannot fill it. Desired behavior after PR is merged: description_done field is displayed to / editable by user -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Point of Sale cash opening and session closing are now managed directly in the POS interface, giving staff guided cash counting and a clearer overview of orders, payments, and cash movements. Cash control is automatically enabled when cash payments are used, improving consistency and reducing manual configuration for managers.
Original PR description
The opening cash control has been refactored and the closing of the session is now happening in the POS UI. This also leads to a cash control in the UI during the closing. The advanced cash control…
The opening cash control has been refactored and the closing of the session is now happening in the POS UI. This also leads to a cash control in the UI during the closing. The advanced cash control is no longer a setting to activate in the config by the user but a computed field based on the presence of a cash payment method. We force the user to always have it now. The opening cash control has been revamped with the addition of a new money calculator (MoneyDetails) allowing the user to easily compute how much money he has based on his bills. The closing control has been converted into a popup which allows the users to get an overview of his session details (about orders, payments, payment methods, cash moves, ...). If the cash_control has been set to True, the user still needs to count his money by introducing it or using the new calculator. When trying to close the session, if it fails, depending on the error the user get, he can be redirected to the back end to manually close the session. At this point, the user is not able to open the POS UI. (In order to fully bring the closing of the session in the front end, all the error handlings need to be brought to the front end as well which takes a lot more time.) Rescue session can only be closed through the back end and the closing cash control is automatically being computed without the user's involvement. This avoid any cash profit/loss in the journals. task-2456424 V15 backport PR https://github.com/odoo/odoo/pull/76333
The SMS list now shows message statuses more clearly with simple color badges and no full-row highlighting. Users can also send, cancel, or retry SMS messages directly from the list, making day-to-day message handling faster and easier.
Original PR description
Generic UX improvements: - better visualization of the status of the SMS - buttons to directly retry, send or cancel an SMS from the list view * move the 'sms status' field to the right of the 'error…
Generic UX improvements:
- better visualization of the status of the SMS
- buttons to directly retry, send or cancel an SMS from the list view
* move the 'sms status' field to the right of the 'error code' one
* use the badge widget for the status
* remove the colors on the whole lines
* add an 'fa-paper-plane send now' button
only visible if the status is 'in queue'
clicking on this button should effectively send the SMS
* add an 'fa-times-circle cancel' button
only visible if the status is 'in queue' or 'error'
clicking on this button should switch the sms to the 'canceled' state
* add an 'fa-repeat retry' button
only visible if the status is 'error' or 'canceled'
clicking on this button should switch the sms to the 'in queue' state
taskid: 2535005
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-prCRM lead enrichment now runs shortly after new leads are created by default, helping sales teams receive enriched lead details sooner. The update also improves CRM form labels, keeps manual enrichment available, and replaces noisy credit-shortage chatter messages with clearer on-screen notifications.
Original PR description
PURPOSE Cleanup automatic enrichment of leads. SPECIFICATIONS Right now, when we choose to automatically enrich the leads from CRM settings, it activates a cron to periodically enrich the leads using…
PURPOSE Cleanup automatic enrichment of leads. SPECIFICATIONS Right now, when we choose to automatically enrich the leads from CRM settings, it activates a cron to periodically enrich the leads using IAP service. This commit improves the behavior by enriching the leads after the records creation using cron trigger. That way it is done nearly after creation and user gets enrich information sooner. To make it clear to users, the description for 'auto' mode is improved to 'Enrich all leads on creation'. Also, now we select 'auto' mode by default instead of 'manual', and display 'Enrich' button on form view irrespective of the selected mode (if lead meets certain conditions) unlike before. Rest of the behavior is still same as before. For example, we still have server action which can enrich the selected leads in batch, which is useful if there are existing leads before we enable 'Lead Enrichment' feature. SIDE SPECIFICATIONS Improve lead / opportunity marketing information display on form view. Send html toast notifications when running out of IAP credits for enrich. Fix some corner cases for lead enrich (involving probability, email). LINKS Task-2269743
Users can now set access more precisely for individual documents, helping teams keep sensitive files limited to the right people. Documents and shared links no longer always need to belong to a folder, making document organization and sharing more flexible.
Original PR description
This commit adds a more granular option to control the access to documents. `folder_id` is no longer a required field on `documents.document` and on `documents.share`. task-2257514