Friday, October 29, 2021
7 changes · master
Enhancements to existing features
This update adds an internal test model that combines phone/SMS messaging with activity management. It helps teams validate future activity-related features more reliably, especially where phone numbers, SMS, VoIP, or document workflows interact.
Original PR description
Purpose is to ease future new tests about activities management involving phone numbers and SMS sending. Task-2657021
Purchase order lines now provide access to past purchase pricing so buyers can compare current prices and discounts with previous orders. This helps teams validate supplier pricing more easily, while hiding unavailable action buttons until a line is saved.
Original PR description
Sometimes it's difficult to track the price of a product, with the different discounts you can obtain. Price of products might change often and it's very practical to track the price at the moment of the order to verify that it's in line with what you paid in the past. Task-2658786 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Odoo now lets developers define a fallback action when optional visual effects are turned off. This helps ensure users still get a clear response instead of a missing or inconsistent experience.
Original PR description
## [IMP] web: improve effect service api Before: The dev creating an effect had to handle himself the fact that effects had been enabled or not. He could just ignore the best practice and make a bad experience for the end user. After: The function providing the effect can now put an `alternative` key in the returned object that is a function to execute if effects are disabled.
This update adds internal helpers that make it easier to test touch-based actions at precise screen positions. It supports upcoming mobile interface improvements by making related tests more reliable and easier to write.
Original PR description
Description of the issue/feature this PR addresses: This PR adds some touch events helper in tests/helpers/utils of web. It is used for the tests of the ActionSwiper component of web_mobile. It is linked to the tasks with IDs 2391177 and 2361187. Current behavior before PR: It is difficult to generate touch actions in tests Desired behavior after PR is merged: You can used those new events in your tests to generate touch interaction at precise coordinates. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Mobile users can now swipe notifications and inbox items to quickly handle common actions, such as marking messages as read, unpinning conversations, or dismissing warnings. This makes managing messages on mobile faster and more intuitive, with the swipe component built for reuse in other areas later.
Original PR description
This PR adds the ActionSwiper component. This component has been made as a generic web_enterprise component for re-usability. Currently used in mail_enterprise, it allows mobile users to swipe to right a message/email and mark it as read. Swiping to the left unpins a conversation. It can be added to other components if needed. Behavior after PR merged: Mobile users will be able to interact with notifications when swiping on them depending the type of notification. - In the notification list, it might unpin the conversation, mark a message as read or dismiss a warning. - In the inbox, you can mark a message as read. It is linked to the tasks with IDs 2391177 and 2361187.
Payroll signature requests now use the document filename in their reference instead of the employee's active contract name. This makes requests easier to identify and match to the correct document for payroll teams.
Original PR description
When asking for a signature request for an employee in payroll, the reference of the signature is always 'signature request - ' + the name of active contract of that employee. This PR changes the reference to be 'signature request' + filename instead. task-2657779
This update makes activity-related errors clearer for users, including when creating phone calls or using document upload activities without document access. It also expands automated testing around activities, VoIP, documents, and performance to reduce regressions in future releases.
Original PR description
PURPOSE Fix an error wording in documents. While being in that code, add tests. SPECIFICATIONS Improve wording when failing to create a phonecall from activities and add tests. Purpose is to be a bit…
PURPOSE Fix an error wording in documents. While being in that code, add tests. SPECIFICATIONS Improve wording when failing to create a phonecall from activities and add tests. Purpose is to be a bit nicer to the user. We also add a few functional tests to begin improving testing of activities in submodules. Add some query counters tests in test_mail_enterprise that installs a lot of sub mail modules in both community and enterprise. Purpose is to have basics for testing and some first query counter tests. In this commit we add some query counters for activities management: creation and usage through mixin. We add voip dependency in test_mail_enterprise in order to test features and additional workload linked to VOIP management in activities. Notably query counters are updated and added to check a bit current performance state. We add documents in test_mail_enterprise dependencies in order to test features and additional workload linked to document management in activities. In this task we test creation of activities linked to documents and upload. We also remove unnecessary definition of ``default_user_id`` as it is defined in ``mail`` module. Code is the same, no need to redefine twice the same code and behavior in documents. Task-2657021