0040332: [Sessions] Under specific circumstances OpenSessionPOS is called without the cashUpReportInformation parameter

Anonymous | Login

Project:

News | My View | View Issues | Roadmap | Summary

View Revisions: Issue #40332		[ All Revisions ] [ Back to Issue ]
Summary	0040332: [Sessions] Under specific circumstances OpenSessionPOS is called without the cashUpReportInformation parameter

Revision	2019-03-06 18:29 by aaroncalero
Steps To Reproduce	This specific execution of the process only happens when the object OB.UTIL.localStorage.getItem('pendingSessions') has data, which seems to happen if the OpenSessionsPOS has failed first (i.e. the system was offline or with heavy load). 1. In an environment with Sessions installed, login in WebPOS and do the Cash Up process. The system will automatically logout in the end of the process. 2. Login in backend and configure the Web POS Synchronized mode preference. 3. Login in WebPOS again. The Open till window will be shown. 4. Complete the Open Till process. The server call needs to end with error, so the errorCallback is executed and the pendingSessions object is created. 5. The login process will continue normally, but when the next runSyncProcess is executed (which happens automatically at the end of the login process), the pending sessions hook will execute and the process will fail in the server

Revision	2019-03-06 17:45 by aaroncalero
Steps To Reproduce	This specific execution of the process only happens when the object OB.UTIL.localStorage.getItem('pendingSessions') has data, which seems to happen if the OpenSessionsPOS has failed first (i.e. the system was offline or with heavy load). The problem can be theoretically reproduced by adding an exception in the OpenSessionsPOS after the cashupReportInformation is processed: 1. In an environment with Sessions installed, login in WebPOS and do the Cash Up process. The system will automatically logout in the end of the process. 2. Login in backend and configure the Web POS Synchronized mode preference. 2. Add a if(true) throw new OBException("test"); line in OpenSessionsPOS after the cashupReportInformation is read. 3. Login in WebPOS again. The Open till window will be shown. 4. Complete the Open Till process and verify that the process fails with the "test" exception. 5. Refresh the application and try again. Now the process will fail because there is no cashup in the parameters.