Openbravo Issue Tracking System - Retail Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0045524Retail ModulesWeb POSpublic2020-11-27 13:162020-12-22 07:25
Reporteravicente 
Assigned ToRetail 
PrioritynormalSeveritymajorReproducibilityalways
StatusclosedResolutionno change required 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned Tomarvintm
OBNetwork customerOBPS
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0045524: The timeout closes the cash up process during last step although user is doing scroll up and down
DescriptionIf I spend more than one minute checking the summary information the cash up provides, a time out session is done (although I move the screen up and down)

Same behaviour when creating a new customer. If the user spends more time that the defined timeout, the session is closed.
Steps To ReproduceCASE 1
1. Log into backend https://livebuilds.openbravo.com/retail_stable_pgsql_pi/ [^]
2. Set the preference 'Web POS Session Timeout' to 1.
3. Log into the terminal https://livebuilds.openbravo.com/retail_stable_pgsql_pi/web/org.openbravo.retail.posterminal/?terminal=VBS-1#login [^]
4. Do a sales.
5. Do cash up until the last step 4 of 4 and do scroll up and down along 1minute (simulation that the user is reviewing the cash up report). Check that the session is closed althoug the scroll.


CASE 2
1. Log into backend https://livebuilds.openbravo.com/retail_stable_pgsql_pi/ [^]
2. Set the preference 'Web POS Session Timeout' to 1.
3. Log into the terminal https://livebuilds.openbravo.com/retail_stable_pgsql_pi/web/org.openbravo.retail.posterminal/?terminal=VBS-1#login [^]
4. Open the form to create a new customer and simulate that the user is entering the customer data.

Proposed SolutionDon't close session during the step 4 of 4 if the user moves the scroll.
Don't close session is a new customer is being created and info is being entered.
Additional Information
TagsNOR
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2020-11-27 13:16avicenteNew Issue
2020-11-27 13:16avicenteAssigned To => Retail
2020-11-27 13:16avicenteOBNetwork customer => OBPS
2020-11-27 13:16avicenteResolution time => 1609369200
2020-11-27 13:16avicenteTriggers an Emergency Pack => No
2020-11-27 13:21avicenteDescription Updatedbug_revision_view_page.php?rev_id=21905#r21905
2020-11-27 13:21avicenteSteps to Reproduce Updatedbug_revision_view_page.php?rev_id=21907#r21907
2020-11-27 13:22avicenteProposed Solution updated
2020-11-27 15:27rafarodaTag Attached: NOR
2020-11-27 15:27rafarodaIssue Monitored: rafaroda
2020-12-22 07:25marvintmReview Assigned To => marvintm
2020-12-22 07:25marvintmNote Added: 0125032
2020-12-22 07:25marvintmStatusnew => closed
2020-12-22 07:25marvintmResolutionopen => no change required

Notes
(0125032)
marvintm   
2020-12-22 07:25   
In general the session is not lost while you are doing activity that triggers requests to the backend. Scrolling up and down doesn't do any request, and therefore the session may be lost if the user only does that, over the whole interval of time that is defined as the standard Tomcat timeout.

This is a standard behaviour in most websites, normally just scrolling in a component will not preserve the session. It would be very complex technically to change, as we would somehow need to "force" a fake request while this is happening, and in our opinion it also doesn't make much sense functionally.

If the user is complaining about this, maybe the session timeout is too short? Because it is hard for me to imagine a user doing this for several minutes?