0056263: Mitigation https://issues.openbravo.com/view.php?id=52070 should not create a new cashup in POS

Openbravo Issue Tracking System - Retail Modules

View Issue Details

Project

Category

View Status

Date Submitted

Last Update

0056263

Retail Modules

Web POS

public

2024-08-14 11:35

2024-11-19 11:16

Reporter

malsasua

Assigned To

ranjith_qualiantech_com

Priority

high

Severity

major

Reproducibility

always

Status

closed

Resolution

fixed

Platform

OS Version

Product Version

Target Version

Fixed in Version

RR24Q4

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

0056263: Mitigation https://issues.openbravo.com/view.php?id=52070 [^] [https://issues.openbravo.com/view.php?id=52070 [^]] should not create a new cashup in POS

Description

In the mitigation created by the issue
https://issues.openbravo.com/view.php?id=52070 [^]
during the login, if the cashup stored in local DB is processed in BO, the mitigation is creating a new cashup in local DB
But, sometimes, a cashup not processed can exist in the BO. But a new cashup is created in POS, then, when this cashup is synced to BO, there are 2 cashups with processed='N' in the BO
When the last cashup is completed in POS, a EWI is raised:
Previous cashup entries should be processed before processing the current cashup entry

Steps To Reproduce

n/a

Proposed Solution

the mitigation https://issues.openbravo.com/view.php?id=52070 [^]
instead of create a new cashup in POS, the system should check if exists another cashup not processed in the BO.
If exists, then it should be sent to POS instead of create a new cashup

Additional Information

Tags

No tags attached.

Relationships

related to	backport	0052070	23Q2	closed	meriem_azaf	POS2	Cashup mitigation: do not check if current cashup is the last one processed, just check if it is processed
related to	feature request	0056377		scheduled	AugustoMauch	POS2	Management of inconsistent application state should be properly addressed in core2 applications
depends on	backport	0056360	RR24Q3.1	closed	ranjith_qualiantech_com	Retail Modules	Mitigation https://issues.openbravo.com/view.php?id=52070 [^] should not create a new cashup in POS
depends on	backport	0056361	RR24Q2.3	closed	ranjith_qualiantech_com	Retail Modules	Mitigation https://issues.openbravo.com/view.php?id=52070 [^] should not create a new cashup in POS