Openbravo Issue Tracking System - Retail Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0051799Retail ModulesWeb POSpublic2023-03-08 08:082023-03-08 08:11
ReporterAugustoMauch 
Assigned ToAugustoMauch 
PriorityurgentSeveritymajorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Version 
Target VersionRR22Q4Fixed in VersionRR22Q4.3 
Merge Request Status
Review Assigned To
OBNetwork customer
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0051799: ERROR WHILE IMPORTING: org.openbravo.mobile.core.process.OutDatedDataChangeException
DescriptionWhen I make a sale in webPOS and pay for it, when I put a debug in preprint, I update and then continue. The following error is generated while importing:
org.openbravo.mobile.core.process.OutDatedDataChangeException: The data of this order has been changed on the server. Please reload the ticket through the menu and apply your changes again.
Steps To Reproduce1 - Open WEBPOS
2 - Put a debug in preprint
3 - Do a sales.
4 - When stop the debugging, click in F5
5 - Continue the sales.
7 - Check the errors while importing
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2023-03-08 08:08AugustoMauchNew Issue
2023-03-08 08:08AugustoMauchAssigned To => AugustoMauch
2023-03-08 08:08AugustoMauchTriggers an Emergency Pack => No
2023-03-08 08:08AugustoMauchIssue generated from0050925
2023-03-08 08:09AugustoMauchversionRR22Q4 =>
2023-03-08 08:09AugustoMauchTarget Version => RR22Q4
2023-03-08 08:10hgbotNote Added: 0147352
2023-03-08 08:11hgbotNote Added: 0147353
2023-03-08 08:11hgbotResolutionopen => fixed
2023-03-08 08:11hgbotStatusnew => closed
2023-03-08 08:11hgbotFixed in Version => RR22Q4.3
2023-03-08 08:11hgbotNote Added: 0147354
2023-03-08 08:11hgbotNote Added: 0147355

Notes
(0147352)
hgbot   
2023-03-08 08:10   
Merge Request created: https://gitlab.com/openbravo/product/pmods/org.openbravo.mobile.core/-/merge_requests/483 [^]
(0147353)
hgbot   
2023-03-08 08:11   
Merge request merged: https://gitlab.com/openbravo/product/pmods/org.openbravo.mobile.core/-/merge_requests/483 [^]
(0147354)
hgbot   
2023-03-08 08:11   
Directly closing issue as related merge request is already approved.

Repository: https://gitlab.com/openbravo/product/pmods/org.openbravo.mobile.core [^]
Changeset: 5ba07e77e818f143e3d63693607e67ac490d9b08
Author: Augusto Mauch <augusto.mauch@openbravo.com>
Date: 08-03-2023 08:10:08
URL: https://gitlab.com/openbravo/product/pmods/org.openbravo.mobile.core/-/commit/5ba07e77e818f143e3d63693607e67ac490d9b08 [^]

Fixes ISSUE-51799: State is persistate immediately if state model is persisted

There is a problem when a state action generates a message if the user refreshes the tab before the state
was persisted. In that situation the message will be sent to the backend but the rest of the state will
remain as it was before the action was completed when recovered from the persisted state.

To prevent this problem, we are now forcing the immediate persistence of the updated state if a new backend message
has been created as a consequence of the action execution. The only exception are OBMOBC_TerminalLog messages, those
do not force immediate persistence to prevent a performance impact on messages that do not generate relevant problems
if sent to the backend twice.

---
M web/org.openbravo.mobile.core/app/model/application-state/State.js
---
(0147355)
hgbot   
2023-03-08 08:11   
Repository: https://gitlab.com/openbravo/product/pmods/org.openbravo.mobile.core [^]
Changeset: 1b82f93d89c831d003f65311551e6025c9c08256
Author: Augusto Mauch <augusto.mauch@openbravo.com>
Date: 08-03-2023 08:10:14
URL: https://gitlab.com/openbravo/product/pmods/org.openbravo.mobile.core/-/commit/1b82f93d89c831d003f65311551e6025c9c08256 [^]

Related to ISSUE-51799: checkContextChange is more robust

As part of the fix of this issue we noticed that checkContextChange is not robust enough. There is a race condition and
potentially checkContextChange could be invoked passing the context as parameter in a non supported format. Instead of
an object that contains four string properties (IDs), it receives an object that contains four objects (user, role, org,
client).

Now checkContextChange supports both formats, in case it ever receives the objects-within-object format

---
M web/org.openbravo.mobile.core/app/integration/remote-server/BackendServer.js
---