Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||
| ID | |||||||||||
| 0047160 | |||||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||||
| feature request | [POS2] POS | minor | have not tried | 2021-06-16 13:29 | 2022-02-01 08:07 | ||||||
| Reporter | plujan | View Status | public | ||||||||
| Assigned To | Triage Platform Base | ||||||||||
| Priority | normal | Resolution | open | Fixed in Version | |||||||
| Status | acknowledged | 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 | ||||||||||
| Merge Request Status | |||||||||||
| Review Assigned To | |||||||||||
| OBNetwork customer | No | ||||||||||
| Support ticket | |||||||||||
| Regression level | |||||||||||
| Regression date | |||||||||||
| Regression introduced in release | |||||||||||
| Regression introduced by commit | |||||||||||
| Triggers an Emergency Pack | No | ||||||||||
| Summary | 0047160: [Disaster Recovery] The feedback to the user when the cache has been deleted should be improved | ||||||||||
| Description | In the unlikely situation that the user does not realise the POS cannot properly run after cleaning the cache, currently a non clear message is shown: "Failed to execute 'transaction' on 'IDBDatabase': The database connection is closing" | ||||||||||
| Steps To Reproduce | Notice:Althought the steps described are a "laboratory scenario", there are real life scenarios where this may happen. 1. Create a ticket with some lines 2. Clean the browser cache 3. Try to pay the ticket / Try to add a product to the ticket / Try to create a new ticket 4. The message mentioned above is shown. | ||||||||||
| Proposed Solution | Other than fixing this specific problem, I would suggest to design an approach to the Disaster Recovery scenarios as a whole. Examples: How the application should behave when detecting something wrong at system level? What if the problem has not been a manual cache cleaning but a corrupted cache caused by a failure of the terminal hard drive? May something like a BSOD help? | ||||||||||
| Tags | No tags attached. | ||||||||||
| Attached Files |  CrashRecoveryMessage.png [^] (69,892 bytes) 2021-06-16 13:29
| ||||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|
 Relationships |
|
Notes |
|
| There are no notes attached to this issue. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2021-06-16 13:29 | plujan | New Issue | |
| 2021-06-16 13:29 | plujan | Assigned To | => Retail |
| 2021-06-16 13:29 | plujan | File Added: CrashRecoveryMessage.png | |
| 2021-06-16 13:29 | plujan | OBNetwork customer | => No |
| 2021-06-16 13:29 | plujan | Triggers an Emergency Pack | => No |
| 2021-10-21 14:23 | guilleaer | Assigned To | Retail => platform |
| 2021-10-21 14:23 | guilleaer | Status | new => acknowledged |
| 2022-02-01 08:07 | alostale | Assigned To | platform => Triage Platform Base |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |