View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008644 | 10000-011: Historical Access | Spec | public | 2023-01-24 05:49 | 2023-03-14 15:41 |
| Reporter | Paul Hunkar | Assigned To | Paul Hunkar | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 1.04 | ||||
| Target Version | 1.05.03 RC1 | Fixed in Version | 1.05.03 RC1 | ||
| Summary | 0008644: History of events - does not explain EventId requirements well enough | ||||
| Description | When Events are being being generated, the Event server will attach unique EventId to all Events. This EventId allows a specific event to be uniquely identified. When historizing event this unique id is required to be stored. When modifying events, the EventId also has to be preserved. When insert new events, then the client may not be able to generate an appropriate EventId and the field will need to be left blank, and the server will generate a unique Eventd for the inserted event. | ||||
| Tags | No tags attached. | ||||
| Commit Version | |||||
| Fix Due Date | |||||
|
|
Updated text to better reflect EventIds and there requirements. |
|
|
Agreed to changes edited in Web Meeting. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-01-24 05:49 | Paul Hunkar | New Issue | |
| 2023-01-24 05:49 | Paul Hunkar | Status | new => assigned |
| 2023-01-24 05:49 | Paul Hunkar | Assigned To | => Paul Hunkar |
| 2023-01-24 06:02 | Paul Hunkar | Status | assigned => resolved |
| 2023-01-24 06:02 | Paul Hunkar | Resolution | open => fixed |
| 2023-01-24 06:02 | Paul Hunkar | Fixed in Version | => 1.05.03 RC1 |
| 2023-01-24 06:02 | Paul Hunkar | Note Added: 0018555 | |
| 2023-03-14 15:41 | Jim Luth | Status | resolved => closed |
| 2023-03-14 15:41 | Jim Luth | Note Added: 0018863 |
