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

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0057135
TypeCategorySeverityReproducibilityDate SubmittedLast Update
backport[Retail Modules] Web POSmajoralways2024-11-05 11:372024-11-18 09:03
ReportermalsasuaView Statuspublic 
Assigned ToTriage Platform Base 
PrioritynormalResolutionopenFixed in Version
StatusscheduledFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget VersionRR24Q2.5
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

0057135: Full refresh is not executed when one masterdata model changed

DescriptionAfter one deploy that modifying one masterdata model, if the login page is not refreshed, the first login is not triggering a full refresh

The problem is reproducible in react and enyo.
Steps To Reproduce. do login in POS
. do cashup
. do logout (no close Chrome tab)
. compile adding one property in one masterdata model (for react, you can apply the patch attached in the posterminal module)
. do login in POS -> full refresh is not executed
. do logout
. refresh brower
. do login -> full refresh is executed
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
blocks defect 0056978 scheduledTriage Platform Base Full refresh is not executed when one masterdata model changed 

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2024-11-18 09:03 AugustoMauch Type defect => backport
2024-11-18 09:03 AugustoMauch Target Version => RR24Q2.5


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker