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

View Issue DetailsJump to Notes ] Issue History ] Print ]
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Retail Modules] Web POSmajorhave not tried2021-05-04 08:292021-06-07 17:24
ReporteralostaleView Statuspublic 
Assigned Togorka_gil 
PriorityimmediateResolutionno change requiredFixed in Version
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Regression levelProduction - Confirmed Stable
Regression date2020-04-06
Regression introduced in releaseRR20Q3
Regression introduced by commit [^]
Triggers an Emergency PackNo

0046474: duplicated data fetched by incremental refreshes during the same session

DescriptionAll the incremental refreshes triggered for the same session check the same updated timestamp. This causes the same data to be sent repeatedly while the session is alive.
Steps To Reproduce1. Configure incremental refresh to be triggered every 1 minute
2. Log in Web POS
3. In backoffice update a product that will be fetched as part of the store's assortment
4. Wait till next refresh occurs
   -> OK: that refresh fetches the updated product. Check also the request lastUpdated param value
5. Wait till next refresh occurs
   -> FAIL: the refresh includes the previous product again. The request has lastUpdated param with the same value than in previous refresh
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
caused by feature request 0043657 closedSandrahuguet Masterdata IndexedDB - Phase 1 

-  Notes
gorka_gil (administrator)
2021-06-07 17:24

Tested now and is working correctly.

The confusion was probably because the way of work of the background refresh.

There is 3 refresh timers:
- full
- incremental
- force

If you configure the incremental each minute and the force each 5 mins,
then will execute the requests of changes each min, with the same data,
if there is a new product will retrieve the same product in each request.

Till the force timer that introduces really the data in the db, from that moment will not retrieve that product. Alternatively making a new order will also save the data in the db.

This is the designed way to work. The first timer gets the data from the backend and saves into ram, and the second timer saves into db. And for do the request to the backend is used the last updated time of the db, since the variable to store in ram is the same, so if a second request happens before save into db, we will lost the data of the previous request.

- Issue History
Date Modified Username Field Change
2021-05-04 08:29 alostale New Issue
2021-05-04 08:29 alostale Assigned To => Retail
2021-05-04 08:29 alostale Triggers an Emergency Pack => No
2021-05-04 08:30 alostale Relationship added caused by 0043657
2021-05-04 08:32 alostale Regression level => Production - Confirmed Stable
2021-05-04 08:32 alostale Regression date => 2020-04-06
2021-05-04 08:32 alostale Regression introduced in release => RR20Q3
2021-05-04 08:32 alostale Regression introduced by commit => [^]
2021-06-07 12:55 gorka_gil Assigned To Retail => gorka_gil
2021-06-07 17:24 gorka_gil Note Added: 0129154
2021-06-07 17:24 gorka_gil Status new => closed
2021-06-07 17:24 gorka_gil Resolution open => no change required

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker