Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
| ID | ||||||||
| 0056798 | ||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
| defect | [POS2] POS | major | always | 2024-10-16 11:08 | 2024-11-04 11:01 | |||
| Reporter | jfvaringot | View Status | public | |||||
| Assigned To | AugustoMauch | |||||||
| Priority | urgent | Resolution | fixed | Fixed in Version | ||||
| Status | closed | Fix in branch | Fixed in SCM revision | |||||
| Projection | none | ETA | none | Target Version | ||||
| OS | Any | Database | Any | Java version | ||||
| OS Version | Database version | Ant version | ||||||
| Product Version | SCM revision | |||||||
| Review Assigned To | ||||||||
| Regression level | ||||||||
| Regression date | ||||||||
| Regression introduced in release | ||||||||
| Regression introduced by commit | ||||||||
| Triggers an Emergency Pack | No | |||||||
| Summary | 0056798: Issue on RM-13604 - Short POS Timeout | |||||||
| Description | 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. | |||||||
| Steps To Reproduce | 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 | |||||||
| Tags | No tags attached. | |||||||
| Attached Files | ||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
||||||||
|
||||||||
 Relationships |
|
Notes |
|
|
(0171100) hgbot (developer) 2024-10-29 11:12 |
Merge Request created: https://gitlab.com/openbravo/product/pmods/org.openbravo.mobile.core/-/merge_requests/766 [^] |
|
(0171101) hgbot (developer) 2024-10-29 11:15 |
Merge Request created: https://gitlab.com/openbravo/product/pmods/org.openbravo.retail.posterminal/-/merge_requests/1744 [^] |
|
(0171280) hgbot (developer) 2024-11-04 11:01 |
Repository: https://gitlab.com/openbravo/product/pmods/org.openbravo.retail.posterminal [^] Changeset: 35a32c5195f7a2910245abec0b42f4ea67e1ffb8 Author: Augusto Mauch <a.mauch@orisha.com> Date: 04-11-2024 10:00:11 URL: https://gitlab.com/openbravo/product/pmods/org.openbravo.retail.posterminal/-/commit/35a32c5195f7a2910245abec0b42f4ea67e1ffb8 [^] Related to ISSUE-56798: 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 --- |
|
(0171281) hgbot (developer) 2024-11-04 11:01 |
Merge request merged: https://gitlab.com/openbravo/product/pmods/org.openbravo.retail.posterminal/-/merge_requests/1744 [^] |
|
(0171282) hgbot (developer) 2024-11-04 11:01 |
Directly closing issue as related merge request is already approved. Repository: https://gitlab.com/openbravo/product/pmods/org.openbravo.mobile.core [^] Changeset: 5d0cd10df84d392e690a6cbbf720213a6ac2a608 Author: Augusto Mauch <a.mauch@orisha.com> Date: 04-11-2024 10:00:09 URL: https://gitlab.com/openbravo/product/pmods/org.openbravo.mobile.core/-/commit/5d0cd10df84d392e690a6cbbf720213a6ac2a608 [^] Fixes ISSUE-56798: 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 --- |
|
(0171283) hgbot (developer) 2024-11-04 11:01 |
Merge request merged: https://gitlab.com/openbravo/product/pmods/org.openbravo.mobile.core/-/merge_requests/766 [^] |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2024-10-16 11:08 | jfvaringot | New Issue | |
| 2024-10-16 11:08 | jfvaringot | Assigned To | => Retail |
| 2024-10-16 11:08 | jfvaringot | Triggers an Emergency Pack | => No |
| 2024-10-17 06:49 | guillermogil | Assigned To | Retail => Triage Platform Base |
| 2024-10-29 11:12 | hgbot | Note Added: 0171100 | |
| 2024-10-29 11:15 | hgbot | Note Added: 0171101 | |
| 2024-10-29 12:26 | AugustoMauch | Assigned To | Triage Platform Base => AugustoMauch |
| 2024-10-29 12:47 | AugustoMauch | Status | new => scheduled |
| 2024-10-29 12:47 | AugustoMauch | Status | scheduled => resolved |
| 2024-10-29 12:47 | AugustoMauch | Resolution | open => fixed |
| 2024-10-29 12:47 | AugustoMauch | Status | resolved => new |
| 2024-10-29 12:47 | AugustoMauch | Resolution | fixed => open |
| 2024-10-29 12:47 | AugustoMauch | Status | new => scheduled |
| 2024-11-04 11:01 | hgbot | Note Added: 0171280 | |
| 2024-11-04 11:01 | hgbot | Note Added: 0171281 | |
| 2024-11-04 11:01 | hgbot | Resolution | open => fixed |
| 2024-11-04 11:01 | hgbot | Status | scheduled => closed |
| 2024-11-04 11:01 | hgbot | Fixed in Version | => RR25Q1 |
| 2024-11-04 11:01 | hgbot | Note Added: 0171282 | |
| 2024-11-04 11:01 | hgbot | Note Added: 0171283 | |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |