Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
| ID | ||||||||
| 0050258 | ||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
| defect | [Retail Modules] Selfcheckout | major | always | 2022-09-15 14:15 | 2022-10-03 08:05 | |||
| Reporter | malsasua | View Status | public | |||||
| Assigned To | ranjith_qualiantech_com | |||||||
| Priority | high | Resolution | no change required | Fixed in Version | ||||
| Status | closed | Fix in branch | Fixed in SCM revision | |||||
| Projection | none | ETA | none | Target Version | ||||
| OS | Any | Database | Any | Java version | ||||
| OS Version | Database version | Ant version | ||||||
| Product Version | SCM revision | |||||||
| Review Assigned To | marvintm | |||||||
| Regression level | ||||||||
| Regression date | ||||||||
| Regression introduced in release | ||||||||
| Regression introduced by commit | ||||||||
| Triggers an Emergency Pack | No | |||||||
| Summary | 0050258: 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 Reproduce | BO: 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 | |||||||
| Tags | No tags attached. | |||||||
| Attached Files | ||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
||||||||
|
||||||||
 Relationships |
|
Notes |
|
|
(0141545) marvintm (manager) 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. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2022-09-15 14:15 | malsasua | New Issue | |
| 2022-09-15 14:15 | malsasua | Assigned To | => Retail |
| 2022-09-15 14:15 | malsasua | Triggers an Emergency Pack | => No |
| 2022-09-15 15:22 | malsasua | Description Updated | View Revisions |
| 2022-09-15 15:25 | malsasua | Steps to Reproduce Updated | View Revisions |
| 2022-09-16 12:01 | hector_hernaez | Issue Monitored: hector_hernaez | |
| 2022-09-22 10:55 | ranjith_qualiantech_com | Assigned To | Retail => ranjith_qualiantech_com |
| 2022-09-22 10:55 | ranjith_qualiantech_com | Status | new => scheduled |
| 2022-09-26 10:06 | maite | Issue Monitored: maite | |
| 2022-10-03 08:05 | marvintm | Review Assigned To | => marvintm |
| 2022-10-03 08:05 | marvintm | Note Added: 0141545 | |
| 2022-10-03 08:05 | marvintm | Status | scheduled => closed |
| 2022-10-03 08:05 | marvintm | Resolution | open => no change required |
| 2022-12-02 06:56 | ranjith_qualiantech_com | Relationship added | related to 0051049 |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |