Openbravo Issue Tracking System - Retail Modules | |||||
View Issue Details | |||||
ID | Project | Category | View Status | Date Submitted | Last Update |
0028733 | Retail Modules | Web POS | public | 2015-01-22 13:24 | 2015-01-22 13:24 |
Reporter | plujan | ||||
Assigned To | marvintm | ||||
Priority | normal | Severity | minor | Reproducibility | random |
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 | 0028733: If cache loading process fails on getting Master Data the data gets never loaded | ||||
Description | After clearing the cache, the process of loading data tries to retrieve all the Master Data. If this process fails, you may end up with a non functioning application. Note that you will not get any error message in the GUI, and that the only solution is to clear the cache again. | ||||
Steps To Reproduce | This steps are not precise, since the nature of the failure is not deterministic. 1. Get an environment where wireless strength is about -80dBm 2. Clear browser cache. 4. Login as vallblanca user 5. At a random basis, some data will fail to load in the cache (you may see something wrong via the web console). From the end user point of view, you may observe one of these: -WebPOS gets stuck in Loading... screen -Main page does not show Business Partner in the initial ticket and the buttons to browse products are disabled -You have no products to browse Note that from an end user point of view no error has happened. In order to solve the issue, a new cache cleaning is required, but this will not happen automatically. | ||||
Proposed Solution | The cache-filling process should be able to detect that everything has been properly loaded and, in case of any error, to discard potentially wrong data to be loaded again. GUI should inform with a proper message that something has gone wrong and provide a list of actions to take. | ||||
Additional Information | |||||
Tags | No tags attached. | ||||
Relationships | |||||
Attached Files | |||||
Issue History | |||||
Date Modified | Username | Field | Change | ||
2015-01-22 13:24 | plujan | New Issue | |||
2015-01-22 13:24 | plujan | Assigned To | => marvintm | ||
2015-01-22 13:24 | plujan | Triggers an Emergency Pack | => No |
There are no notes attached to this issue. |