0052627: Pos 2: promotions wrongly configured block the access to the WebPOS

Openbravo Issue Tracking System - Retail Modules

View Issue Details

Project

Category

View Status

Date Submitted

Last Update

0052627

Retail Modules

Discounts and Promotions

public

2023-05-31 09:29

2023-07-11 14:32

Reporter

noemieroussel

Assigned To

ranjith_qualiantech_com

Priority

high

Severity

major

Reproducibility

have not tried

Status

closed

Resolution

fixed

Platform

OS Version

Product Version

Target Version

RR23Q2.2

Fixed in Version

Merge Request Status

Review Assigned To

OBNetwork customer

Support ticket

Regression level

Packaging and release

Regression date

2022-10-04

Regression introduced in release

RR22Q4

Regression introduced by commit

https://gitlab.com/openbravo/product/pmods/org.openbravo.mobile.core/-/commit/d6a1d4f03f0a48eaa5793b783e45ce3c70c13f5e [^]

Triggers an Emergency Pack

Summary

0052627: Pos 2: promotions wrongly configured block the access to the WebPOS

Description

When we configure a promotion wrongly, the expected behavior is to have an error message in Back Office when activating a promotion where a mandatory filter is missing (for Combo for example, the error occurs when there is no record registered in Family subtab), but not in the WEBPOS.

If I configure a promotion with an error or a missing filter, I should still be able to log in to WebPOS and do a sale, and the promotion that is not correctly set up will not be available.

We need to know which configuration can cause this blocking error.

Steps To Reproduce

Go to the backoffice

Create a new record in "Discounts and Promotions" : a Combo promotion without adding family. Set it as active.

Try to enter in the WebPOS. -> POS can't be opened

Then, go to the backoffice and deactivate the promotion.

Go to the POS and refresh, see that POS is now accesible.

Go to the backoffice and activate the promotion.

Go to the POS and refresh, see that POS is now unaccesible.

Proposed Solution

We need to know which configuration can cause this blocking error.

Additional Information