Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
| ID | ||||||||
| 0038783 | ||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
| defect | [Modules] External Data Integration | major | always | 2018-06-18 13:56 | 2018-06-25 18:30 | |||
| Reporter | javietxe | View Status | public | |||||
| Assigned To | AugustoMauch | |||||||
| Priority | normal | 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 | ||||||||
| Review Assigned To | caristu | |||||||
| Regression introduced in release | ||||||||
| Summary | 0038783: SERQA 221 EDL: RequestDate after Executed date | |||||||
| Description | When a synchronous EDL fails, sometimes the RequestDate is a date after the Executed, and this should not happen anytime as the description of the fields are: - RequestDate: Date of the reception of the request - Executed: Date of the finishing of processing. | |||||||
| Steps To Reproduce | Integrate any synchronous EDL with error. | |||||||
| Tags | No tags attached. | |||||||
| Attached Files | ||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|
 Relationships |
|
Notes |
|
|
(0105199) AugustoMauch (manager) 2018-06-18 18:40 |
Repository: erp/pmods/org.openbravo.externaldata.integration Changeset: e32866258863777e7844e870be26019e14d6148d Author: Augusto Mauch <augusto.mauch <at> openbravo.com> Date: Mon Jun 18 18:02:17 2018 +0200 URL: http://code.openbravo.com/erp/pmods/org.openbravo.externaldata.integration/rev/e32866258863777e7844e870be26019e14d6148d [^] [^] Fixes issue 38783: ExecutionDate is properly set when the EDLRequest fails The problem was that if the request failed, the executionDate was not being set. In that case the default database value remained, if there were differente in the database and the JVM clock, the execution date could be < than the creation date, which did not make sense. --- M src/org/openbravo/externaldata/integration/process/ProcessRequest.java |
|
(0105369) caristu (manager) 2018-06-25 18:30 |
Reviewed |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2018-06-18 13:56 | javietxe | New Issue | |
| 2018-06-18 13:56 | javietxe | Assigned To | => platform |
| 2018-06-18 13:56 | javietxe | Resolution time | => 1530482400 |
| 2018-06-18 14:07 | javietxe | Summary | SERQA 221 EDL: RequestDate before Executed date => SERQA 221 EDL: RequestDate after Executed date |
| 2018-06-18 14:07 | javietxe | Description Updated | View Revisions |
| 2018-06-18 18:40 | AugustoMauch | Status | new => scheduled |
| 2018-06-18 18:40 | AugustoMauch | Note Added: 0105199 | |
| 2018-06-18 18:40 | AugustoMauch | Status | scheduled => resolved |
| 2018-06-18 18:40 | AugustoMauch | Resolution | open => fixed |
| 2018-06-19 11:57 | AugustoMauch | Review Assigned To | => caristu |
| 2018-06-19 11:57 | AugustoMauch | Assigned To | platform => AugustoMauch |
| 2018-06-25 18:30 | caristu | Note Added: 0105369 | |
| 2018-06-25 18:30 | caristu | Status | resolved => closed |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |