0057872: KIT functionnality has had a regression in the Backoffice and in POS.

Openbravo Issue Tracking System - POS2

View Issue Details

Project

Category

View Status

Date Submitted

Last Update

0057872

POS2

POS

public

2025-02-05 12:59

2025-02-18 11:56

Reporter

nicolasuriz

Assigned To

javierRodriguez

Priority

high

Severity

major

Reproducibility

always

Status

closed

Resolution

fixed

Platform

OS Version

Product Version

Target Version

Fixed in Version

Merge Request Status

Review Assigned To

guilleaer

OBNetwork customer

Support ticket

Regression level

Regression date

Regression introduced in release

Regression introduced by commit

Triggers an Emergency Pack

Summary

0057872: KIT functionnality has had a regression in the Backoffice and in POS.

Description

The KITs are not working anymore. I am going to summarize the problems in Backoffice and POS.

-In the backoffice:
* The validations for fields "Stocked" and "Grouped product" have stopped working and even though you select the Special use for "Kit"
* The tab "Product of the Kit" remains unavailable even though the condition is just to select in the header the Special use "KIT"

-In the POS:
*Even if you add an already existing and well configured Kit with its components, if you add the KIT to the ticket, the components list to add to the ticket in order to proceed to complete the KIT are not displayed anymore.
*If you add an unique component of an specific Kit, the Kit is not added to the ticket.
* If lets you add a component that is present in two different kits without showing the validation where it informs the user that the component cannot be added to the ticket as it is present in more than one different kit.

Steps To Reproduce

Backoffice:

1. Try to create a Kit adding the special Use to KIT and respecting the conditions of a KIT:
1.1 Grouped product cannot be selected to True
1.2 Stocked cannot be checked to True
1.3 Tab "Products of the Kit" is not available

POS:
1. If you had an already two existing kits with one unique component per kit and one component shared between them, do the following test.
1.1 Add one kit to the ticket, check that the components are not displayed
1.2 Add one unique component of one of the kits, the kit is not added to the ticket.
1.3 Add the shared component to the ticket, the validation is not present informing the user that the component cannot be added because it is present in more than one kit and it is removed until the kit itself is added when you could start scanning the component.

Proposed Solution

Additional Information