Project:
| View Revisions: Issue #51822 | [ All Revisions ] [ Back to Issue ] | ||
| Summary | 0051822: If localStorage does not have latest safebox information, updated it with the information stored in the backend | ||
| Revision | 2023-03-21 09:34 by meriem_azaf | ||
| Description | Sometimes, the information about currently attached safebox is not up to date on localStorage (root cause of this will be addressed in another issue). When that happens, we could start the POS: - assuming that a safebox is attached, when it has already been removed, or - assuming that there is no safebox attached, when one is currently in the POS We are going to assume that the backend will always have the most up to date information, so when login in we will: - make a request to the backend to check if the terminal has currently a safebox attached - use that information to update the localStorage |
||
| Revision | 2023-03-21 09:30 by meriem_azaf | ||
| Description | We have demonstarted that this problem happens because a problem with the state persistance. While we find a solution for this problem we should be able to develop a mitigation fix which: 1. Detects that a safebos which is not attached in the backoffice looks attacahed for POS 2. Remove safe box from the POS -> It will force users to select the safebox Note: Usually this issue happens together with the problem of cashup (Working with a cashup which already exists" |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |