Project:
| View Revisions: Issue #53414 | [ Back to Issue ] | ||
| Summary | 0053414: If a master data refresh fails, the next time the user logs in, the refresh should be repeated | ||
| Revision | 2023-09-11 09:05 by AugustoMauch | ||
| Description | The following case is theoretically possible: - When the user logs in, conditions are met so that the full/incremental master data refresh takes place - Something goes wrong during that master data refresh, the process ends in error when only some of the models have been updated, user is logged out - Next time the user logs in, conditions to do a full/incremental master data refresh are not met, so user logs in in the application having potentially inconsistent data due to the failed refresh. We can be sure that of the reasons that trigger a refresh will still be met the next time the user logs in if the previous refreshed failed, i.e. the master data refresh timeout. But we cannot be sure about others (i.e. there are several ways to do forced updates). The current implementations already tries to force the masterdata to be refreshed in case the latest one failed [1], but that mechanism will not be triggered To prevent this problem, we have to ensure that regardless of other conditions are met, if a previous master data refreshed failed, the next time the user logs in the master data refresh is restarted if the browser failed or if the tab was closed before reaching that line. [1] https://gitlab.com/openbravo/product/pmods/org.openbravo.mobile.core/-/blob/master/web/org.openbravo.mobile.core/app/model/masterdata/MasterdataController.js#L140 [^] |
||
| Revision | 2023-09-07 13:36 by AugustoMauch | ||
| Description | The following case is theoretically possible: - When the user logs in, conditions are met so that the full/incremental master data refresh takes place - Something goes wrong during that master data refresh, the process ends in error when only some of the models have been updated, user is logged out - Next time the user logs in, conditions to do a full/incremental master data refresh are not met, so user logs in in the application having potentially inconsistent data due to the failed refresh. We can be sure that of the reasons that trigger a refresh will still be met the next time the user logs in if the previous refreshed failed, i.e. the master data refresh timeout. But we cannot be sure about others (i.e. there are several ways to do forced updates). To prevent this problem, we have to ensure that regardless of other conditions are met, if a previous master data refreshed failed, the next time the user logs in the master data refresh is restarted |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |