Openbravo Issue Tracking System - Retail Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0031598Retail ModulesWeb POSpublic2015-11-26 11:492015-12-14 12:17
Reporterkchoperena 
Assigned ToRetail 
PriorityhighSeveritymajorReproducibilityalways
StatusclosedResolutionno change required 
PlatformOS30OS VersionProfessional Appliance
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned ToOrekaria
OBNetwork customer
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0031598: [SERQA 433] The product has been added to the ticket although the time out was expired
DescriptionThe product has been added to the ticket although the time out was expired.
Steps To Reproduce1.Login in the Web POS and open the browse.
2.Wait the timeout.
3.After timeout expiration, add a product to the ticket. The look screen is done automatically.
4.Login with the same user as in step 1.
Proposed Solution
Additional Information
TagsSER-QA
Relationships
depends on feature request 0031689RR16Q1 closed Retail The terminal should auto-lock when no activity is detected 
Attached Filespng SeesionExpired.png (174,069) 2015-12-07 19:37
https://issues.openbravo.com/file_download.php?file_id=8786&type=bug
png
Issue History
Date ModifiedUsernameFieldChange
2015-11-26 11:49kchoperenaNew Issue
2015-11-26 11:49kchoperenaAssigned To => Retail
2015-11-26 11:49kchoperenaResolution time => 1449702000
2015-11-26 11:49kchoperenaTriggers an Emergency Pack => No
2015-11-26 12:02OrekariaStatusnew => acknowledged
2015-12-01 10:26ageteTag Attached: SER-QA
2015-12-01 10:26ageteSummaryThe product has been added to the ticket although the time out was expired => [433] The product has been added to the ticket although the time out was expired
2015-12-01 11:04ageteSummary[433] The product has been added to the ticket although the time out was expired => [SERQA433] The product has been added to the ticket although the time out was expired
2015-12-07 19:35OrekariaStatusacknowledged => scheduled
2015-12-07 19:37OrekariaReview Assigned To => Orekaria
2015-12-07 19:37OrekariaNote Added: 0082600
2015-12-07 19:37OrekariaStatusscheduled => closed
2015-12-07 19:37OrekariaResolutionopen => no change required
2015-12-07 19:37OrekariaFile Added: SeesionExpired.png
2015-12-10 13:29OrekariaRelationship addeddepends on 0031689
2015-12-14 12:17ageteSummary[SERQA433] The product has been added to the ticket although the time out was expired => [SERQA 433] The product has been added to the ticket although the time out was expired

Notes
(0082600)
Orekaria   
2015-12-07 19:37   
The application is working as expected.
Create a new feature request in case that another functionality is expected

Please see this notes:

Currently, the Web POS only detects that the session has expired when the user triggers a functionality which requires online operation. This includes completing a receipt, or looking for previous receipts.

However, there are a significant number of features which do not currently require online operation, such as adding a product to the receipt, adding a discretionary discount, returning a line, ... None of these operations will do a request to the backend, so in none of these cases the Web POS will detect that the session has expired. Please take into account that the message is reporting that the "session timed out" and that "Your pending tickets will be saved".

This is usually not a problem for our current customers because as completing a receipt is an authenticated operation, it's always mandatory to validate the session before the changes are finally persisted and sent to the backend.

This is the way this functionality was designed, and it is how it works, and it's not easy at all to change it. In our opinion, if BUT needs a different behavior, then it should be logged as a feature request, and we should discuss how to implement it.