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

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0056730
TypeCategorySeverityReproducibilityDate SubmittedLast Update
feature request[POS2] Coremajorhave not tried2024-10-10 11:522024-10-24 07:54
ReporterAugustoMauchView Statuspublic 
Assigned Toranjith_qualiantech_com 
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

0056730: Management of inconsistent application state should be properly addressed in EnyoPOS

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.

Note, the backend infra to support this, and the frontend infra for core2 applications has already been developed here: https://issues.openbravo.com/view.php?id=56377. [^] This issue should only address the missing piece, which is to consume the backend API during the login process to check the validity of the state, and reset the state accordingly if it is not valid. Similar to what is done in core2 applications here: https://gitlab.com/openbravo/product/pmods/org.openbravo.core2/-/merge_requests/1604/diffs#a9f9ead2b85fe0a0ffdef835b186359c141b3b79_41_42 [^]
Steps To Reproduce-
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
related to feature request 0056377 scheduledAugustoMauch Management of inconsistent application state should be properly addressed in core2 applications 

-  Notes
(0170860)
hgbot (developer)
2024-10-24 07:54

Merge Request created: https://gitlab.com/openbravo/product/pmods/org.openbravo.mobile.core/-/merge_requests/763 [^]

- Issue History
Date Modified Username Field Change
2024-10-10 11:52 AugustoMauch New Issue
2024-10-10 11:52 AugustoMauch Assigned To => AugustoMauch
2024-10-10 11:52 AugustoMauch Triggers an Emergency Pack => No
2024-10-10 11:52 AugustoMauch Issue generated from 0056377
2024-10-10 11:52 AugustoMauch Assigned To AugustoMauch => marvintm
2024-10-10 11:54 AugustoMauch Description Updated View Revisions
2024-10-10 11:55 AugustoMauch Relationship added related to 0056377
2024-10-10 13:28 eugeni Issue Monitored: eugeni
2024-10-10 17:04 marvintm Assigned To marvintm => ranjith_qualiantech_com
2024-10-10 17:04 marvintm Status new => acknowledged
2024-10-21 03:11 ranjith_qualiantech_com Status acknowledged => scheduled
2024-10-24 07:54 hgbot Note Added: 0170860


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker