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

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0052243
TypeCategorySeverityReproducibilityDate SubmittedLast Update
backport[POS2] POStrivialhave not tried2023-04-25 16:232023-05-11 11:10
ReporterjayalaView Statuspublic 
Assigned Tojayala 
PrioritynormalResolutionfixedFixed in Version23Q1.3
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version23Q1.3
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
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
Summary

0052243: 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.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
blocks feature request 0052231 closedjayala Open order in the most adecuated schema 

-  Notes
(0149482)
hgbot (developer)
2023-05-09 11:00

Merge Request created: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/merge_requests/1771 [^]
(0149539)
hgbot (developer)
2023-05-10 09:32

Merge request closed: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/merge_requests/1771 [^]
(0149605)
hgbot (developer)
2023-05-11 10:51

Merge Request created: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/merge_requests/1781 [^]
(0149608)
hgbot (developer)
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 (developer)
2023-05-11 11:10

Merge request merged: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/merge_requests/1781 [^]

- Issue History
Date Modified Username Field Change
2023-04-26 10:55 jayala Type feature request => backport
2023-04-26 10:55 jayala Target Version => 23Q1.3
2023-04-26 10:55 jayala Assigned To Retail => jayala
2023-05-09 11:00 hgbot Merge Request Status => open
2023-05-09 11:00 hgbot Note Added: 0149482
2023-05-10 09:32 hgbot Note Added: 0149539
2023-05-11 10:51 hgbot Note Added: 0149605
2023-05-11 11:10 hgbot Merge Request Status open => approved
2023-05-11 11:10 hgbot Resolution open => fixed
2023-05-11 11:10 hgbot Status scheduled => closed
2023-05-11 11:10 hgbot Fixed in Version => 23Q1.3
2023-05-11 11:10 hgbot Note Added: 0149608
2023-05-11 11:10 hgbot Note Added: 0149609


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker