Openbravo Issue Tracking System - POS2
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0045620POS2Restaurantspublic2020-12-17 11:142020-12-29 16:54
ReporterAugustoMauch 
Assigned ToAugustoMauch 
PrioritynormalSeveritymajorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Version 
Target VersionFixed 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 PackNo
Summary0045620: Autodiscovery menu process not working properly for menu that contain grouped categories
Description The autodiscovery process is not working properly when the menu built automatically contain grouped categories. When storing the menu meta data in the ticket, the group ids are being stored instead of the menu category ids.

As a result, the menu is shown as not completed, and when paid it will show wrong data on the ERP.
Steps To ReproduceCreate a menu with this configuration in the ERP:
- One group, min=max=2
- Two categories, both belong to the group created in the previous step
- Each category contains two menu items (i.e. category 1 contains Cesar Salad, Onion Soup, category 2 contains Cheeseburger, carbonara pizza)

Open webpos, and add the following two items:
- Cesar Salad
- Carbonara Pizza

An instance for the grouped menu will be created, but it will not be shown properly (see attached screenshots)
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
has duplicate defect 0045455 closed Retail Import error for order with an auto-completed menu 
Attached Filespng ExpectedGroupedMenu.png (32,067) 2020-12-17 11:16
https://issues.openbravo.com/file_download.php?file_id=15182&type=bug
png

png WrongGroupedMenu.png (34,015) 2020-12-17 11:16
https://issues.openbravo.com/file_download.php?file_id=15183&type=bug
png
Issue History
Date ModifiedUsernameFieldChange
2020-12-17 11:14AugustoMauchNew Issue
2020-12-17 11:14AugustoMauchAssigned To => AugustoMauch
2020-12-17 11:14AugustoMauchTriggers an Emergency Pack => No
2020-12-17 11:14AugustoMauchIssue generated from0045619
2020-12-17 11:16AugustoMauchFile Added: ExpectedGroupedMenu.png
2020-12-17 11:16AugustoMauchFile Added: WrongGroupedMenu.png
2020-12-17 14:47AugustoMauchRelationship addedhas duplicate 0045455
2020-12-18 12:17hgbotResolutionopen => fixed
2020-12-18 12:17hgbotStatusnew => resolved
2020-12-18 12:17hgbotNote Added: 0124936
2020-12-29 16:54AugustoMauchStatusresolved => closed

Notes
(0124936)
hgbot   
2020-12-18 12:17   
Repository: https://gitlab.com/openbravo/product/pmods/org.openbravo.retail.restaurant [^]
Changeset: f5d3c9603745f66466c120046416b801a2d76d2c
Author: Augusto Mauch <augusto.mauch@openbravo.com>
Date: 2020-12-18T12:16:39+01:00
URL: https://gitlab.com/openbravo/product/pmods/org.openbravo.retail.restaurant/-/commit/f5d3c9603745f66466c120046416b801a2d76d2c [^]

Fixes issue 45620, menus that use grouped categories are properly autodiscovered

Now the category id stored on the ticket meta data is proper, instead of being sometimes
the id of the menu group

---
M web-jspack/org.openbravo.retail.restaurant/src/model/ticket/actions/AddProductActionPreparation.js
---