Monday, March 25, 2024
3 changes · master
Resolved issues and error corrections
This update fixes an internal issue affecting restaurant Point of Sale and Indian localization features. It ensures these modules follow the current application rules, helping avoid errors or instability during Point of Sale operations.
Original PR description
PoS variable was use in models in localization modules. This is not allowed anymore. This commit fixes the issue.
The Planning demo data now uses safer relative date calculations so sample shifts have valid start and end dates. This prevents demo data from triggering a scheduling date constraint and helps installations load the Planning examples reliably.
Original PR description
Working with relative week days can be surprising, sor instance ```python In [3]: datetime(2024, 3, 23) - relativedelta(weeks=2, weekday=4) Out[3]: datetime.datetime(2024, 3, 15, 0, 0) In [4]: datetime(2024, 3, 23) - relativedelta(weeks=2, weekday=5) Out[4]: datetime.datetime(2024, 3, 9, 0, 0) ``` This is due to the fact that 2024-03-23 is a Saturday (weekday=5), so setting the weekday has no effect, whereas searching for weekday=4 will search for the next day that matches the criterion (Friday), leading in a future date. This was breaking the constraint `planning_slot_check_start_date_lower_end_date`
This update adjusts Point of Sale-related modules to follow the latest internal rules for how sales data is handled. It helps prevent errors in Chilean electronic invoicing for PoS and preparation display workflows after recent platform changes.
Original PR description
PoS variable was use in models in localization modules. This is not allowed anymore. This commit fixes the issue.