Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
| ID | ||||||||||||
| 0031275 | ||||||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
| defect | [Retail Modules] Layaway order | trivial | have not tried | 2015-10-27 17:38 | 2015-10-27 17:38 | |||||||
| Reporter | plujan | View Status | public | |||||||||
| Assigned To | Retail | |||||||||||
| Priority | normal | Resolution | open | Fixed in Version | ||||||||
| Status | new | Fix in branch | Fixed in SCM revision | |||||||||
| Projection | none | ETA | none | Target Version | ||||||||
| OS | Any | Database | Any | Java version | ||||||||
| OS Version | Database version | Ant version | ||||||||||
| Product Version | main | SCM revision | ||||||||||
| Merge Request Status | ||||||||||||
| Review Assigned To | ||||||||||||
| OBNetwork customer | No | |||||||||||
| 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. | |||||||||||
| Tags | No tags attached. | |||||||||||
| Attached Files | ||||||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|
 Relationships |
|
Notes |
|
| There are no notes attached to this issue. |
|
Notes |
|
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 | OBNetwork customer | => No |
| 2015-10-27 17:38 | plujan | Triggers an Emergency Pack | => No |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |