Openbravo Issue Tracking System - Retail Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0050258Retail ModulesSelfcheckoutpublic2022-09-15 14:152022-10-03 08:05
Reportermalsasua 
Assigned Toranjith_qualiantech_com 
PriorityhighSeveritymajorReproducibilityalways
StatusclosedResolutionno change required 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned Tomarvintm
OBNetwork customer
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0050258: In SCO, the incremental refresh process is executed during the purchase
Description. it is possible to buy the same item with different price if the incremental refresh process is executed during the purchase process

Video explaining the problem:
https://watch.screencastify.com/v/oQSHjb66DwXOmMQVfFz4 [^]

min: 0:05-> product Avalanche is added with price 150 -> OK
min: 0:15-> price is modified to 120 in BO
min: 1:15-> incremental refresh process is executed in Backgroud
min: 1:20-> product Avalanche is added with price 150 -> OK
min: 2:45-> product Avalanche is added with price 120 -> KO
Steps To ReproduceBO:
1. configure the incremental refresh process to execute for each 2 min

SCO:
2. add the product1: price 10

BO:
3. change the price of product1 from 10 to 20

SCO:
4. wait until the inc refresh process is executed
5. add the product1: price 20
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
related to defect 0051049 closed ranjith_qualiantech_com In SCO, the Incremental Refresh process is executed during the purchase in DKT APAC 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2022-09-15 14:15malsasuaNew Issue
2022-09-15 14:15malsasuaAssigned To => Retail
2022-09-15 14:15malsasuaTriggers an Emergency Pack => No
2022-09-15 15:22malsasuaDescription Updatedbug_revision_view_page.php?rev_id=24768#r24768
2022-09-15 15:25malsasuaSteps to Reproduce Updatedbug_revision_view_page.php?rev_id=24770#r24770
2022-09-16 12:01hector_hernaezIssue Monitored: hector_hernaez
2022-09-22 10:55ranjith_qualiantech_comAssigned ToRetail => ranjith_qualiantech_com
2022-09-22 10:55ranjith_qualiantech_comStatusnew => scheduled
2022-09-26 10:06maiteIssue Monitored: maite
2022-10-03 08:05marvintmReview Assigned To => marvintm
2022-10-03 08:05marvintmNote Added: 0141545
2022-10-03 08:05marvintmStatusscheduled => closed
2022-10-03 08:05marvintmResolutionopen => no change required
2022-12-02 06:56ranjith_qualiantech_comRelationship addedrelated to 0051049

Notes
(0141545)
marvintm   
2022-10-03 08:05   
This is actually the expected behavior.

There are two settings relevant for this:
- "Time to Incrementally Refresh Masterdata (in minutes)"
- "Time to force masterdata refresh on inactivity (in minutes)"

When the first is reached, an incremental refresh will be triggered. This will load the missing data in the background, but will not apply it yet, until the current sale is finished.

However, if the timeout after the current sale is reached, then we will force the change in the data, even if the current sale is not finished.

If customers don't want this second thing to happen, then they need to increase this timeout to some time they feel comfortable with.