Daily updates from Odoo
Wednesday, January 22, 2025
4 changes
2 changes
Enhancements to existing features
Returning visitors booking the same appointment type are now kept with their previously assigned staff member when that person is still available, reducing duplicate leads and making follow-up easier. Upcoming appointment notices now appear above the calendar, so visitors can still see available booking options while being reminded of their existing appointment.
Original PR description
[IMP] {website_}appointment{_crm} : staff user assignation for the appointment types of visitors. Description of the issue/feature this PR addresses: When a visitor books several appointments for a…
[IMP] {website_}appointment{_crm} : staff user assignation for the appointment types of visitors.
Description of the issue/feature this PR addresses:
When a visitor books several appointments for a specific appointment type, for each of them a lead is be created. The lead will be assign to the staff user selected by the visitor on the appointment type page. So if the visitor chose each time a different staff user, there will be multiple leads for an appointment type and for a visitor but with different salespersons. So the management of the leads is complicated.
Current behavior before PR:
If the appointment does not authorize a random assignation of a staff user, the visitors can choose any of the available ones
Desired behavior after PR is merged:
For an specific appointment type and for a specific visitor, if a lead already exists and the staff user is assigned to it is still available, this one is chosen for the next appointment. Thus the selector widget is not present anymore.
If an ongoing lead with the same staff user, appointment type and partner already exists, this one must be link to the event and no lead must be created.
[IMP] {website_}appointment{_crm} : change the dislayed of the upcoming appointment alert.
Description of the issue/feature this PR addresses:
The upcoming appointment alert must be displayed above the calendar like all the other alerts
Current behavior before PR:
If an appointment is coming soon, the visitor lands on a specific page, where he cannot create a new appointment and where an alert offers him the possibility to check the upcoming appointment or create a new one.
Desired behavior after PR is merged:
The alert message informing the visitor that he has an upcoming appointment must be displayed above the calendar. Only a button giving him the possibility to check this last one must be present in the alert message.
task-4247031Repeat bookings for the same appointment type now stay with the same available staff member, reducing duplicate or fragmented sales follow-up. Visitors also see upcoming appointment reminders directly above the calendar, making it easier to review existing bookings without blocking new scheduling.
Original PR description
[IMP] {website_}appointment{_crm} : staff user assignation for the appointment types of visitors. Description of the issue/feature this PR addresses: When a visitor books several appointments for a…
[IMP] {website_}appointment{_crm} : staff user assignation for the appointment types of visitors.
Description of the issue/feature this PR addresses:
When a visitor books several appointments for a specific appointment type, for each of them a lead is be created. The lead will be assign to the staff user selected by the visitor on the appointment type page. So if the visitor chose each time a different staff user, there will be multiple leads for an appointment type and for a visitor but with different salespersons. So the management of the leads is complicated.
Current behavior before PR:
If the appointment does not authorize a random assignation of a staff user, the visitors can choose any of the available ones
Desired behavior after PR is merged:
For an specific appointment type and for a specific visitor, if a lead already exists and the staff user is assigned to it is still available, this one is chosen for the next appointment. Thus the selector widget is not present anymore.
If an ongoing lead with the same staff user, appointment type and partner already exists, this one must be link to the event and no lead must be created.
[IMP] {website_}appointment{_crm} : change the displayed of the upcoming appointment alert.
Description of the issue/feature this PR addresses:
The upcoming appointment alert must be displayed above the calendar like all the other alerts
Current behavior before PR:
If an appointment is coming soon, the visitor lands on a specific page, where he cannot create a new appointment and where an alert offers him the possibility to check the upcoming appointment or create a new one.
Desired behavior after PR is merged:
The alert message informing the visitor that he has an upcoming appointment must be displayed above the calendar. Only a button giving him the possibility to check this last one must be present in the alert message.
task-42470312 changes
Enhancements to existing features
When the same visitor books another appointment of the same type, Odoo now reuses the salesperson already assigned to their existing lead when that person is available. This keeps follow-up ownership consistent, simplifies sales management, and shows upcoming appointment alerts directly above the booking calendar.
Original PR description
task-4247031
Resolved issues and error corrections
Orders placed from the same table QR code are now combined into the existing open table order. This helps restaurants avoid missing or split orders when multiple guests at one table order from different devices.
Original PR description
When 2 orders are made from the same QR Code representing the same table all the orders would not be merged on the table Steps to reproduce: ------------------- * Setup QR + Ordering and serving at Table in PoS settings * Open one table QR Code in 2 different devices/browsers * Make an order in each device > Observation: Only one will appear on the table Why the fix: ------------ Based on the behavior in 17.4 we should merge the orders from the same table. To do this when we find an open order for the table we change the id of the new order to the one of the existing order so that those 2 orders are merged. opw-4482805