Openbravo Issue Tracking System - POS2
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0052448POS2POSpublic2023-05-15 14:382023-05-17 10:17
Reporterjayala 
Assigned Tojayala 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version23Q3 
Merge Request Statusmerged
Review Assigned To
OBNetwork customerNo
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0052448: 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
depends on backport 005244923Q2.1 closed jayala Open ticket with correct schema 
depends on backport 005245023Q1.3 closed jayala Open ticket with correct schema 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2023-05-15 14:38jayalaNew Issue
2023-05-15 14:38jayalaAssigned To => jayala
2023-05-15 14:38jayalaOBNetwork customer => No
2023-05-15 14:38jayalaTriggers an Emergency Pack => No
2023-05-15 14:41hgbotMerge Request Status => open
2023-05-15 14:41hgbotNote Added: 0149703
2023-05-15 14:42jayalaStatusnew => scheduled
2023-05-17 10:16hgbotResolutionopen => fixed
2023-05-17 10:16hgbotStatusscheduled => resolved
2023-05-17 10:16hgbotFixed in Version => 23Q3
2023-05-17 10:16hgbotNote Added: 0149862
2023-05-17 10:16hgbotMerge Request Statusopen => merged
2023-05-17 10:16hgbotNote Added: 0149863
2023-05-17 10:17javierRodriguezStatusresolved => closed

Notes
(0149703)
hgbot   
2023-05-15 14:41   
Merge Request created: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/merge_requests/1792 [^]
(0149862)
hgbot   
2023-05-17 10:16   
Repository: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2 [^]
Changeset: 939fd9f16643a0271b51ac15853e94b7b1bed6cc
Author: Javier Ayala <javier.ayala@openbravo.com>
Date: 17-05-2023 08:15:35
URL: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/commit/939fd9f16643a0271b51ac15853e94b7b1bed6cc [^]

Fixed ISSUE-52448: 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
---
(0149863)
hgbot   
2023-05-17 10:16   
Merge request merged: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/merge_requests/1792 [^]