Project:
| View Revisions: Issue #56978 | [ Back to Issue ] | ||
| Summary | 0056978: Full refresh is not executed when one masterdata model changed | ||
| Revision | 2024-11-05 13:57 by malsasua | ||
| Steps To Reproduce | . do login in POS . do cashup . do logout (no close Chrome tab) . compile adding one property in one masterdata model (for react, you can apply the patch attached in the posterminal module) . do login in POS -> full refresh is not executed . do logout . refresh brower . do login -> full refresh is executed |
||
| Revision | 2024-11-05 13:57 by malsasua | ||
| Description | After one deploy that modifying one masterdata model, if the login page is not refreshed, the first login is not triggering a full refresh The problem is reproducible in react and enyo. |
||
| Revision | 2024-11-05 12:54 by malsasua | ||
| Steps To Reproduce | . do login in POS . do cashup . do logout (no close Chrome tab) . compile adding one property in one masterdata model (you can apply the patch attached in the posterminal module) . do login in POS -> full refresh is not executed . do logout . refresh brower . do login -> full refresh is executed |
||
| Revision | 2024-11-05 12:54 by malsasua | ||
| Description | After one deploy that modifying one masterdata model, if the login page is not refreshed, the first login is not triggering a full refresh | ||
| Copyright © 2000 - 2009 MantisBT Group |
 |