Openbravo Issue Tracking System - Retail Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0027790Retail ModulesWeb POSpublic2014-10-07 17:522014-10-15 13:21
Reporterjecharri 
Assigned Tomarvintm 
PriorityurgentSeveritymajorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Version 
Target VersionFixed in VersionRR15Q1 
Merge Request Status
Review Assigned Tomigueldejuana
OBNetwork customerOBPS
Support ticket31493
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0027790: Web POS session are going to expire after the Ping has disappear
DescriptionWeb POS session are going to expire after the Ping has disappeared.

Openbravo can configure sessions expiration date using record "timeout" in window "AD Implementation mapping". This parameter will say to our users that if they don't have any activity in X minutes the session is not going to be valid any more.

Before the ping was removed, it was impossible to be able to reach this time because the ping was creating this activity to avoid that session could be without activity longer than Y seconds.
Steps To Reproduce-login as "sytem administrator"
-go to "AD Implementation mapping"
-select record "timeout" and change the search key to 2
-stop tomcat and compile with ant smartbuild
-start tomcat

-login to Web POS
-don't do anything during more than 2 minutes
-after that create an order
-verify that system thinks that you are offline and ask again to do the login
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2014-10-07 17:52jecharriNew Issue
2014-10-07 17:52jecharriAssigned To => marvintm
2014-10-07 17:52jecharriOBNetwork customer => Yes
2014-10-07 17:52jecharriSupport ticket => 31493
2014-10-07 17:52jecharriResolution time => 1415574000
2014-10-07 17:52jecharriTriggers an Emergency Pack => No
2014-10-07 20:48hgbotCheckin
2014-10-07 20:48hgbotNote Added: 0070784
2014-10-07 20:48hgbotStatusnew => resolved
2014-10-07 20:48hgbotResolutionopen => fixed
2014-10-07 20:48hgbotFixed in SCM revision => http://code.openbravo.com/erp/pmods/org.openbravo.retail.posterminal/rev/12d0d52e01faf203ee11fd5f7f9435ce8405600d [^]
2014-10-10 11:39migueldejuanaReview Assigned To => migueldejuana
2014-10-10 11:39migueldejuanaNote Added: 0070866
2014-10-10 11:39migueldejuanaStatusresolved => closed
2014-10-10 11:39migueldejuanaFixed in Version => RR15Q1
2014-10-15 13:21hgbotCheckin
2014-10-15 13:21hgbotNote Added: 0070956

Notes
(0070784)
hgbot   
2014-10-07 20:48   
Repository: erp/pmods/org.openbravo.retail.posterminal
Changeset: 12d0d52e01faf203ee11fd5f7f9435ce8405600d
Author: Antonio Moreno <antonio.moreno <at> openbravo.com>
Date: Tue Oct 07 20:48:05 2014 +0200
URL: http://code.openbravo.com/erp/pmods/org.openbravo.retail.posterminal/rev/12d0d52e01faf203ee11fd5f7f9435ce8405600d [^]

Fixed issue 27790. Changed the way Web POS sessions expire.
- Now sessions will no longer expire by default if the browser is logged in the Web POS (they still expire if logged out of the application).
- There is a new preference which allows the user to change this behavior, so that the session will expire as configured in the standard Tomcat timeout property (configured in AD Model Implementation window, in the 'Timeout' record).

---
M src-db/database/sourcedata/AD_REF_LIST.xml
M src/org/openbravo/retail/posterminal/term/Terminal.java
M web/org.openbravo.retail.posterminal/js/login/model/login-model.js
---
(0070866)
migueldejuana   
2014-10-10 11:39   
Tested and reviewed in 9f470354180c
(0070956)
hgbot   
2014-10-15 13:21   
Repository: erp/pmods/org.openbravo.retail.posterminal
Changeset: 7994ab8c2d0254f851b732ef8dd25cc49a415278
Author: Antonio Moreno <antonio.moreno <at> openbravo.com>
Date: Wed Oct 15 13:21:34 2014 +0200
URL: http://code.openbravo.com/erp/pmods/org.openbravo.retail.posterminal/rev/7994ab8c2d0254f851b732ef8dd25cc49a415278 [^]

Related to issue 27790. Clarified what the preference actually does in the name

---
M src-db/database/sourcedata/AD_REF_LIST.xml
---