Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue Details[ Jump to Notes ] [ Issue History ] [ Print ]
ID
0050053
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[POS2] POSmajoralways2022-08-24 17:002023-08-23 08:46
Reportercharlotte_vasseurView Statuspublic 
Assigned ToRetail 
PriorityhighResolutionduplicateFixed in Version
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0050053: [Price List] Cache problems in POS after stopping a commercial operation

DescriptionWe have to clean cache/history or open POS in private mode of the browser to see changes after stopping a commercial operation
Refreshing masterdata in POS should be enough
Steps To ReproduceIn Backoffice, window ‘Commercial Operation’
Create a commercial operation for few products (with starting date in the past) and validate it (see OPCOM 1.png)
Go to ‘Price List’ window and select the price list that is used by the store of the terminal wanted (for Vall Blanca Store : The White Valley Group Sale Price List)
In ‘Price List Version’ subtab, select the last active price list version (for Vall Blanca Store : The White Valley Group Saale Price List Version)
In ‘Product Price’ subtab, select the product wanted (targeted by the commercial operation)
In ‘Product Price with Exceptions’ : the price exception is created (see OPCOM 1 Price List Exception.png)

Refresh master data in POS, the prices of the commercial operation applies for the products (see OPCOM 1 POS.png)

In backoffice, select the previous commercial operation and click on ‘Stop’ button and choose today

The end date is set as today in the header of the commercial operation and in the included stores (see OPCOM 1 STOP.png)
The end date is set as today for the product price exception and ‘active’ is no longer checked (see OPCOM 1 STOP Price List Exception.png)

In POS, refresh master data
Search for the product => The price exception from the commercial operation is still applied (KO)

=> If we clean the cache and history of the browser, close and reopen POS (or open POS in a private mode window of the browser), then the price exception from the commercial operation no longer applies
TagsFASH
Attached Filespng file icon OPCOM 1.png [^] (183,835 bytes) 2022-08-24 17:00


png file icon OPCOM 1 Price List Exception.png [^] (158,827 bytes) 2022-08-24 17:00


png file icon OPCOM 1 POS.png [^] (139,224 bytes) 2022-08-24 17:00


png file icon OPCOM 1 STOP.png [^] (156,800 bytes) 2022-08-24 17:00


png file icon OPCOM 1 STOP Price List Exception.png [^] (158,505 bytes) 2022-08-24 17:00

- Relationships [ Relation Graph ] [ Dependency Graph ]
duplicate of defect 0049975 closedradhakrishnan Retail Modules Stop Button doesn't stop the commercial operation right away 

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2022-08-24 17:00 charlotte_vasseur New Issue
2022-08-24 17:00 charlotte_vasseur Assigned To => Retail
2022-08-24 17:00 charlotte_vasseur File Added: OPCOM 1.png
2022-08-24 17:00 charlotte_vasseur Triggers an Emergency Pack => No
2022-08-24 17:00 charlotte_vasseur File Added: OPCOM 1 Price List Exception.png
2022-08-24 17:00 charlotte_vasseur File Added: OPCOM 1 POS.png
2022-08-24 17:00 charlotte_vasseur File Added: OPCOM 1 STOP.png
2022-08-24 17:00 charlotte_vasseur File Added: OPCOM 1 STOP Price List Exception.png
2022-08-24 17:45 rafaroda Tag Attached: FASH
2022-10-10 15:28 ranjith_qualiantech_com Relationship added duplicate of 0049975
2023-08-23 08:46 ranjith_qualiantech_com Status new => closed
2023-08-23 08:46 ranjith_qualiantech_com Resolution open => duplicate

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker