Openbravo Issue Tracking System - Retail Modules | |||||
View Issue Details | |||||
ID | Project | Category | View Status | Date Submitted | Last Update |
0031275 | Retail Modules | Layaway order | public | 2015-10-27 17:38 | 2015-10-27 17:38 |
Reporter | plujan | ||||
Assigned To | Retail | ||||
Priority | normal | Severity | trivial | Reproducibility | have not tried |
Status | new | Resolution | open | ||
Platform | OS | 5 | OS Version | ||
Product Version | main | ||||
Target Version | Fixed in Version | ||||
Merge Request Status | |||||
Review Assigned To | |||||
OBNetwork customer | |||||
Support ticket | |||||
Regression level | |||||
Regression date | |||||
Regression introduced in release | |||||
Regression introduced by commit | |||||
Triggers an Emergency Pack | No | ||||
Summary | 0031275: [RR15Q4] [Multiterminal Layway] Tickets can be paid twice using different terminals | ||||
Description | A created layaway can be found in all the terminals of the store. There is a flow where two or more terminals see the same layaway as not paid, and the payment flow can be executed with no warnings nor errors. As a result, in the backend the same Sales Order appears as paid multiple times. | ||||
Steps To Reproduce | 1. Using VBS-1 terminal create a ticket and choose the menu option to Layway it. 2. Using two terminales, VBS-1 and VBS1001 seek for the created ticket and execute the payment flow. Note that the flow shows no errors/warnings. 3. Go to the backend and login as WhiteValley admin 4. Seek for the ticket, check that two payments were created | ||||
Proposed Solution | This flow is a corner case, since it will not happen in normal conditions. However, in order to prevent this to happen by mistake, some kind of message to alert the user about a potential duplicated payment should be shown. | ||||
Additional Information | |||||
Tags | No tags attached. | ||||
Relationships | |||||
Attached Files | |||||
Issue History | |||||
Date Modified | Username | Field | Change | ||
2015-10-27 17:38 | plujan | New Issue | |||
2015-10-27 17:38 | plujan | Assigned To | => Retail | ||
2015-10-27 17:38 | plujan | Triggers an Emergency Pack | => No |
There are no notes attached to this issue. |