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

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0056377
TypeCategorySeverityReproducibilityDate SubmittedLast Update
feature request[POS2] Corecriticalhave not tried2024-09-05 11:562024-10-10 13:26
ReporterAugustoMauchView Statuspublic 
Assigned ToAugustoMauch 
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

0056377: Management of inconsistent application state should be properly addressed in core2 applications

DescriptionFrom time to time, the application state gets inconsistent, apparently not reflecting the current state of the application but a previous one.

We looking for those inconsistencies on a case-to-case basis, and introducing mitigation measures on a case-to-case basis as well.

This mechanism should be improved, so that if any inconsistency is found, all the application state modules should be re-initialized properly.
Steps To Reproduce-
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
related to feature request 0056730 scheduledranjith_qualiantech_com POS2 Management of inconsistent application state should be properly addressed in EnyoPOS 
related to feature request 0054707 newAugustoMauch Retail Modules Add support to select the state persistence method (localstorage vs indexed db) 
related to defect 0054743 closedsreehari Retail Modules When the state persistence fails, the information of the cashup becomes outdated, and this can lead to data corruption 
related to defect 0056263 closedranjith_qualiantech_com Retail Modules Mitigation https://issues.openbravo.com/view.php?id=52070 [^] should not create a new cashup in POS 
related to backport 005207023Q2 closedmeriem_azaf POS2 Cashup mitigation: do not check if current cashup is the last one processed, just check if it is processed 
related to defect 0056246 closedsreehari POS2 Implement second Mitigation for duplicating document sequence number 

-  Notes
(0170023)
hgbot (developer)
2024-10-06 12:55

Merge Request created: https://gitlab.com/openbravo/product/pmods/org.openbravo.core2/-/merge_requests/1604 [^]
(0170024)
hgbot (developer)
2024-10-06 12:57

Merge Request created: https://gitlab.com/openbravo/product/pmods/org.openbravo.mobile.core/-/merge_requests/755 [^]
(0170025)
hgbot (developer)
2024-10-06 13:00

Merge Request created: https://gitlab.com/openbravo/product/pmods/org.openbravo.retail.posterminal/-/merge_requests/1699 [^]

- Issue History
Date Modified Username Field Change
2024-09-05 11:56 AugustoMauch New Issue
2024-09-05 11:56 AugustoMauch Assigned To => AugustoMauch
2024-09-05 11:56 AugustoMauch Triggers an Emergency Pack => No
2024-09-05 12:03 AugustoMauch Status new => scheduled
2024-09-17 09:23 Practics Issue Monitored: Practics
2024-10-06 12:55 hgbot Note Added: 0170023
2024-10-06 12:57 hgbot Note Added: 0170024
2024-10-06 13:00 hgbot Note Added: 0170025
2024-10-10 11:51 AugustoMauch Summary Management of inconsistent application state should be properly addressed => Management of inconsistent application state should be properly addressed in core2 applications
2024-10-10 11:52 AugustoMauch Issue cloned 0056730
2024-10-10 11:55 AugustoMauch Relationship added related to 0056730
2024-10-10 13:26 eugeni Issue Monitored: eugeni
2024-10-31 13:04 malsasua Relationship added related to 0054707
2024-10-31 13:10 malsasua Relationship added related to 0054743
2024-10-31 13:10 malsasua Relationship added related to 0056263
2024-10-31 13:11 malsasua Relationship added related to 0052070
2024-10-31 13:17 malsasua Relationship added related to 0056246


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker