View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008410 | 10000-004: Services | Spec | public | 2022-10-14 15:23 | 2022-12-07 14:40 |
| Reporter | Paul Hunkar | Assigned To | Paul Hunkar | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Product Version | 1.05.02 | ||||
| Target Version | 1.05.03 RC1 | Fixed in Version | 1.05.03 RC1 | ||
| Summary | 0008410: History retrieval needs a new error code | ||||
| Description | if a historian does not support an index range processing for a historical data, it should be possible to report this error with a specific errorCode - need to define an errorcode | ||||
| Tags | No tags attached. | ||||
| Commit Version | |||||
| Fix Due Date | |||||
|
|
Table 58 – HistoryRead Operation Level Result Codes Added index range status codes we have also in Read: Not sure why we need others - I assume IndexRange processing is required for ReadHistory (as it is of Read). |
|
|
Agreed to changes in Virtual F2F. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-10-14 15:23 | Paul Hunkar | New Issue | |
| 2022-11-08 17:04 | Jim Luth | Assigned To | => Paul Hunkar |
| 2022-11-08 17:04 | Jim Luth | Status | new => assigned |
| 2022-12-06 20:30 | Matthias Damm | Status | assigned => resolved |
| 2022-12-06 20:30 | Matthias Damm | Resolution | open => fixed |
| 2022-12-06 20:30 | Matthias Damm | Fixed in Version | => 1.05.03 RC1 |
| 2022-12-06 20:30 | Matthias Damm | Note Added: 0018255 | |
| 2022-12-07 14:40 | Jim Luth | Status | resolved => closed |
| 2022-12-07 14:40 | Jim Luth | Note Added: 0018261 |
