Wednesday, September 6, 2023
6 changes · master
Resolved issues and error corrections
This fix prevents the Mail and Discuss app from crashing when the same record deletion is triggered more than once, such as during slow network conditions. Users get a more stable messaging experience because repeated delete actions now safely end in the intended deleted state.
Original PR description
Before this commit, calling `record.delete` twice would result in a crash. This is due to `this.Model`being cleared once the delete is done. This commit skips the deletion if it was already done: calling delete will result in the desired state anyway. This can be easily reproduced: - Throttle your network - Send a message on the discuss app - A crash occurs
Point of Sale no longer briefly flashes the receipt preview when the system is configured to skip it. Receipts now print directly from the payment screen, creating a cleaner checkout experience for cashiers and customers.
Original PR description
Currently when the pos.config is set to "Skip Preview", when printing a receipt, the receipt or bill screen shows very quickly and disappears. This is not good UX. Now, the receipt is printed from the payment screen itself. We don't need to show the receipt screen at all. taskId: 3441238
This fixes an issue where time off allocations that started in the past could be counted twice after the scheduled accrual process ran. The change ensures balances stay accurate, reducing the risk of employees receiving incorrect leave amounts.
Original PR description
Before this commit, creating a new allocation based on accruals and setting a start date prior to the creation date would compute the amount of days that should already have been accrued during that time. However, the lastcall field is not updated and running the accrual cron leads to a wrong duration. How to recreate the issue: - create an accrual plan - create an allocation set on that accrual - set a start date in the past for that allocation - the duration should be automatically set to a value above 0 - save and validate - run the accrual cron - the allocation now has its duration doubled After this commit, the lastcall should be set to the allocation creation date. This way, running the cron will correctly keep the value of the amount of days.
Point of Sale orders now use one consistent order date instead of separate creation and validation dates. This reduces confusion in order processing and helps keep order information aligned across the checkout, tickets, loyalty, online payment, restaurant, and self-order flows.
Original PR description
In this commit: =============== Revised parsing of order date flow. Eliminated the confusion caused by separate "creation_date" and "validation_date" by consolidating both into the "date_order" field. This change provides clarity to the parsing of order date process.
Fixed an issue where appointment booking pages displayed “Invalid DateTime” instead of the day for available slots. This ensures customers can clearly see and select appointment dates, avoiding confusion during booking.
Original PR description
Steps to Reproduce =================== 1. On website click on appointment tab from nav bar. 2. Click on any appointment. -> on the slot selection page we can see that the day is not showing and instead of day it is showing 'Invalid DateTime' Technical ========== Changing fromJSDate() to fromISO() because fromJSDate() only takes date object as an argument but slotDate is a string so it is giving error like 'Invalid DateTime' on UI side. This bug is comming after the refactor of moment to luxon https://github.com/odoo/enterprise/pull/44051/commits/f543608428dbc255962bf9b7fecc1de3ebeedb68 task-3491906
This update fixes several manufacturing workflow issues, including starting work orders when no user session is available, simplifying finished goods handling, and adding a quicker way to generate serial or lot numbers during quality checks. It also stabilizes a timesheet timer test to reduce unreliable failures in development.