Project:
| View Revisions: Issue #51222 | [ Back to Issue ] | ||
| Summary | 0051222: scanEvents and selectedLine data is currently persisted in localStorage and never removed | ||
| Revision | 2023-01-13 10:59 by cberner | ||
| Steps To Reproduce | ## Prior, assign some UPC/EAN to a product so it is scaneable 1. Login AWO 2. Go to Count(Inventory Count) and start the counting process 3. Try to scan some items After scan, check in devtools: Application -> LocalStorage -> scanEvents, you should be able to see some events there. Try to complete the inventory count, and see that the events are still there. Also check the selectedLine localstorage property, it gets bigger the more documents you open with a line selected: OB.UTIL.localStorage.getItem('selectedLine'); |
||
| Revision | 2023-01-13 10:59 by cberner | ||
| Description | When we scan an item from Inventory Count or Distribution Order(as examples), a scan event is saved in localStorage under the key "scanEvents". This events are saved per document and are never removed from the local storage, not even when the document has been completed/processed. This will result in problems if the terminal is used long enough, as the localStorage usage will keep growing until it reaches the limit(5MB in chrome). And when that limit is reached, the state persistence will start failing, as it is also saved in local storage. Which might result in application not working properly. Also, when a document is opened and a line is selected, an entry is added to localstorage "selectedLine" property, which only increases and is never removed. |
||
| Revision | 2022-12-22 09:24 by cberner | ||
| Description | When we scan an item from Inventory Count or Distribution Order(as examples), a scan event is saved in localStorage under the key "scanEvents". This events are saved per document and are never removed from the local storage, not even when the document has been completed/processed. This will result in problems if the terminal is used long enough, as the localStorage usage will keep growing until it reaches the limit(5MB in chrome). And when that limit is reached, the state persistence will start failing, as it is also saved in local storage. Which might result in application not working properly. |
||
| Revision | 2022-12-22 09:24 by cberner | ||
| Steps To Reproduce | ## Prior, assign some UPC/EAN to a product so it is scaneable 1. Login AWO 2. Go to Count(Inventory Count) and start the counting process 3. Try to scan some items After scan, check in devtools: Application -> LocalStorage -> scanEvents, you should be able to see some events there. Try to complete the inventory count, and see that the events are still there. |
||
| Revision | 2022-12-21 13:48 by cberner | ||
| Steps To Reproduce | ## Prior, assign some UPC/EAN to a product so it is scaneable 1. Login AWO 2. Go Count(Inventory Count) and start the counting process 3. Try to scan some items After scan, check in devtools: Application -> LocalStorage -> scanEvents, you should be able to see some events there. Try to complete the inventory count, and see that the events are still there. |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |