Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
| ID | ||||||||
| 0055833 | ||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
| defect | [Openbravo Localizations] Localization Italy | major | always | 2024-06-25 11:59 | 2024-07-26 08:56 | |||
| Reporter | maite | View Status | public | |||||
| Assigned To | Triage Platform Conn | |||||||
| Priority | urgent | Resolution | fixed | Fixed in Version | ||||
| Status | closed | 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 | |||||||
| Regression date | ||||||||
| Regression introduced by commit | ||||||||
| Regression level | ||||||||
| Regression introduced in release | ||||||||
| Summary | 0055833: Fiscalization error in receipt: TypeError: Failed to fetch | |||||||
| Description | It is possible to fiscalize the same ticket several times when the "Failed to fetch" exception is thrown by the fiscal printer: the exception is caught but the ticket is fiscalized, then the user presses on the "retry" option and the ticket is fiscalized again. At any point, the fiscal printer answer is Sucess so the ticket is finally synchronized from the till (and fiscalized again) | |||||||
| Steps To Reproduce | attached screenshot from the terminal log where the "Failed to fetch" error can be shown attached screenshot of the point of code where the exception is caught no related information is found in the HWM log | |||||||
| Tags | No tags attached. | |||||||
| Attached Files |  terminal_log.png [^] (102,591 bytes) 2024-06-25 11:59
exception.png [^] (16,623 bytes) 2024-06-25 12:00
| |||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|
 Relationships |
|
Notes |
|
|
(0166604) psanjuan (manager) 2024-07-02 14:25 edited on: 2024-07-02 14:29 |
It is important to understand why "Failed to fetch" error is shown. Our proposal is to implement a more detailed log to understand what is the current status of the connectivity with the printer, and the network request sent. Besides this, we need to implement a way for the seller to indicate if a "Documento Commerciale" (simplified Invoice) has been printed under this scenario, with some field to indicate the "Document No" and the "Z Report", so we avoid to "Retry" the call to the Printer a second time. |
|
(0167373) hgbot (developer) 2024-07-26 08:53 |
Repository: https://gitlab.com/openbravo/product/pmods/org.openbravo.events.fiscalrtprinter [^] Changeset: 3d3efb2e6a5968629f57e8c855fa07e6336f8ac2 Author: Fermín Gascón <f.gascon@orisha.com> Date: 26-07-2024 06:53:25 URL: https://gitlab.com/openbravo/product/pmods/org.openbravo.events.fiscalrtprinter/-/commit/3d3efb2e6a5968629f57e8c855fa07e6336f8ac2 [^] [RM-14956] Confirmation after fetch error and rounding Fixes ISSUE-55833: Fiscalization error in receipt: TypeError: Failed to fetch Fixes ISSUE-55989: RTPrinter rounding issue --- M src-db/database/sourcedata/AD_MESSAGE.xml M web/org.openbravo.events.fiscalrtprinter/res/fiscalreceipt.xml M web/org.openbravo.events.fiscalrtprinter/source/RTPrinterFiscalization.js M web/org.openbravo.events.fiscalrtprinter/source/model/utils/formatFunctions.js --- |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2024-06-25 11:59 | maite | New Issue | |
| 2024-06-25 11:59 | maite | Assigned To | => psanjuan |
| 2024-06-25 11:59 | maite | File Added: terminal_log.png | |
| 2024-06-25 12:00 | maite | File Added: exception.png | |
| 2024-07-02 14:25 | psanjuan | Note Added: 0166604 | |
| 2024-07-02 14:29 | psanjuan | Note Edited: 0166604 | View Revisions |
| 2024-07-08 22:25 | jonae | Assigned To | psanjuan => Triage Platform Conn |
| 2024-07-26 08:53 | hgbot | Resolution | open => fixed |
| 2024-07-26 08:53 | hgbot | Status | new => resolved |
| 2024-07-26 08:53 | hgbot | Note Added: 0167373 | |
| 2024-07-26 08:56 | adrianromero | Status | resolved => closed |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |