IdentifiedList
Type CDM 7.2.0Attaches an identifier to a collection of objects, when those objects themselves can each be represented by an identifier. One use case is the representation of package transactions, where each component is a separate trade with its own identifier, and those trades are linked together as a package with its own identifier. The data type has been named generically rather than referring to 'packages' as it may have a number of other uses.
Extends —
Extended by —
Attributes 3
Namespace cdm.base.staticdata.identifier
Attributes
All 3 declared on IdentifiedList. Cardinality in amber is required.
| Name | Type | Card. | Description |
|---|---|---|---|
| listId | Identifier | 1..1 | The identifier for the list. In the case of a package transaction, this would be the package identifier. This attribute is mandatory to allow the list itself to be identified. |
| componentId | Identifier | 2..* | Identifiers for each component of the list. Since the data type is used to link multiple identified objects together, at least 2 components are required in the list. Creating an identified list with only 1 identified component has been deemed unnecessary, because it would just create a redundant identifier. |
| price | Price | 0..1 | The price of the package. |
Referenced by
3 types hold an IdentifiedList as an attribute.
Open IdentifiedList in the Model Browser
Walk the tree and the reference graph interactively, and switch releases to see how the type has changed. Free, no signup.