Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
| ID | ||||||||||||
| 0029811 | ||||||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
| feature request | [Retail Modules] Web POS | major | always | 2015-05-07 14:53 | 2016-10-27 21:46 | |||||||
| Reporter | Orekaria | View Status | public | |||||||||
| Assigned To | Retail | |||||||||||
| Priority | normal | Resolution | open | Fixed in Version | ||||||||
| Status | new | Fix in branch | Fixed in SCM revision | |||||||||
| Projection | none | ETA | none | Target Version | ||||||||
| OS | Any | Database | Any | Java version | ||||||||
| OS Version | Database version | Ant version | ||||||||||
| Product Version | SCM revision | |||||||||||
| Review Assigned To | ||||||||||||
| Regression level | ||||||||||||
| Regression date | ||||||||||||
| Regression introduced in release | ||||||||||||
| Regression introduced by commit | ||||||||||||
| Triggers an Emergency Pack | No | |||||||||||
| Summary | 0029811: Better handling of critical, application breaking errors | |||||||||||
| Description | Better handling of critical, application breaking errors The problem is that if an unhandled exception is risen an error is being shown in the messages' bubble but it gives no information to the user about what actions should be done | |||||||||||
| Steps To Reproduce | provoke an unhandled error. e.g: add receipt.set('bp', null) to the 'requirementsAreMet' method of the 'toolbar-left.js' file: ... var receipt = model.get('order'); receipt.set('bp', null); requirements.isReceipt = !OB.UTIL.isNullOrUndefined(receipt); ... logging into the webpos will create a receipt with no business partner verify that when a new product is added, an unhandled exception is thrown verify that the message is shown in the messages' bubble verify that the same message is shown again and again | |||||||||||
| Proposed Solution | show a popup to the user reporting about the error and the actions that should be taken the actions could include or combine, reporting the system administrator, reloading the webpos, mark the error as not to be shown again | |||||||||||
| Tags | No tags attached. | |||||||||||
| Attached Files |  Error_Reload_New-v2.1.png [^] (96,314 bytes) 2016-10-27 21:08
Error_Reload_New-v2.2.png [^] (71,846 bytes) 2016-10-27 21:08
WarningIcon.png [^] (1,618 bytes) 2016-10-27 21:46
| |||||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|||||||||||||||
|
|||||||||||||||
 Relationships |
|
Notes |
|
|
(0090966) dbaz (developer) 2016-10-27 21:12 |
Attached tentative mockups. If the user decides to continue after the red popup, a warning should be shown in the SCAN area. If this warning box is pressed, the red popup will be shown again. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2015-05-07 14:53 | Orekaria | New Issue | |
| 2015-05-07 14:53 | Orekaria | Assigned To | => Retail |
| 2015-05-07 14:53 | Orekaria | Triggers an Emergency Pack | => No |
| 2015-05-07 14:54 | Orekaria | Steps to Reproduce Updated | View Revisions |
| 2015-05-07 14:55 | Orekaria | Issue Monitored: dmitry_mezentsev | |
| 2015-05-08 15:10 | Orekaria | Relationship added | related to 0029778 |
| 2016-10-27 21:08 | dbaz | File Added: Error_Reload_New-v2.1.png | |
| 2016-10-27 21:08 | dbaz | File Added: Error_Reload_New-v2.2.png | |
| 2016-10-27 21:12 | dbaz | Note Added: 0090966 | |
| 2016-10-27 21:46 | dbaz | File Added: WarningIcon.png | |
| 2016-10-27 22:15 | dbaz | Relationship added | related to 0034327 |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |