Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
| ID | ||||||||
| 0053326 | ||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
| feature request | [Retail Modules] Web POS | minor | have not tried | 2023-08-30 09:07 | 2023-09-07 11:05 | |||
| Reporter | AugustoMauch | View Status | public | |||||
| Assigned To | AugustoMauch | |||||||
| Priority | normal | Resolution | fixed | Fixed in Version | RR23Q4 | |||
| 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 | 0053326: When doing a master data refresh, a terminal log message should explain why it was triggered | |||||||
| Description | A full master data refresh will be triggered when a user logs in and: - it is the first login in that terminal, or after the cache was cleaned - the full refresh timeout has expired An incremental data refresh will be triggered when: - the incremental refresh timeout has expired. - the user forces an incremental masterdata refresh Sometimes we find in production that a master data refresh was triggered without being clear what triggered that refresh. A terminal log message should be written, explaining what triggered it. If it was because the timeout was expired, the timeout and the last time the full/incremental refresh took place should be included in the message | |||||||
| Steps To Reproduce | After cleaning cache in the browser: - Log in the POS - Check that a full refresh takes place * A terminal log message should notify that a full refresh should be done because there is no local master data - Log out - Wait until the full refresh timeout expires (defining a small value for it and a big value for the incremental refresh timeout will help) - Log in again * A terminal log message should notify that a full refresh should be done because its timeout expired, including the timeout and the datetime of the last time the full refresh took place - Wait until the incremental refresh timeout expires (defining a small value for it and a big value for the full refresh timeout will help) - Log in again * A terminal log message should notify that an incremental refresh should be done because its timeout expired, including the timeout and the datetime of the last time the incremental refresh took place - Force an incremental masterdata refresh * A terminal log message should notify that an incremental refresh should be done because the user forced it | |||||||
| Tags | No tags attached. | |||||||
| Attached Files | ||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|||||||||
|
|||||||||
 Relationships |
|
Notes |
|
|
(0154336) hgbot (developer) 2023-09-01 11:10 |
Merge Request created: https://gitlab.com/openbravo/product/pmods/org.openbravo.mobile.core/-/merge_requests/602 [^] |
|
(0154551) hgbot (developer) 2023-09-06 15:31 |
Merge request merged: https://gitlab.com/openbravo/product/pmods/org.openbravo.mobile.core/-/merge_requests/602 [^] |
|
(0154552) hgbot (developer) 2023-09-06 15:31 |
Directly closing issue as related merge request is already approved. Repository: https://gitlab.com/openbravo/product/pmods/org.openbravo.mobile.core [^] Changeset: 51b05764400e6271c5a55847d933bd9cb27d3bf0 Author: Augusto Mauch <augusto.mauch@openbravo.com> Date: 06-09-2023 15:30:12 URL: https://gitlab.com/openbravo/product/pmods/org.openbravo.mobile.core/-/commit/51b05764400e6271c5a55847d933bd9cb27d3bf0 [^] Fixes ISSUE-53326: Adds log explaining why master data refresh process was triggered --- M web/org.openbravo.mobile.core/app/model/masterdata/MasterdataController.js M web/org.openbravo.mobile.core/source/model/ob-terminal-model.js --- |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2023-08-30 09:07 | AugustoMauch | New Issue | |
| 2023-08-30 09:07 | AugustoMauch | Assigned To | => Retail |
| 2023-08-30 09:07 | AugustoMauch | Triggers an Emergency Pack | => No |
| 2023-08-30 09:08 | AugustoMauch | Assigned To | Retail => AugustoMauch |
| 2023-08-30 09:08 | AugustoMauch | Status | new => scheduled |
| 2023-08-31 15:07 | AugustoMauch | Summary | When doing a master data refresh, a terminal log message should explain what triggered => When doing a master data refresh, a terminal log message should explain why it was triggered |
| 2023-09-01 11:10 | hgbot | Note Added: 0154336 | |
| 2023-09-06 15:31 | hgbot | Resolution | open => fixed |
| 2023-09-06 15:31 | hgbot | Status | scheduled => closed |
| 2023-09-06 15:31 | hgbot | Note Added: 0154551 | |
| 2023-09-06 15:31 | hgbot | Fixed in Version | => RR23Q4 |
| 2023-09-06 15:31 | hgbot | Note Added: 0154552 | |
| 2023-09-07 11:05 | rafaroda | Relationship added | related to 0052812 |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |