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

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0055833
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo Localizations] Localization Italymajoralways2024-06-25 11:592024-07-08 22:25
ReportermaiteView Statuspublic 
Assigned ToTriage Platform Conn 
PriorityurgentResolutionopenFixed in Version
StatusnewFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Regression date
Regression introduced by commit
Regression level
Regression introduced in release
Summary

0055833: Fiscalization error in receipt: TypeError: Failed to fetch

DescriptionIt 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 Reproduceattached 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
TagsNo tags attached.
Attached Filespng file icon terminal_log.png [^] (102,591 bytes) 2024-06-25 11:59


png file icon exception.png [^] (16,623 bytes) 2024-06-25 12:00

- Relationships Relation Graph ] Dependency Graph ]

-  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.


- 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


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker