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

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0027216
TypeCategorySeverityReproducibilityDate SubmittedLast Update
design defect[Retail Modules] Web POSminoralways2014-07-28 17:322014-10-06 16:52
ReporterjecharriView Statuspublic 
Assigned Tomarvintm 
PriorityurgentResolutionopenFixed 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
Summary

0027216: Stabilization: Web POS should not login if the database is not consistent or a table is empty

DescriptionWeb POS should not login if the database is not consistent or a table is empty
Steps To ReproduceFor example
-If you do not define any product to Web POS it should not login
-If due to a connection error suddenly the business partner table is empty (or any other), it should not login
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
depends on feature request 0027329 newRetail Stabilization: Overhaul the loading process (since the url is entered until the webpos has loaded) 
related to defect 0026589 closedOrekaria Stabilization: When the backend generates a new uuid.js, chrome does not update/delete the Web SQL database 
Not all the children of this issue are yet resolved or closed.

-  Notes
(0070735)
mtaal (manager)
2014-10-06 11:21

This issue has 2 sides to it. From one side we will implement in the mid-term a loading mechanism which can handle more pessismistic cases.

For now to solve/prevent the issue we will add a check that before showing the webpos that the client database is checked. If there are no products or business partners then the system should show a message and logout. The message should show which table is empty.

There are no products in the local database, the application will logout. Please try again to login and contact your administrator if this happens repeatedly,

or

There are no business partners in the local database, the application will logout. Please try again to login and contact your administrator if this happens repeatedly,


- Issue History
Date Modified Username Field Change
2014-07-28 17:32 jecharri New Issue
2014-07-28 17:32 jecharri Assigned To => marvintm
2014-07-28 17:32 jecharri Resolution time => 1409608800
2014-07-28 17:32 jecharri Triggers an Emergency Pack => No
2014-07-28 17:33 jecharri Resolution time 1409608800 => 1412978400
2014-07-28 17:33 jecharri Severity major => minor
2014-07-29 17:05 jecharri Summary Web POS should not login if the database is not consistent of a table is empty => Web POS should not login if the database is not consistent or a table is empty
2014-07-29 17:05 jecharri Description Updated View Revisions
2014-07-29 17:27 jecharri Issue cloned 0027228
2014-08-13 19:50 Orekaria Relationship added depends on 0027329
2014-08-18 15:05 Orekaria Relationship added related to 0026589
2014-08-22 09:51 Orekaria Summary Web POS should not login if the database is not consistent or a table is empty => Stabilization: Web POS should not login if the database is not consistent or a table is empty
2014-10-06 11:21 mtaal Note Added: 0070735
2014-10-06 11:21 mtaal Type defect => design defect
2014-10-06 16:52 mtaal Target Version RR14Q4 =>


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker