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

View Issue Details[ Jump to Notes ] [ Issue History ] [ Print ]
ID
0052734
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[POS2] POSminorhave not tried2023-06-13 16:472023-06-15 08:40
ReporterguilleaerView Statuspublic 
Assigned Toguilleaer 
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 customerGold
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0052734: CurrentSchemaId property of UI model is not correct in some cases

DescriptionCurrentSchemaId property of UI model is not correct when cashup is done and the list of orders is cleared.

I have an order is schema A and I execute cashup
UI.CurrentSchemaId is A
When cashup is done all orders are removed and new one created using the default schema B

In that situation the schema of the new order is B but the info iin the UI model is A

When POS starts after cashup the schema A is shown in the screen but the ticket which is being used has the schema B

Both ticket and UI models should has the same value in this case
Steps To ReproduceHaving a store with 2 schemas
Schema A
Schema B

Being Schema B the default one (This is configured in touchpoint window)

Login in POS
Do a sale in schema B
move to schema A
execute cashup and finish
Login in POS
Schema A is shown in the screen (wrong)
Add a product to the ticket -> Shows that it was added from schema B (Wrong)
Proposed SolutionWhen cashup is done and a new order is created for the defaukt schema, this schema should be set also at the UI model
TagsNo tags attached.
Attached Files

- Relationships [ Relation Graph ] [ Dependency Graph ]
depends on backport 005273523Q2.2 closedguilleaer CurrentSchemaId property of UI model is not correct in some cases 
depends on backport 005273623Q1.4 closedguilleaer CurrentSchemaId property of UI model is not correct in some cases 

-  Notes
(0151121)
hgbot (developer)
2023-06-13 16:56

 Merge Request created: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/merge_requests/1893 [^]
(0151179)
hgbot (developer)
2023-06-15 08:40

 Merge request merged: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/merge_requests/1893 [^]
(0151180)
hgbot (developer)
2023-06-15 08:40

 Directly closing issue as related merge request is already approved.

Repository: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2 [^]
Changeset: af233b1516363af135dab7966a2d22ffc45d60f0
Author: Guillermo Alvarez de Eulate <guillermo.alvarez@openbravo.com>
Date: 15-06-2023 06:40:14
URL: https://gitlab.com/openbravo/product/pmods/org.openbravo.pos2/-/commit/af233b1516363af135dab7966a2d22ffc45d60f0 [^]

fixed ISSUE-52734: currentSchemaId of UI model is set when new order is created by cashup

---
M web-jspack/org.openbravo.pos2/src/model/user-interface/__test__/FinishCashupUserAction.test.js
M web-jspack/org.openbravo.pos2/src/model/user-interface/user-actions/cashup/FinishCashup.js
---

- Issue History
Date Modified Username Field Change
2023-06-13 16:47 guilleaer New Issue
2023-06-13 16:47 guilleaer Assigned To => guilleaer
2023-06-13 16:47 guilleaer OBNetwork customer => Gold
2023-06-13 16:47 guilleaer Triggers an Emergency Pack => No
2023-06-13 16:47 guilleaer Status new => scheduled
2023-06-13 16:56 hgbot Merge Request Status => open
2023-06-13 16:56 hgbot Note Added: 0151121
2023-06-14 16:05 hgbot Merge Request Status open => approved
2023-06-15 08:40 hgbot Resolution open => fixed
2023-06-15 08:40 hgbot Status scheduled => closed
2023-06-15 08:40 hgbot Note Added: 0151179
2023-06-15 08:40 hgbot Fixed in Version => 23Q3
2023-06-15 08:40 hgbot Note Added: 0151180

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker