Openbravo Issue Tracking System - Retail Modules |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0034586 | Retail Modules | Web POS | public | 2016-11-18 15:05 | 2016-12-07 14:54 |
|
| Reporter | malsasua | |
| Assigned To | marvintm | |
| Priority | high | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | |
| Platform | | OS | 5 | OS Version | |
| Product Version | | |
| Target Version | | Fixed in Version | RR17Q1 | |
| Merge Request Status | |
| Review Assigned To | guilleaer |
| OBNetwork customer | |
| Support ticket | |
| Regression level | |
| Regression date | |
| Regression introduced in release | |
| Regression introduced by commit | |
| Triggers an Emergency Pack | No |
|
| Summary | 0034586: it is posible to create receipts related with processed cashup |
| Description | there is one way to create receipts from WEBPOS related with processed cashups |
| Steps To Reproduce | in webpos:
. create receipt1 associated to cashup1 (it is synced successfully)
. process the cashup (it is synced, but it is stored in "Data Import Entry" in error status)
-> new cashup (with id cashup2) has been created in terminal but not synced with backoffice
. clean the cache of terminal
the cashup loaded from backend is the cashup live in backoffice (cashup1)
. do a receipt (receipt2 associated with cashup1 is synced and stored in Data Import Entry with status Error, waiting to process the cashup created in step1)
in backoffice:
. fix the error of cashup1 and process it
. process receipt2 -> error: the cashup associated to this receipt has been processed |
| Proposed Solution | |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | | causes | defect | 0035367 | RR17Q2 | closed | marvintm | Not possible to log in the Web POS if there are resolved errors in the Errors While Importing POS data window |
|
| Attached Files | |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2016-11-18 15:05 | malsasua | New Issue | |
| 2016-11-18 15:05 | malsasua | Assigned To | => Retail |
| 2016-11-18 15:05 | malsasua | Resolution time | => 1481324400 |
| 2016-11-18 15:05 | malsasua | Triggers an Emergency Pack | => No |
| 2016-12-06 13:14 | marvintm | Status | new => scheduled |
| 2016-12-06 13:14 | marvintm | Assigned To | Retail => marvintm |
| 2016-12-06 19:27 | hgbot | Checkin | |
| 2016-12-06 19:27 | hgbot | Note Added: 0092145 | |
| 2016-12-06 19:27 | hgbot | Status | scheduled => resolved |
| 2016-12-06 19:27 | hgbot | Resolution | open => fixed |
| 2016-12-06 19:27 | hgbot | Fixed in SCM revision | => http://code.openbravo.com/erp/pmods/org.openbravo.retail.posterminal/rev/02c6c8e2af1710fd1ca9e865b55ed7996fe6151a [^] |
| 2016-12-06 20:35 | hgbot | Checkin | |
| 2016-12-06 20:35 | hgbot | Note Added: 0092148 | |
| 2016-12-06 20:35 | hgbot | Checkin | |
| 2016-12-06 20:35 | hgbot | Note Added: 0092149 | |
| 2016-12-07 14:44 | hgbot | Checkin | |
| 2016-12-07 14:44 | hgbot | Note Added: 0092195 | |
| 2016-12-07 14:54 | guilleaer | Review Assigned To | => guilleaer |
| 2016-12-07 14:54 | guilleaer | Status | resolved => closed |
| 2016-12-07 14:54 | guilleaer | Fixed in Version | => RR17Q1 |
| 2017-02-27 12:34 | marvintm | Relationship added | causes 0035367 |
|
Notes |
|
|
(0092145)
|
|
hgbot
|
|
2016-12-06 19:27
|
|
Repository: erp/pmods/org.openbravo.retail.posterminal
Changeset: 02c6c8e2af1710fd1ca9e865b55ed7996fe6151a
Author: Antonio Moreno <antonio.moreno <at> openbravo.com>
Date: Tue Dec 06 15:59:52 2016 +0100
URL: http://code.openbravo.com/erp/pmods/org.openbravo.retail.posterminal/rev/02c6c8e2af1710fd1ca9e865b55ed7996fe6151a [^]
Fixed issue 34586. Restrict login in case cache is lost, and there is an error in a cashup.
- If a processed cashup fails with error (either as importentry, or later on as a POS error), then its corresponding record in the backend is not marked as complete.
- This is not a problem in the case the Web POS continues to work normally, because a new cashup is created automatically in the client side.
- However, if the cache is then cleared, then currently there is a problem, because the Web POS tries to load the current cashup from the backend, and here the record was not updated yet, because of the error.
- The solution is to detect this case, and then restrict the login in this terminal until the problem is resolved.
---
M src-db/database/sourcedata/AD_MESSAGE.xml
M src/org/openbravo/retail/posterminal/master/Cashup.java
M web/org.openbravo.retail.posterminal/js/login/model/login-model.js
M web/org.openbravo.retail.posterminal/js/utils/cashUpReportUtils.js
---
|
|
|
|
(0092148)
|
|
hgbot
|
|
2016-12-06 20:35
|
|
Repository: tools/automation/pi-mobile
Changeset: 2492d5cadf781752fe51afafed4fe94e31583ae5
Author: Antonio Moreno <antonio.moreno <at> openbravo.com>
Date: Tue Dec 06 16:01:20 2016 +0100
URL: http://code.openbravo.com/tools/automation/pi-mobile/rev/2492d5cadf781752fe51afafed4fe94e31583ae5 [^]
Related to issue 34586. Added automated test for this case.
---
M src-test/org/openbravo/test/mobile/core/utils/AllowedErrorsHelper.java
A src-test/org/openbravo/test/mobile/retail/pack/selenium/tests/system/I34586_CashupErrorLoginRestricted.java
---
|
|
|
|
(0092149)
|
|
hgbot
|
|
2016-12-06 20:35
|
|
|
|
|
(0092195)
|
|
hgbot
|
|
2016-12-07 14:44
|
|
|