Openbravo Issue Tracking System - POS2
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0052243POS2POSpublic2023-04-25 16:232023-05-11 11:10
Reporterjayala 
Assigned Tojayala 
PrioritynormalSeveritytrivialReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Version 
Target Version23Q1.3Fixed in Version23Q1.3 
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
Summary0052243: Open order in the most adecuated schema
DescriptionWhen an order which has a schemaId information is loaded, POS should be able to load it automatically opening the linked schema.
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 SolutionWe will decide which schema will be selected in the POS based on the following conditions:
 1. Use the schema provided by the order in case it's available in the POS and compatible with the loaded order.
 2. Use the schema which currently is being used in POS in case it's available in the POS and compatible with the loaded order.
 3. Use the default schema defined for the POS in case it's available in the POS and compatible with the loaded order.
 *. If none of the schemas installed on the POS are compatible with the current order then a warning will be shown and the order will be opened using the default schema.
Additional Information
TagsNo tags attached.
Relationships
blocks feature request 0052231 closed jayala Open order in the most adecuated schema 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2023-04-26 10:55jayalaTypefeature request => backport
2023-04-26 10:55jayalaTarget Version => 23Q1.3
2023-04-26 10:55jayalaAssigned ToRetail => jayala
2023-05-09 11:00hgbotMerge Request Status => open
2023-05-09 11:00hgbotNote Added: 0149482
2023-05-10 09:32hgbotNote Added: 0149539
2023-05-11 10:51hgbotNote Added: 0149605
2023-05-11 11:10hgbotMerge Request Statusopen => approved
2023-05-11 11:10hgbotResolutionopen => fixed
2023-05-11 11:10hgbotStatusscheduled => closed
2023-05-11 11:10hgbotFixed in Version => 23Q1.3
2023-05-11 11:10hgbotNote Added: 0149608
2023-05-11 11:10hgbotNote Added: 0149609

Notes
(0149482)
hgbot   
2023-05-09 11:00   
Merge Request created: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/merge_requests/1771 [^]
(0149539)
hgbot   
2023-05-10 09:32   
Merge request closed: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/merge_requests/1771 [^]
(0149605)
hgbot   
2023-05-11 10:51   
Merge Request created: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/merge_requests/1781 [^]
(0149608)
hgbot   
2023-05-11 11:10   
Directly closing issue as related merge request is already approved.

Repository: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2 [^]
Changeset: ec7aa039c0eeba5dbb858eca6e8fac85c5ada378
Author: Javier Ayala <javier.ayala@openbravo.com>
Date: 11-05-2023 10:51:47
URL: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/commit/ec7aa039c0eeba5dbb858eca6e8fac85c5ada378 [^]

Fixed ISSUE-52243: Open order in the most adecuated schema

---
M src-db/database/sourcedata/AD_MESSAGE.xml
M web-jspack/org.openbravo.pos2/src/model/ticket/TicketExtension.js
M web-jspack/org.openbravo.pos2/src/model/ticket/actions/SetCurrentSchema.js
M web-jspack/org.openbravo.pos2/src/model/ticket/user-actions/LoadRemoteTicket.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
---
(0149609)
hgbot   
2023-05-11 11:10   
Merge request merged: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/merge_requests/1781 [^]