Monday, November 4, 2024
5 changes
1 change
Resolved issues and error corrections
Kiosk self-ordering now receives timely online payment status updates, including when a payment is in progress and when it is completed. This prevents customers from getting stuck after scanning the payment QR code and helps the kiosk move smoothly to order validation once payment succeeds.
Original PR description
Currently, when using the kiosk with an online payment method, the kiosk does not receive notification about the payment status. Steps to reproduce: ------------------- * Select the **Point of Sale**…
Currently, when using the kiosk with an online payment method, the kiosk does not receive notification about the payment status. Steps to reproduce: ------------------- * Select the **Point of Sale** App * Under Configuration select **Payment Methods** * Create a new payment method (Online payment, Allowed Providers: Demo) * Now go into the setting of the restaurant (make sure session was closed) * Change the Payment methods, remove the cash and add the one created * Change Self Ordering to Kiosk then save * Open the kiosk and create an order * Go to pay the order * Scan the qr code * Pa with demo > Observation: 2 observations. First we don't receive the "In progress" notification after scanning the qr code. Second, we are not redirected to the validation page after the order was paid. In the backend orders are marked as paid. Why the fix: ------------ `request.env['bus.bus']` is empty. The issue was already solved in the next version with https://github.com/odoo/odoo/commit/31226b1a95242631a190d92e9ffb5ad97822bcbd#diff-a843415b00d5a84e604420ec6a19040426294ec9b5deeacf6f12876c12af06dd opw-4120145
1 change
Resolved issues and error corrections
Point of Sale order creation now makes the new order available immediately, preventing follow-up actions from running before key order details are ready. This improves reliability for due settlements, delivery integrations, and related fiscal or compliance flows.
Original PR description
2 changes
Resolved issues and error corrections
The All Tasks list now loads much faster, especially when grouped by stages with many tasks. This reduces long wait times from around 20 seconds to under a second in heavy views, improving day-to-day usability for project and sales teams.
Original PR description
1 change
Resolved issues and error corrections
This update corrects a recent change that prevented officers from viewing feedback answers. The fix ensures officers have the necessary access to this information, streamlining the appraisal process and improving data visibility. This resolves issue OPW-4128638.
Original PR description
after this [FIX](https://github.com/odoo/enterprise/commit/ffcc8c425b53df94d79ace17fb444504df8acd52), the access to answers of feedbacks is restricted to the manager of appraisals, but the officer should have access too. this commit fixes this issue. opw-4128638
`add_new_order` method is now synchronous and returns the new order. This allows to directly use the new order in the next steps without the need to await the promise. The `pos_order` reference is now added to the order by calling `getNextOrderRefs` that's isn't awaited anymore. That's means that during a small amount of time, the order didn't have following fields: `pos_reference`, `tracking_number` and `sequence_number`
This commit fixes a performance issue with the "All tasks" list view. The issue especially arose when the view was grouped by stages (because groups are opened by default in that case) and when it…
This commit fixes a performance issue with the "All tasks" list view. The issue especially arose when the view was grouped by stages (because groups are opened by default in that case) and when it contained a lot of stages, each of them containing a lot of records. In the worst case, the view could have to render up to 800 records (80 per group, 10 groups opened), and it could take around 20seconds. With this commit, the rendering part is done in around 400ms.
This commit actually fixes 2 issues.
First, in sale_project, there was an override of `isCellReadonly` to force the `sale_line_id` to be readonly if several records with different partners (`partner_id` field) were selected. This override accessed `this.props.list.selection` once per cell (all cells, not only for the `sale_line_id` column), and this is actually a getter which browses through all records, to generate the list of selected ones. This was thus quadratic. This commit applies a similar logic as in [1] to compute the selection only once for the whole table.
Second, [1] wasn't as optimal as expected. Indeed, we tried to compute a flag only once for the whole template rendering, by setting a variable on `this`. However, the ListRenderer template using `t-call` to render each row, a new rendering context is created for each row. By doing
```xml
t-att-class="getCellClass(column, record)"
```
the `this` inside `getCellClass` is that rendering context object, so it can't be used to share a flag from a row to another. Explicitely calling `getCellClass` on `this` ensures that the `this` inside the function is the instance, which is the same for all rows.
[1] https://github.com/odoo/odoo/pull/153858
Description of the issue/feature this PR addresses:
Current behavior before PR:
Desired behavior after PR is merged:
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prCreating time off from the Gantt view no longer fails when a resource has no working time set. This prevents an error during leave creation and keeps Time Off management usable in configurations with empty resource calendars.
Original PR description
The error occurs because we are setting ``Working Time`` to empty in ``Resources`` and then attempting to add leave from the ``Gantt`` view in the Time Off section. Steps to reproduce: --- - Install ``hr_holidays_gantt`` module(without demo data) - Go to resource and from ``Administrator`` remove ``Working Time`` - Now Time Off > Management > Time Off - Go to ``Gantt`` view > Create New and Click on ``Save & Close`` ``Traceback: KeyError: 6`` At [1], we are facing an error because ``leaves_mapping`` is empty and we are trying to access this dictionary using a key that doesn't exist. [1]- https://github.com/odoo/enterprise/blob/d4608a66f164940fe4383507e23eed9f54bf60df/hr_holidays_gantt/models/hr_leave.py#L181 sentry-6010228921