Openbravo Issue Tracking System - Retail Modules |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0028608 | Retail Modules | Manual user action | public | 2015-01-14 11:31 | 2016-01-25 20:18 |
|
Reporter | lorenzofidalgo | |
Assigned To | marvintm | |
Priority | urgent | Severity | minor | Reproducibility | always |
Status | new | Resolution | open | |
Platform | | OS | 5 | OS Version | |
Product Version | RR14Q4 | |
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 | 0028608: After completing a receipt, POS shows a successful synchronization message, but Sales Orders are lost |
Description | Tested in livebuilds RR14Q4, RR14Q3.4 & RR14Q2.5.
Once completed a receipt, POS shows the following message: "Data synchronization was successful". Checking "Sales Order" backend, the receipt never appears.
After checking log, it appears: "ERROR org.openbravo.mobile.core.process.DataSynchronizationProcess - Error while loading order
org.openbravo.base.exception.OBException: The Period does not exist or it is not opened"
POS should not allow users to "complete" receipts in POS or showing successul messages if it is not possible to treat them succeessfully.
All those completed receipts in POS are lost. |
Steps To Reproduce | Login POS, choose any product and complete a receipt.
Go to backend and login as Openbravo/openbravo and choose "The White Valley Group Admin" role.
Go to Sales Order window. Check there is no new sales orders. |
Proposed Solution | |
Additional Information | |
Tags | No tags attached. |
Relationships | related to | defect | 0028562 | | closed | marvintm | Cash up does not finish and an error is shown at the console |
|
Attached Files | |
|
Issue History |
Date Modified | Username | Field | Change |
2015-01-14 11:31 | lorenzofidalgo | New Issue | |
2015-01-14 11:31 | lorenzofidalgo | Assigned To | => marvintm |
2015-01-14 11:31 | lorenzofidalgo | Triggers an Emergency Pack | => No |
2015-01-14 11:34 | lorenzofidalgo | Relationship added | related to 0028562 |
2015-01-30 11:33 | malsasua | Note Added: 0073940 | |
2015-01-30 11:33 | malsasua | Status | new => closed |
2015-01-30 11:33 | malsasua | Resolution | open => no change required |
2016-01-13 15:20 | lorenzofidalgo | Steps to Reproduce Updated | bug_revision_view_page.php?rev_id=10607#r10607 |
2016-01-13 15:22 | lorenzofidalgo | Note Added: 0083241 | |
2016-01-13 15:22 | lorenzofidalgo | Status | closed => new |
2016-01-13 15:22 | lorenzofidalgo | Resolution | no change required => open |
2016-01-13 15:34 | lorenzofidalgo | Note Added: 0083243 | |
2016-01-13 15:38 | lorenzofidalgo | Note Added: 0083244 | |
2016-01-25 20:18 | dmitry_mezentsev | Note Added: 0083600 | |
2016-01-25 20:18 | dmitry_mezentsev | Severity | critical => minor |
Notes |
|
|
it is the behavior expected: the sales orders have been inserted in "Errors while importing data" window. From this window, the sales order can be imported when the problem of period closed has been fixed. |
|
|
|
No error is shown to warn the POS user that those receipt are not correctly processed. At least an error message should be shown to the user. Currently, success message is shown. |
|
|
|
With this Steps to Reproduce it is obvious that some changes are required:
0-Login POS as vallblanca.
1-Create a new receipt and complete it.
2-In dropdown menu, go to Receipts option.
3-Look for the just created receipt. Defect: That receipt does not appear. It has not correctly created and it has not been warned to the user. Instead of that, success message is shown. |
|
|
|
This has been reproduced in RR16Q1 |
|
|
|
Not Critical, http://wiki.openbravo.com/wiki/Bug_Reporting_Guidelines#How_to_Choose_the_Right_Severity [^]
I understand the use case but we need to think on the approach here because it applies not only to this specific case but to all scenarios when the order is saved in the errors. Now we do not notify POS user about them because it cannot influence / change them and so why to bother. But it is true that there are scenarios (like this search for the receipt) where it could help to know.
Still developing this notification is a topic because now with 2 steps order saving (at first in the raw "queue" table and then post-processing) the order for POS is saved when it is in the queue and it does not know about its processing result that happens later on.
So success message makes sense. It means the order was moved to the backoffice. But we could think on putting some on-demand request mechanism from POS to check error table that can be triggered by the user when the receipt is not found in the order table. |
|