Openbravo Issue Tracking System - POS2 | |||||
View Issue Details | |||||
ID | Project | Category | View Status | Date Submitted | Last Update |
0054869 | POS2 | POS | public | 2024-03-06 16:50 | 2024-03-06 16:59 |
Reporter | asier_perez | ||||
Assigned To | Retail | ||||
Priority | normal | Severity | minor | Reproducibility | always |
Status | new | Resolution | open | ||
Platform | OS | 5 | OS Version | ||
Product Version | |||||
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 | 0054869: The store is not closed when you close it, causing inconsistencies in the state and the back office | ||||
Description | When closing a till, if there are no more open tills, you have the option to close the store. After clicking the option to close the store, a popup appears with this text: "Store closed successfuly". (Note that "succesfuly" has a typo, but that is not the issue.) However, the store has not been closed successfully, because both the state and the back office indicate that it is till open. Moreover, if you refresh the page at this point, you will appear in the "set business date", as if the store would have been closed successfully. But the state and the back office still say that they are open, and from now on this inconsistency will keep appearing when logging in. This inconsistent status causes failures in automated tests. | ||||
Steps To Reproduce | Note: In some steps, I will ask you to check the till's information in the state. To do so, open developer tools and go to the Console tab, then type this text and press enter: OB.App.State.getState().Till When typing that text, you will see some fields, including storeStatus and tillStatus, which have two possible values: 'CL' when they are closed, and 'OP' when they are opened. Now, try to reproduce the issue in an environment you know there are no open tills apart from the one you are going to use. 1) Go to POS2, and close the till and the store if they are opened => Then, in the log in screen, ensure that the store and the till appear as closed in the state 2) Insert the credentials and log in => Then, in the "set business date" screen, ensure that the store and the till remain closed 3) Click Next button => In the "initial count", ensure that the store is now open, and the till remains closed 4) Click Finish button => Now in the key map screen, check that both the store and the till are opened 5) Go to Close Till 6) Click Next at the steps 1 and 2 of the cash up process 7) Click Finish at the step 3 => A popup will be shown asking you whether you want to close the store or not; you can check that the till and the store are still open 8) Select YES to close the store => Another popup will be shown saying that the till has been closed successfully, BUT check the state, because THEY ARE NOT CLOSED 9) Without clicking OK or anywhere else inside the POS, copy the web link to the till 10) Open another tab in the same browser and close the previous tab, then paste the link in the new one and press enter => The the "set business date" screen will appear (quite unexpected) 11) Check the till's information in the state => Both the till and the store are opened, but they should be closed Apart from the state, you can see the till's and store's status in the "Terminals and Tills Status" from the back office, and the issue is also present there. | ||||
Proposed Solution | |||||
Additional Information | |||||
Tags | No tags attached. | ||||
Relationships | |||||
Attached Files | inconsistentTillState.png (318,686) 2024-03-06 16:50 https://issues.openbravo.com/file_download.php?file_id=19525&type=bug | ||||
Issue History | |||||
Date Modified | Username | Field | Change | ||
2024-03-06 16:50 | asier_perez | New Issue | |||
2024-03-06 16:50 | asier_perez | Assigned To | => Retail | ||
2024-03-06 16:50 | asier_perez | File Added: inconsistentTillState.png | |||
2024-03-06 16:50 | asier_perez | Triggers an Emergency Pack | => No | ||
2024-03-06 16:52 | asier_perez | Steps to Reproduce Updated | bug_revision_view_page.php?rev_id=27647#r27647 | ||
2024-03-06 16:53 | asier_perez | Steps to Reproduce Updated | bug_revision_view_page.php?rev_id=27648#r27648 | ||
2024-03-06 16:54 | asier_perez | Steps to Reproduce Updated | bug_revision_view_page.php?rev_id=27649#r27649 | ||
2024-03-06 16:54 | asier_perez | Steps to Reproduce Updated | bug_revision_view_page.php?rev_id=27650#r27650 | ||
2024-03-06 16:59 | asier_perez | Steps to Reproduce Updated | bug_revision_view_page.php?rev_id=27651#r27651 |
There are no notes attached to this issue. |