Thursday, March 28, 2024
3 changes · 17.0
Enhancements to existing features
Imported electronic invoices now use Peppol endpoint and scheme details to identify the correct business partner more accurately. This reduces duplicate contacts and helps ensure invoices are linked to the right customer or supplier during import.
Original PR description
When importing an xml inheriting from EN16931 (Peppol Bis 3, A-NZ, E-FFF, NLCIUS, etc), use the peppol endpoint and eas to retrieve the correct partner, by passing a search domain to `_retrieve_partner` (through the `domain` argument). Hence, when retrieving the partner (using `_retrieve_partner`), we will sequentially: 1. search for a partner with a matching VAT 2. if there's a domain provided, search a partner matching the domain 3. search for a partner with a matching phone or email 4. search for a partner with a matching name If not partner is found, we create a new one. opw-3815296
The term "Upsell" has been replaced with "Quotation" in the customer portal for the subscription sales module. This change improves the customer experience in regions where the term "Upsell" has negative connotations, making the platform more culturally appropriate and customer-friendly.
Original PR description
The term "Upsell" has a negative impact on customers in some countries. It has been changed to "Quotation" task_id: 3699064
The appointment scheduling system now supports managing multiple resources per booking, similar to restaurant reservation systems with capacity management. The gantt view has been reorganized to group appointments by resources, making it easier to manage complex booking scenarios where customers can select multiple resources (staff, equipment, etc.) for a single appointment.
Original PR description
We now group the gantt view by resource_ids to manage appointment type where multiple resources can be chosen for the booking. It is now possible to manage appointment types of restaurant type (aka with manage capacity and multi resources). The field appointment_resource_id on the calendar event is removed as no longer useful. Everything is now managed with the computed resource_ids field and store with the appointment_resource_ids field through the appointment_booking_line table. The capacity distribution between resources is simplified and takes the shared resources in last. task-3812927