Anonymous | Login
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
TypeCategorySeverityReproducibilityDate SubmittedLast Update
backport[Retail Modules] Web POSmajoralways2020-02-10 16:532020-02-18 07:32
Reportergorka_gilView Statuspublic 
Assigned Tomarkmm82 
PriorityurgentResolutionfixedFixed in VersionRR19Q3.3
StatusclosedFix in branchFixed in SCM revision5b052b8960c0
ProjectionnoneETAnoneTarget VersionRR19Q3.3
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned Toguilleaer
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo

0043166: Before update sources the messages should be synchronized

DescriptionIf exist messages without synchronize, it is needed to send them to the backend before update the webpos sources.
Steps To ReproduceThis issues is especially relevant when message table is moved from websql to indexedDB.

- Having an instance of message table in websql (20q1 or less).
- Go offline and create a ticket.
- Switch the an instance with message table in indexedDB (20q2 or more)
- Go back online.
- Problem: it is updating the sources before synchronize the messages, to these messages will be never synchronize.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
blocks defect 0043163 closedgorka_gil Before update sources the messages should be synchronized 

-  Notes
hgbot (developer)
2020-02-13 17:33

Repository: retail/backports/3.0RR19Q3.3/
Changeset: 5b052b8960c0f3a1bd42d47acbd7f27707200483
Author: Mark Molina <mark.molina <at>>
Date: Thu Feb 13 13:26:17 2020 -0300
URL: [^]

Fixes BUG-43166: Synchronize messages before update sources
- In login, don't update sources if still messages in message table
- Requests of import entry: added call to checkSourceVersion
- Normal requests: it have the sourceVersion, save it in RAM
  for use on import entry request that don't have it:
- When detected the change of source version, force the
  synchronization of messages
   - If fail, show popup and do logout
- Stop logClient synchronization to avoid errors when updating
  because logClient servlet was removed as part of indexedDB change

Also removed error popup on update to allow login offline
If we do login with messages pending to synchronize, in the login process
is forced a syncrhonize of all the messages, but if fails
we don't want to show a popup and do logout, because on innestable
networks will make very dificult the login offline.

M web/
M web/
M web/
M web/

- Issue History
Date Modified Username Field Change
2020-02-10 16:59 gorka_gil Type defect => backport
2020-02-10 16:59 gorka_gil Target Version => RR19Q3.3
2020-02-13 17:33 hgbot Checkin
2020-02-13 17:33 hgbot Note Added: 0117751
2020-02-13 17:33 hgbot Status scheduled => resolved
2020-02-13 17:33 hgbot Resolution open => fixed
2020-02-13 17:33 hgbot Fixed in SCM revision => [^]
2020-02-13 17:43 markmm82 Assigned To gorka_gil => markmm82
2020-02-18 07:32 guilleaer Review Assigned To => guilleaer
2020-02-18 07:32 guilleaer Status resolved => closed
2020-02-18 07:32 guilleaer Fixed in Version => RR19Q3.3

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker