0050337: Visibility of state persistence problems should be increased

Openbravo Issue Tracking System - POS2

View Issue Details

Project

Category

View Status

Date Submitted

Last Update

0050337

POS2

POS

public

2022-09-26 14:59

2022-09-27 14:54

Reporter

AugustoMauch

Assigned To

AugustoMauch

Priority

normal

Severity

major

Reproducibility

random

Status

closed

Resolution

fixed

Platform

OS Version

Product Version

Target Version

22Q3.1

Fixed in Version

22Q3.1

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

0050337: Visibility of state persistence problems should be increased

Description

In order to properly research the state persistence problems that seem to be happening in some tills, it would be very useful to add some log to check if the application state is being persisted properly.

The idea is that after a ticket or a cashup is completed, we will force the state to be persisted and then we will check if the persisted state is the one we expect.

Steps To Reproduce

Root cause of the problem:
- Complete a cashup
- Sometimes the cashup will not be properly persisted and the next time the user logs in, the previous version of the cashup is used.

Proposed Solution

Additional Information