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

View Issue DetailsJump to Notes ] Issue History ] Print ]
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[POS2] POSminorhave not tried2023-03-09 10:262023-03-09 12:33
ReportercaristuView Statuspublic 
Assigned ToTriage Platform Base 
PriorityhighResolutionopenFixed in Version
StatusnewFix 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

0051820: Refresh masterdata forces to reload the app although terminal properties have not changed

DescriptionAfter refreshing the application, the refresh masterdata process always forces to refresh the application although there have not been real changes in the terminal properties.

Note that in this case the hooks in TerminalDataMasterHooks are always detecting the same change in the terminal properties. See attached.
Steps To Reproduce1) Login in ReactPOS
2) Press F5 to refresh the application: this step seems to be needed to reproduce the bug
3) Click on the "Refresh Masterdata" button
4) When the refresh finishes, a popup with the following message appears: "Configuration of the terminal has changed, a refresh is required."
5) Once the application is reloaded, click on the "Refresh Masterdata" button again
6) When the refresh finishes, the popup to refresh appears again although we have not done any change in the terminal properties
TagsNo tags attached.
Attached Filespng file icon changes.png [^] (87,476 bytes) 2023-03-09 10:28

- Relationships Relation Graph ] Dependency Graph ]
related to design defect 0047591 closedcberner POS2 Terminal model not updated in incremental refresh 
related to feature request 0051631 closedcaristu Retail Modules Masterdata Remote Mode - Phase 1 
caused by feature request 0051052 closedjavierRodriguez POS2 Use the inactivity infrastructure to automatically close a ticket if the user did not interact with the POS for some time 

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2023-03-09 10:26 caristu New Issue
2023-03-09 10:26 caristu Assigned To => Retail
2023-03-09 10:26 caristu Triggers an Emergency Pack => No
2023-03-09 10:27 caristu Relationship added related to 0047591
2023-03-09 10:28 caristu File Added: changes.png
2023-03-09 10:28 caristu Relationship added caused by 0051052
2023-03-09 10:53 caristu Assigned To Retail => Triage Platform Base
2023-03-09 12:33 caristu Relationship added related to 0051631

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker