Thursday, September 5, 2024
4 changes · saas-17.4
Enhancements to existing features
The attendance onboarding flow now uses clearer wording and a redesigned mobile layout to prevent broken or hard-to-use screens. The kiosk experience also performs better by showing employee cards in pages sized to the user's screen.
Original PR description
Some texts are changed to be more comprehensible. The mobile view was reworked to avoid broken onboarding view. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Floating orders in the point of sale are now kept visible even when their cart is empty, helping staff avoid losing track of open orders. The order list is also easier to scan because entries are sorted by time, note, and tracking number, with clearer note text when adding details.
Original PR description
This commit improves the floating order experience. It prevents the order from disappearing even if the cart is empty by automatically booking it. It changes the placeholder of the note popup. It sorts the floating order by time (included in the note), then by note, then by tracking_number. task-id: 4011383 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The attendance app now includes Gantt and pivot views to make attendance information easier to understand and analyze. This helps managers review schedules and attendance patterns more clearly without relying only on list-style data.
Original PR description
To improve customer's comprehensibility; the gantt and pivot view are added task-3999189
Subscription billing and payment status updates now coordinate more smoothly when they happen at the same time. This reduces failed updates caused by payment webhooks and invoice processing trying to modify the same subscription order simultaneously.
Original PR description
Before this commit, when the payment provider updated the tx state with a webhook, the order was updated in a separate SQL transaction than the invoicing corn of subscription. Both transactions would update the same sale.order, resulting in concurrent update errors.