Openbravo Issue Tracking System - POS2 | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0057356 | POS2 | Fashion | public | 2024-12-03 17:17 | 2024-12-04 14:51 |
| Reporter | philippe_mui | ||||
| Assigned To | guilleaer | ||||
| Priority | high | Severity | major | Reproducibility | always |
| Status | acknowledged | Resolution | open | ||
| Platform | OS | 5 | OS Version | ||
| Product Version | |||||
| Target Version | Fixed in Version | ||||
| 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 | No | ||||
| Summary | 0057356: RM-19593 Pos 2: promotions wrongly configured block the access to the WebPOS | ||||
| Description | This was supposed to be solved with https://issues.openbravo.com/view.php?id=52618 [^] but it is still KO in 24Q4. https://openbravo.atlassian.net/browse/RM-19593 [^] 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 | |||||
| Tags | FASH | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2024-12-03 17:17 | philippe_mui | New Issue | |||
| 2024-12-03 17:17 | philippe_mui | Assigned To | => Retail | ||
| 2024-12-03 17:17 | philippe_mui | Triggers an Emergency Pack | => No | ||
| 2024-12-03 17:17 | philippe_mui | Tag Attached: FASH | |||
| 2024-12-04 14:51 | guilleaer | Assigned To | Retail => guilleaer | ||
| 2024-12-04 14:51 | guilleaer | Status | new => acknowledged | ||
| There are no notes attached to this issue. |