Openbravo Issue Tracking System - POS2
View Issue Details
0056923POS2POSpublic2024-10-16 11:082024-11-06 23:15
jfvaringot 
AugustoMauch 
urgentmajoralways
closedfixed 
5
 
24Q4 
No
0056923: Issue on RM-13604 - Short POS Timeout
When the lead time is set to 0 or blank, the behavior of the short time-out is not as desired.



Case 1 :
- Web POS Session Timeout setting : 30s
- Web POS Session Timeout - Alert Lead Time : 0s
- Expected : Log out after 30s, without any alert popup
- Result : Alert message after 45s, telling the deconnection will occur in 0s. No automatic logout.

Case 2 :
- Web POS Session Timeout setting : 30s
- Web POS Session Timeout - Alert Lead Time : N/A
- Expected : Log out after 30s, without any alert popup
- Result : Alert message displayed immediately after the update of the POS, with 120s countdown.
When clicking on 'Stay connected', the countdown is rest to 120s and starts again.
When clicking on 'Disconnect', the user is logged out, but the alert message is still displayed, with the 120s countdown.
Case 1 :
On back office :
- Web POS Session Timeout setting : 30s
- Web POS Session Timeout - Alert Lead Time : 0s

On POS :
- Work on POS
- Wait 30s

Case 2:
On back office :
- Web POS Session Timeout setting : 30s
- Web POS Session Timeout - Alert Lead Time : put nothing

On POS :
- Work on POS
- Wait 30s
No tags attached.
blocks defect 0056798 closed AugustoMauch Issue on RM-13604 - Short POS Timeout 
Issue History
2024-10-29 12:47AugustoMauchTypedefect => backport
2024-10-29 12:47AugustoMauchTarget Version => 24Q4
2024-11-06 22:48hgbotNote Added: 0171590
2024-11-06 22:49hgbotNote Added: 0171591
2024-11-06 23:15hgbotNote Added: 0171592
2024-11-06 23:15hgbotNote Added: 0171593
2024-11-06 23:15hgbotNote Added: 0171594
2024-11-06 23:15hgbotResolutionopen => fixed
2024-11-06 23:15hgbotStatusscheduled => closed
2024-11-06 23:15hgbotFixed in Version => RR24Q4
2024-11-06 23:15hgbotNote Added: 0171595

Notes
(0171590)
hgbot   
2024-11-06 22:48   
Merge Request created: https://gitlab.com/openbravo/product/pmods/org.openbravo.retail.posterminal/-/merge_requests/1762 [^]
(0171591)
hgbot   
2024-11-06 22:49   
Merge Request created: https://gitlab.com/openbravo/product/pmods/org.openbravo.mobile.core/-/merge_requests/767 [^]
(0171592)
hgbot   
2024-11-06 23:15   
Merge request merged: https://gitlab.com/openbravo/product/pmods/org.openbravo.mobile.core/-/merge_requests/767 [^]
(0171593)
hgbot   
2024-11-06 23:15   
Merge request merged: https://gitlab.com/openbravo/product/pmods/org.openbravo.retail.posterminal/-/merge_requests/1762 [^]
(0171594)
hgbot   
2024-11-06 23:15   
Repository: https://gitlab.com/openbravo/product/pmods/org.openbravo.retail.posterminal [^]
Changeset: da549ac13a661d5fa4db6354d24ae4907f9743ed
Author: Augusto Mauch <a.mauch@orisha.com>
Date: 06-11-2024 22:14:20
URL: https://gitlab.com/openbravo/product/pmods/org.openbravo.retail.posterminal/-/commit/da549ac13a661d5fa4db6354d24ae4907f9743ed [^]

Related to ISSUE-56923: Null-valued lead time should be interpreted as 0 lead time

It was initially understood that no defining the timeout lead preference and defining it with a null value should
behave the same way and that the default 2-minute lead time should be used.

That assumption was not proper, if the preference is not defined we should still use the default value,
but if the value is null, it should be set to 0

---
M src/org/openbravo/retail/posterminal/term/Terminal.java
---
(0171595)
hgbot   
2024-11-06 23:15   
Directly closing issue as related merge request is already approved.

Repository: https://gitlab.com/openbravo/product/pmods/org.openbravo.mobile.core [^]
Changeset: 5c6ff11c49a9cd1646ecec8c495adfeb2d77befc
Author: Augusto Mauch <a.mauch@orisha.com>
Date: 06-11-2024 22:49:16
URL: https://gitlab.com/openbravo/product/pmods/org.openbravo.mobile.core/-/commit/5c6ff11c49a9cd1646ecec8c495adfeb2d77befc [^]

Fixes ISSUE-56923: Do not show lead time popover if there is no lead time

If lead time is 0, instead of showing a popover with a countdown, logout immediately once the application
detects that the session should be expired

---
M web/org.openbravo.mobile.core/app/integration/remote-server/BackendServer.js
---