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

View Issue Details[ Jump to Notes ] [ Issue History ] [ Print ]
ID
0052448
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[POS2] POSminorhave not tried2023-05-15 14:382023-05-17 10:17
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 Statusmerged
Review Assigned To
OBNetwork customerNo
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

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

- Relationships [ Relation Graph ] [ Dependency Graph ]
depends on backport 005244923Q2.1 closedjayala Open ticket with correct schema 
depends on backport 005245023Q1.3 closedjayala Open ticket with correct schema 

-  Notes
(0149703)
hgbot (developer)
2023-05-15 14:41

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

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

- Issue History
Date Modified Username Field Change
2023-05-15 14:38 jayala New Issue
2023-05-15 14:38 jayala Assigned To => jayala
2023-05-15 14:38 jayala OBNetwork customer => No
2023-05-15 14:38 jayala Triggers an Emergency Pack => No
2023-05-15 14:41 hgbot Merge Request Status => open
2023-05-15 14:41 hgbot Note Added: 0149703
2023-05-15 14:42 jayala Status new => scheduled
2023-05-17 10:16 hgbot Resolution open => fixed
2023-05-17 10:16 hgbot Status scheduled => resolved
2023-05-17 10:16 hgbot Fixed in Version => 23Q3
2023-05-17 10:16 hgbot Note Added: 0149862
2023-05-17 10:16 hgbot Merge Request Status open => merged
2023-05-17 10:16 hgbot Note Added: 0149863
2023-05-17 10:17 javierRodriguez Status resolved => closed

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker