0053326: When doing a master data refresh, a terminal log message should explain why it was triggered

Openbravo Issue Tracking System - Retail Modules

View Issue Details

Project

Category

View Status

Date Submitted

Last Update

0053326

Retail Modules

Web POS

public

2023-08-30 09:07

2023-09-07 11:05

Reporter

AugustoMauch

Assigned To

AugustoMauch

Priority

normal

Severity

minor

Reproducibility

have not tried

Status

closed

Resolution

fixed

Platform

OS Version

Product Version

Target Version

Fixed in Version

RR23Q4

Merge Request Status

Review Assigned To

OBNetwork customer

Support ticket

Regression level

Regression date

Regression introduced in release

Regression introduced by commit

Triggers an Emergency Pack

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

Proposed Solution

Additional Information