Openbravo Issue Tracking System - Modules | |||||
View Issue Details | |||||
ID | Project | Category | View Status | Date Submitted | Last Update |
0036378 | Modules | External Data Integration | public | 2017-06-30 09:47 | 2022-02-01 08:08 |
Reporter | caristu | ||||
Assigned To | Triage Platform Base | ||||
Priority | high | Severity | minor | Reproducibility | N/A |
Status | new | Resolution | open | ||
Platform | OS | 5 | OS Version | ||
Product Version | |||||
Target Version | Fixed in Version | ||||
Merge Request Status | |||||
Regression date | |||||
Regression introduced by commit | |||||
Regression level | |||||
Review Assigned To | |||||
Support ticket | |||||
OBNetwork customer | |||||
Regression introduced in release | |||||
Summary | 0036378: Not possible to separate failed items on OutputDataProcessor processing | ||||
Description | Currently in EDL processes designed to have an output, it is not to possible to separate failed items in an "error" request line if the processing of that item fails in the processing done by the OutputDataProcessor. It would be nice to have this behavior in the output part of the process. Currently this is only happening during the processing of the item by the ItemProcessor. | ||||
Steps To Reproduce | In description | ||||
Proposed Solution | Add the ability to support a hook in the AsynchronousProcessor class to allow the processing of a new type of OutputDataProcessor. It will separate the processed items that failed during the output process in a different request line (error batch). | ||||
Additional Information | |||||
Tags | No tags attached. | ||||
Relationships | |||||
Attached Files | |||||
Issue History | |||||
Date Modified | Username | Field | Change | ||
2017-06-30 09:47 | caristu | New Issue | |||
2017-06-30 09:47 | caristu | Assigned To | => platform | ||
2017-06-30 11:12 | caristu | Summary | Not possible to separate failed items from OutputDataProcessor objects => Not possible to separate failed items on OutputDataProcessor processing | ||
2017-08-03 10:22 | caristu | Proposed Solution updated | |||
2022-02-01 08:08 | alostale | Assigned To | platform => Triage Platform Base |
There are no notes attached to this issue. |