Openbravo Issue Tracking System - POS2
View Issue Details
0056639POS2Corepublic2024-10-03 12:162024-11-07 19:00
malsasua 
Bimla_vm 
normalminorhave not tried
closedopen 
5
 
 
guilleaer
No
0056639: Combo fixed discount is informed in the line although the combo was not applied
When there are two combo fixed price discounts configured for the same products, and one has got a higher priority than the other, with the flag: "apply next discount: false", in the POS, in the line info, the two combo discounts name are displayed
BO:
. create a new combo fixed price discount:
 - name: test1
 - priority: 1
 - apply next discount: No
 - combo fixed price: 42
 - new Family:
   - name F1
   - qty: 2
   - max qty: 2
   - add product
      - Crampons 10 point
. create a new combo fixed price discount:
 - name: test2
 - priority: (empty)
 - apply next discount: Yes
 - combo fixed price: 25
 - new Family:
   - name F1
   - qty: 1
   - max qty: 1
   - add product
      - Crampons 10 point

POS:
- add product: Crampons 10 point
 - qty 2

Total ticket 42 € -> it is OK
In the line description, the 2 combo names are displayed (see attachment) -> KO
only test1 combo name should be displayed
No tags attached.
png combo.png (25,030) 2024-10-03 12:17
https://issues.openbravo.com/file_download.php?file_id=20222&type=bug
png
Issue History
2024-10-03 12:16malsasuaNew Issue
2024-10-03 12:16malsasuaAssigned To => Triage Platform Base
2024-10-03 12:16malsasuaTriggers an Emergency Pack => No
2024-10-03 12:17malsasuaFile Added: combo.png
2024-10-14 08:23malsasuaSeveritymajor => minor
2024-10-25 11:47AugustoMauchAssigned ToTriage Platform Base => Retail
2024-10-29 08:15guilleaerAssigned ToRetail => guilleaer
2024-10-29 08:15guilleaerStatusnew => acknowledged
2024-10-29 08:16Bimla_vmAssigned Toguilleaer => Bimla_vm
2024-10-29 08:16Bimla_vmStatusacknowledged => scheduled
2024-11-07 19:00guilleaerReview Assigned To => guilleaer
2024-11-07 19:00guilleaerNote Added: 0171657
2024-11-07 19:00guilleaerStatusscheduled => closed

Notes
(0171657)
guilleaer   
2024-11-07 19:00   
In the case of test2, the priority is empty, so it will be treated as the first discount to apply (since no-manual discounts must be sorted by priority, and discounts with null priorities are considered first in memory). Additionally, in test2, the "Apply next discount" field is set to true, allowing the next discount, which is test1, to be applied.