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

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0052493
TypeCategorySeverityReproducibilityDate SubmittedLast Update
backport[POS2] POSmajorhave not tried2023-05-17 12:542023-05-19 13:32
ReportercbernerView Statuspublic 
Assigned Tocberner 
PrioritynormalResolutionno change requiredFixed in Version
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version23Q1.3
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned Tocberner
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0052493: Session timeout dialog bypass pos2 blocked application

DescriptionWhen 2 pos2 are open in different tabs/windows, one of them is marked as blocked and we shouldn't be able to use it until it is refreshed.

This can be bypassed by the session timeout dialog, which appears after the set period of time for the session to expire and allows us to login again and work with an incorrect state.
Steps To Reproduce1. Setup a small session timeout by going to backoffice -> Preferences. Add a new record with property Web POS Session Timeout of 3 mins for example, and mark it as selected and visible to all users.
2. Login WebPOS
3. Open in another tab the same WebPOS and complete a ticket in this one
4. Go back to the other tab and wait for session timeout to happen, then login again
5. After logging in, a duplicate ticket error appears as part of the console and terminal log, this shows us that we're using the incorrect state.
Proposed SolutionDon't allow dialogUIHandler dialogs to appear on a blocked terminal.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
blocks defect 0052468 closedcberner Session timeout dialog bypass pos2 blocked application 

-  Notes
(0149980)
cberner (developer)
2023-05-19 13:32

BrowserTab.js for core2 does not exist in 23Q1, so the backport will not be done.

- Issue History
Date Modified Username Field Change
2023-05-19 12:59 AugustoMauch Type defect => backport
2023-05-19 12:59 AugustoMauch Target Version => 23Q1.3
2023-05-19 13:32 cberner Review Assigned To => cberner
2023-05-19 13:32 cberner Note Added: 0149980
2023-05-19 13:32 cberner Status scheduled => closed
2023-05-19 13:32 cberner Resolution open => no change required


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker