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

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0056978
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[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 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

0056978: 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 Filesdiff file icon posterminal_test.diff [^] (1,482 bytes) 2024-11-05 11:37 [Show Content]

- Relationships Relation Graph ] Dependency Graph ]
depends on backport 0057133RR24Q4 scheduledTriage Platform Base Retail Modules Full refresh is not executed when one masterdata model changed 
depends on backport 0057134RR24Q3.3 scheduledTriage Platform Base Retail Modules Full refresh is not executed when one masterdata model changed 
depends on backport 0057135RR24Q2.5 scheduledTriage Platform Base Retail Modules Full refresh is not executed when one masterdata model changed 
related to defect 0056436 closedjarmendariz POS2 blank page on 1st login after deploy 
Not all the children of this issue are yet resolved or closed.

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2024-11-05 11:37 malsasua New Issue
2024-11-05 11:37 malsasua Assigned To => Retail
2024-11-05 11:37 malsasua File Added: posterminal_test.diff
2024-11-05 11:37 malsasua Triggers an Emergency Pack => No
2024-11-05 11:39 malsasua Summary Full refresh is not executed when one model changed => Full refresh is not executed when one masterdata model changed
2024-11-05 11:51 AgatheBertin Issue Monitored: AgatheBertin
2024-11-05 12:54 malsasua Assigned To Retail => Triage Platform Base
2024-11-05 13:57 malsasua Description Updated View Revisions
2024-11-05 13:57 malsasua Steps to Reproduce Updated View Revisions
2024-11-18 09:03 AugustoMauch Status new => scheduled
2024-11-21 17:30 jarmendariz Relationship added related to 0056436


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker