Friday, August 30, 2024
5 changes · master
Enhancements to existing features
This update simplifies how the UrbanPiper point of sale integration identifies the current order. It reduces reliance on duplicate internal logic, helping keep order handling more consistent and easier to maintain.
Original PR description
Remove `selectedOrder` getter to use `get_order()` instead. taskId: 4141914
Resolved issues and error corrections
The Field Service sales tour has been corrected so users can create a product and return to the product list without encountering an error. This prevents interruptions during guided Field Service workflows and keeps the product selection flow stable.
Original PR description
This commit resolves an issue where a traceback occurs during the FSM tour. Steps to reproduce: 1. Start the FSM tour. 2. Create a new task. 3. Launch the timer on the task. 4. Click on the Products cart stat button. 5. Create a new product. 6. Use the breadcrumbs to navigate back to the product list. 7. Traceback occurs. Issue: Extra classes were being added unintentionally, causing the traceback. Solution: Remove the unnecessary classes to prevent the traceback. task-4140462
Miscellaneous changes
vat base and change exempt base to exports account. Forward-Port-Of: odoo/enterprise#66380 Forward-Port-Of: odoo/enterprise#66086
Original PR description
vat base and change exempt base to exports account. Forward-Port-Of: odoo/enterprise#66380 Forward-Port-Of: odoo/enterprise#66086
Have a partner in need of action with the followup level configured to Send an Email, with 'Automatic' enabled Case 1: - Send the followup manually - Reply to the follouwp mail - Message will be posted as log note but the system link the message with the previous one[1], where user is the author and will be automatically notified Case 2: - Wait for the cron to send followup automatically - Reply to the followup mail - Message will be posted as log note but since OdooBot is the author
Original PR description
Have a partner in need of action with the followup level configured to Send an Email, with 'Automatic' enabled Case 1: - Send the followup manually - Reply to the follouwp mail - Message will be posted as log note but the system link the message with the previous one[1], where user is the author and will be automatically notified Case 2: - Wait for the cron to send followup automatically - Reply to the followup mail - Message will be posted as log note but since OdooBot is the author of the previous message no user will receive any notification With this commit we make use of the followup responsible when sending followup email automatically before defaulting to OdooBot [1] https://github.com/odoo/odoo/blob/fe4b2a6d08a450b281e7ac0676afd51a88dd6008/addons/mail/models/mail_thread.py#L1182 opw-4000835 Forward-Port-Of: odoo/enterprise#67391
As the SO for subscription are updated every recurrence, it's hard to keep track of possible upselling opportunities. This change update the sale upselling opportunity for subscription to save more information regarding the opportunity and don't erase old activities to keep a better record of what has been deliverd/invoiced. task-id : 3323129 Forward-Port-Of: odoo/enterprise#63894
Original PR description
As the SO for subscription are updated every recurrence, it's hard to keep track of possible upselling opportunities. This change update the sale upselling opportunity for subscription to save more information regarding the opportunity and don't erase old activities to keep a better record of what has been deliverd/invoiced. task-id : 3323129 Forward-Port-Of: odoo/enterprise#63894