Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0048791
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[POS2] Restaurantsmajoralways2022-03-14 18:322022-05-17 17:29
Reportertimothee_catteeuwView Statuspublic 
Assigned Tomeriem_azaf 
PrioritynormalResolutionopenFixed in Version
StatusscheduledFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0048791: JIRA 2763 - Error message too quickly displayed when modifiers selection have no default value

DescriptionIn that context for example (cf. screen shot without error message)

- Type de cuisson has a default value, and the selection of 1 value is necessary

- Ingredient has no default value and requires at least the selection of 1 value


if I press "saignant", an error message is displayed (cf. other screenshot)

it is caused by ingredients list because :

- this list has no default value

- it is mandatory to select at least one value of modifiers group. Otherwise it is not possible to move forward.

Steps To ReproduceSteps to reproduce :
1) go to BO
2) create 2 modifiers groups
3) for the 1st,min and max selection equals to 1
4) for the second, min selection = 1 and mas selection = 3
5) link a product to both modifiers
6) go to webpos
7) Select the product
8) select a value different than the default value for the 1st modifier
--> a message appears too soon --> Select at least one option
Proposed SolutionActually the problem happens due to the validation of the modifier group constraints.

Taking the above example, we have 2 modifier groups

Group 1:

    Minimum (of selected options) 1
    Maximum (of selected options) 1

    Option 1 - Default value
    Option 2 -
    Option 3 -

Group 2:

    Minimum (of selected options) 1
    Maximum (of selected options) 3

    Option 1 -
    Option 2 -
    Option 3 -

------------------------------------------------

Once the product configuration window is displayed, it is divided into the corresponding 2 groups, but the validations (which are executed in case of any change in any of the modifiers) are performed on ALL the different modifiers (regardless of the group), so when the modification or configuration is performed on any of the modifiers of the first group, the validation is performed for the first group as for the second one (which does not comply with its configuration and the message is displayed).

------------------------------------------------

Therefore, the following 2 solutions are proposed:

-----

SOLUTION 1:

1.- Internally divide the modifiers window into 2 different forms (in case of having X groups, divide them into X forms).

2.- Once a modifier has been selected. Perform the validations of the modifiers on the form to which it belongs (independently of the rest).

(This way we could, also, be able to show more 'accurate' error messages in the groups where the requirements are not fulfilled).
(This way we would avoid error messages for modifier groups that have not yet been selected).

-----

SOLUTION 2:

1.- Perform validations/verification of modifier groups when the 'Finish' button is pressed (which is currently disabled because the requirements are not met).

-----

Forced solution:

1.- That all modifier groups have 1 default value set.
TagsNo tags attached.
Attached Filespng file icon image-2022-03-14-18-12-55-081.png [^] (21,479 bytes) 2022-03-14 18:33


png file icon image-2022-03-14-18-13-43-663.png [^] (25,400 bytes) 2022-03-14 18:33

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
(0136952)
guilleaer (manager)
2022-05-04 17:24

We have sttoped to work on it because solution looks complex and now this is not a priority. As a workaround a default option should be selected

- Issue History
Date Modified Username Field Change
2022-03-14 18:32 timothee_catteeuw New Issue
2022-03-14 18:32 timothee_catteeuw Assigned To => Retail
2022-03-14 18:32 timothee_catteeuw Triggers an Emergency Pack => No
2022-03-14 18:33 timothee_catteeuw File Added: image-2022-03-14-18-12-55-081.png
2022-03-14 18:33 timothee_catteeuw File Added: image-2022-03-14-18-13-43-663.png
2022-04-21 15:04 sntgreale Assigned To Retail => sntgreale
2022-04-21 15:04 sntgreale Status new => acknowledged
2022-04-22 04:11 sntgreale Status acknowledged => scheduled
2022-05-04 17:23 guilleaer Assigned To sntgreale => Retail
2022-05-04 17:23 guilleaer Status scheduled => acknowledged
2022-05-04 17:24 guilleaer Note Added: 0136952
2022-05-04 20:18 sntgreale Proposed Solution updated
2022-05-04 20:24 sntgreale Proposed Solution updated
2022-05-04 20:24 sntgreale Proposed Solution updated
2022-05-17 15:47 AugustoMauch Assigned To Retail => meriem_azaf
2022-05-17 17:29 AugustoMauch Status acknowledged => scheduled


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker