Tuesday, July 2, 2019
5 changes · master
Enhancements to existing features
Survey answer forms now display which attempt a response represents, such as attempt 2 of 4. This helps staff understand a respondent's progress and retry history without extra investigation, while avoiding performance issues in broader list views.
Original PR description
Purpose ======= This commit adds the attempt number on the answer (= survey.user_input) form view. The attempt number is always relative to its "pool" of attempts and depends on the "invite_token" if specified. ex: Attempt n° 2 / 4 (where "4" is the attempts_limit of the related survey). This information is only displayed in the form view because it can't be computed in batch and would badly impact the performance of the list view. 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
Administrators in debug mode can now see a direct shortcut from a user profile to that user's available menus, including a count. This makes it easier to review or configure menu access, such as when preparing template users.
Original PR description
**Description of the issue/feature this PR addresses:** Adds a smart button with count to see Menus (in debug mode only). It can be useful, for example when creating template user. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Product attribute values are now shown with cleaner, less repetitive names in product setup and search results. This reduces visual clutter for users configuring product variants and makes selecting the right values easier.
Original PR description
Add comment on both methods to clarify their goal. Remove the unnecessary check. Indeed the `product.template.attribute.value` is not displayed during the variant set up of the product template so there is no point to check the context for it. Update the view to apply the context change also for the search result. Indeed the context change on the o2m itself didn't propagate so the attribute was displayed unnecessarily on the search result. 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
Sales quotes and orders created from a subscription upsell or renewal now show a message in the sales chatter linking back to the original subscription. This makes it easier for sales teams to understand the context of an order and quickly access the related subscription record.
Original PR description
Before this - There was no way to know a quote/so come from a upsell/renewal of the subscription. In this - Added chatter msg in Sale Order with link to Subscription. task-49017
Code cleanup and technical improvements
The VOIP phone-related code was reorganized to make future SMS and phone widget improvements easier to deliver. This is an internal cleanup with little immediate change for users, but it helps reduce complexity for upcoming enhancements.
Original PR description
This merge is mainly an enterprise adaptation of community PR https://github.com/odoo/odoo/pull/34516. See sub commits for more details.