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

View Issue Details[ Jump to Notes ] [ Issue History ] [ Print ]
ID
0052231
TypeCategorySeverityReproducibilityDate SubmittedLast Update
feature request[POS2] POStrivialhave not tried2023-04-25 16:232023-05-11 10:26
ReporterjayalaView Statuspublic 
Assigned Tojayala 
PrioritynormalResolutionfixedFixed in Version23Q3
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
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

0052231: 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 ]
depends on backport 005224223Q2.1 closedjayala Open order in the most adecuated schema 
depends on backport 005224323Q1.3 closedjayala Open order in the most adecuated schema 

-  Notes
(0148944)
hgbot (developer)
2023-04-26 16:26

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

 Merge request merged: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/merge_requests/1730 [^]
(0149480)
hgbot (developer)
2023-05-09 10:30

 Directly closing issue as related merge request is already approved.

Repository: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2 [^]
Changeset: fa0239203f9207155957c63dd51653112355ea23
Author: Javier Ayala <javier.ayala@openbravo.com>
Date: 09-05-2023 08:30:05
URL: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/commit/fa0239203f9207155957c63dd51653112355ea23 [^]

Fixed ISSUE-52231: 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
---
(0149492)
hgbot (developer)
2023-05-09 13:29

 Directly closing issue as related merge request is already approved.

Repository: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2 [^]
Changeset: 130e9dfbe7f9d37e8345620f22e64dccf8e309cc
Author: Javier Rodriguez Regueiro <javier.rodriguez@openbravo.com>
Date: 09-05-2023 13:27:52
URL: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/commit/130e9dfbe7f9d37e8345620f22e64dccf8e309cc [^]

Revert "Fixed ISSUE-52231: Open order in the most adecuated schema"

This reverts commit fa0239203f9207155957c63dd51653112355ea23.

---
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
---
(0149506)
hgbot (developer)
2023-05-09 16:54

 Merge Request created: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/merge_requests/1773 [^]
(0149598)
hgbot (developer)
2023-05-11 10:26

 Directly closing issue as related merge request is already approved.

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

Fixed ISSUE-52231: 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
---
(0149599)
hgbot (developer)
2023-05-11 10:26

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

- Issue History
Date Modified Username Field Change
2023-04-25 16:23 jayala New Issue
2023-04-25 16:23 jayala Assigned To => Retail
2023-04-25 16:23 jayala OBNetwork customer => No
2023-04-25 16:23 jayala Triggers an Emergency Pack => No
2023-04-26 10:54 jayala Summary Prevent load an order when schema isn't compatible => Open order in the most adecuated schema
2023-04-26 10:54 jayala Description Updated View Revisions
2023-04-26 10:54 jayala Steps to Reproduce Updated View Revisions
2023-04-26 10:54 jayala Proposed Solution updated
2023-04-26 10:54 jayala Type defect => feature request
2023-04-26 10:55 jayala Status new => scheduled
2023-04-26 10:56 jayala Assigned To Retail => jayala
2023-04-26 16:26 hgbot Merge Request Status => open
2023-04-26 16:26 hgbot Note Added: 0148944
2023-05-09 10:29 hgbot Merge Request Status open => approved
2023-05-09 10:30 hgbot Resolution open => fixed
2023-05-09 10:30 hgbot Status scheduled => closed
2023-05-09 10:30 hgbot Note Added: 0149479
2023-05-09 10:30 hgbot Fixed in Version => 23Q3
2023-05-09 10:30 hgbot Note Added: 0149480
2023-05-09 13:29 hgbot Note Added: 0149492
2023-05-09 16:54 hgbot Note Added: 0149506
2023-05-11 10:26 hgbot Note Added: 0149598
2023-05-11 10:26 hgbot Note Added: 0149599

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker