View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008128 | 10000-110: Asset Management Basics | Spec | public | 2022-07-22 15:18 | 2022-10-10 07:05 |
| Reporter | Wolfgang Mahnke | Assigned To | Wolfgang Mahnke | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Summary | 0008128: Clarification on changes of AssetId, Aliases and NodeVersion and ModelChangeEvents | ||||
| Description | When an AssetId changes (can potentially be done by the enduser), the BrowseName of the Alias Object has to change. Do we expect such a change to trigger a NodeVersion update and a ModelChangeEvent (if supported) from the AliasCategory? | ||||
| Tags | No tags attached. | ||||
| Commit Version | |||||
| related to | 0008321 | closed | Paul Hunkar | 10000-017: Alias Names | NodeVersion / ModelChangeEvents and change of BrowseName of Aliases |
|
|
Discussed in Harmonization Working Group: Extension to use case: Some environments do not allow changing BrowseName, so implementation requires deleting and recreating Node with new BrowseName (which also implies that ModelChangeEvent / NodeVersion need to change). |
|
|
Fixed in Alias Name (see related issue), therefore no fix in this specification needed. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-07-22 15:18 | Wolfgang Mahnke | New Issue | |
| 2022-07-22 15:18 | Wolfgang Mahnke | Status | new => assigned |
| 2022-07-22 15:18 | Wolfgang Mahnke | Assigned To | => Wolfgang Mahnke |
| 2022-09-13 09:07 | Wolfgang Mahnke | Note Added: 0017632 | |
| 2022-09-13 10:27 | Wolfgang Mahnke | Relationship added | related to 0008321 |
| 2022-10-10 07:05 | Wolfgang Mahnke | Status | assigned => closed |
| 2022-10-10 07:05 | Wolfgang Mahnke | Resolution | open => fixed |
| 2022-10-10 07:05 | Wolfgang Mahnke | Note Added: 0017982 |
