Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0040332
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Retail Modules] Sessionsmajorrandom2019-03-06 16:462019-03-06 18:29
ReporteraaroncaleroView Statuspublic 
Assigned Torqueralta 
PriorityhighResolutionopenFixed in Version
StatusnewFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

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

DescriptionThere is a hook[1] in the sessions module that, under specific circumstances, is calling the OpenSessionsPOS process without the cashupReportInformation parameter, which is a mandatory parameter for the execution of the process.

When this happens, the Open till process fails and the till is not opened, and a record is created in the Errors While Importing POS Data window.

[1] https://code.openbravo.com/erp/pmods/org.openbravo.retail.sessions/file/tip/web/org.openbravo.retail.sessions/js/components/loginhook.js#l407 [^]
Steps To ReproduceThis 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
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2019-03-06 16:46 aaroncalero New Issue
2019-03-06 16:46 aaroncalero Assigned To => Retail
2019-03-06 16:46 aaroncalero Triggers an Emergency Pack => No
2019-03-06 17:45 rqueralta Assigned To Retail => rqueralta
2019-03-06 18:29 aaroncalero Steps to Reproduce Updated View Revisions


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker