Openbravo Issue Tracking System - POS2
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0052449POS2POSpublic2023-05-15 14:382023-05-17 10:18
Reporterjayala 
Assigned Tojayala 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Version 
Target Version23Q2.1Fixed in Version23Q2.1 
Merge Request Statusapproved
Review Assigned To
OBNetwork customerNo
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0052449: Open ticket with correct schema
DescriptionWhen you open a ticket with a different schema or delivery mode than the terminal, the POS system should try to select it in order to display it correctly. If it cannot do so because it is not configured in the terminal, it should open it using the default schema. In either of these two cases, a small pop-up will be displayed with a warning indicating this anomaly to the user.
Steps To Reproduce1. Search for a ticket which has the field "obpos2OrgSchema" filled.
2. Open the order.
3. See that order is opened but not in the schema indicated for the order.
Proposed SolutionIt has been noticed that the current development did not take into account the deliveryModeSelection === 'A' (All) for the schema 'calculation,' so it is being added. Furthermore, the developed logic is the opposite. If deliveryModeSelection === 'I', the schema should be included, and if deliveryModeSelection === 'E', the schema should be excluded.
Additional Information
TagsNo tags attached.
Relationships
blocks defect 0052448 closed jayala Open ticket with correct schema 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2023-05-15 14:42jayalaTypedefect => backport
2023-05-15 14:42jayalaTarget Version => 23Q2.1
2023-05-16 14:57hgbotNote Added: 0149834
2023-05-16 14:58hgbotNote Added: 0149835
2023-05-16 15:03hgbotNote Added: 0149836
2023-05-17 10:18hgbotMerge Request Statusopen => approved
2023-05-17 10:18hgbotResolutionopen => fixed
2023-05-17 10:18hgbotStatusscheduled => closed
2023-05-17 10:18hgbotFixed in Version => 23Q2.1
2023-05-17 10:18hgbotNote Added: 0149864
2023-05-17 10:18hgbotNote Added: 0149865

Notes
(0149834)
hgbot   
2023-05-16 14:57   
Merge Request created: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/merge_requests/1803 [^]
(0149835)
hgbot   
2023-05-16 14:58   
Merge request closed: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/merge_requests/1803 [^]
(0149836)
hgbot   
2023-05-16 15:03   
Merge Request created: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/merge_requests/1804 [^]
(0149864)
hgbot   
2023-05-17 10:18   
Directly closing issue as related merge request is already approved.

Repository: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2 [^]
Changeset: 71a11dda4883d3c8d344d74f9fdb32b97cad1722
Author: Javier Ayala <javier.ayala@openbravo.com>
Date: 16-05-2023 16:21:37
URL: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/commit/71a11dda4883d3c8d344d74f9fdb32b97cad1722 [^]

Fixed ISSUE-52449: Open ticket with correct schema

---
M web-jspack/org.openbravo.pos2/src/model/ticket/__test__/SetCurrentSchema.test.js
M web-jspack/org.openbravo.pos2/src/model/ticket/actions/SetCurrentSchema.js
M web-jspack/org.openbravo.pos2/src/model/user-interface/__test__/SelectCurrentSchema.test.js
M web-jspack/org.openbravo.pos2/src/model/user-interface/user-actions/SelectCurrentSchema.js
---
(0149865)
hgbot   
2023-05-17 10:18   
Merge request merged: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/merge_requests/1804 [^]