0035367: Not possible to log in the Web POS if there are resolved errors in the Errors While Importing POS data window

Openbravo Issue Tracking System - Retail Modules

View Issue Details

Project

Category

View Status

Date Submitted

Last Update

0035367

Retail Modules

Web POS

public

2017-02-27 12:33

2017-03-15 08:50

Reporter

marvintm

Assigned To

marvintm

Priority

normal

Severity

major

Reproducibility

always

Status

closed

Resolution

fixed

Platform

OS Version

Product Version

Target Version

RR17Q2

Fixed in Version

RR17Q2

Merge Request Status

Review Assigned To

guilleaer

OBNetwork customer

Support ticket

Regression level

Packaging and release

Regression date

2016-12-06

Regression introduced in release

main

Regression introduced by commit

https://code.openbravo.com/erp/pmods/org.openbravo.retail.posterminal/rev/02c6c8e2af1710fd1ca9e865b55ed7996fe6151a [^]

Triggers an Emergency Pack

Summary

0035367: Not possible to log in the Web POS if there are resolved errors in the Errors While Importing POS data window

Description

Since the change done for this issue: https://issues.openbravo.com/view.php?id=34586, [^] it's no longer possible to log in the Web POS if there are pending errors in the Errors window. This is correct. However, the check also raises in case the errors existed but are now resolved, and this is not correct, as in this case the system is in safe state, and login should be allowed.

Steps To Reproduce

- Log in the Web POS.
- Force a cashup error (for example, add "if(1==1) throw new OBException("Boom");" to the ProcessCashClose.java class).
- Execute the cashup process. Notice that the cashup goes to the Errors While Importing POS data window.
- Clear the cache and try to log in the Web POS. Notice that the following message appears: "Error in previous cashup"
- Remove the code which causes the error.
- Save Again the error in the Window. Notice the error changes to "Saved successfully"
- Try to login in the Web POS again. Notice that the same message appears again. This is not correct.

Proposed Solution

The query should filter by errors in "Error" status.

Additional Information

Tags

No tags attached.

Relationships

depends on	backport	0035368	RR17Q1	closed	marvintm	Not possible to log in the Web POS if there are resolved errors in the Errors While Importing POS data window
caused by	defect	0034586		closed	marvintm	it is posible to create receipts related with processed cashup