Identifier
Type CDM 7.2.0A class to specify a generic identifier, applicable to CDM artefacts such as executions, contracts, lifecycle events and legal documents. An issuer can be associated with the actual identifier value as a way to properly qualify it.
Extends —
Attributes 3
Namespace cdm.base.staticdata.identifier
Attributes
All 3 declared on Identifier. Cardinality in amber is required.
| Name | Type | Card. | Description |
|---|---|---|---|
| issuerReference | Party | 0..1 | The identifier issuer, when specified by reference to a party specified as part of the transaction. |
| issuer | string | 0..1 | The identifier issuer, when specified explicitly alongside the identifier value (instead of being specified by reference to a party). |
| assignedIdentifier | AssignedIdentifier | 1..* | The identifier value. This level of indirection between the issuer and the identifier and its version provides the ability to associate multiple identifiers to one issuer, consistently with the FpML PartyTradeIdentifier. |
Conditions
Validation rules the model enforces on this type, in Rune. An instance that breaks one of these is invalid CDM, whatever produced it.
IssuerChoice Condition
The identifier issuer is specified either explicitly or by reference to one of the parties.
required choice issuerReference, issuerReferenced by
15 types hold an Identifier as an attribute.
BusinessUnitCollateralCollateralPortfolioContractualDefinitionEligibleCollateralSpecificationExecutionInstructionFloatingRateIndexMapIdentifiedListLegalAgreementBaseMarginCallBasePartyAgreementIdentifierQuantityChangeInstructionTradeLotTransferBaseWorkflowStep
Functions
Model functions that produce or consume this type. These are the CDM's own behaviour — the logic a correct implementation has to match.
| Function | Role | Description |
|---|---|---|
| MapIssuerTradeIdModelToIdentifier | returns | — |
| MapPortfolioNameToIdentifier | returns | — |
| MapEventIdentifier | returns | — |
| Create_PairOffInstruction | takes | Creates a set of instructions to pair-off a set of trades based on a pair reference. A package component is created based on that pair reference and the list of identifiers for the underlying trades. That package component is then added onto the execution details of every underlying trade. The existing trades are not terminated. |
| Create_ShapingInstruction | takes | Creates a set of instructions to shape a trade based on shaped quantities and a package ID. The original trade is closed and split into (smaller) shaped trades based on a set of trade lots containing the shaped quantities and an identifier for each shaped trade. A package component is created based on the package ID and the list of identifiers for the shaped trades. That package component is then added onto the execution details of every shaped trade. |
| Create_PackageExecutionDetails | takes | Add a package component to an execution details object. This package component is constructed using an identifier for the package and the list of identifiers for its components. |
| Create_WorkflowStep | takes | Function to create a workflow step with a business event and associated details about the message, identifiers, event timestamps, parties and accounts involved in the step. The function should be used when there is already a fully formed business event with the action set to signify that the step is new, or a correction/cancellation of a previous step. The action is constrained so that when a previous workflow step is specified, the valid actions are as follows; New -> New, New -> Correct, New -> Cancel, Correct -> Correct and Correct -> Cancel. When a previous workflow is not specified, the action must be New. |
| Create_AcceptedWorkflowStep | takes | Represents the acceptance of a proposed instruction that results in a workflow step containing a business event, message details, identifiers, event timestamps, parties and accounts. The previous workflow step input must exist to provide workflow lineage. The instruction from the previous workflow step should be used with a [creation BusinessEvent] function to create the input business event passed into this function e.g. PartyChangeInstruction from the previous step is used with Create_PartyChange to produce the business event which should used as an input to this step. |
| Create_ProposedWorkflowStep | takes | Represents the proposal to create a business event that results in a workflow step containing an instruction, message details, identifiers, event timestamps, parties and accounts. The optional previous workflow step input provides workflow lineage to where there has been a correction or cancellation to the proposed step. The action is constrained so that when a previous workflow step is specified, the valid actions are as follows; New -> Correct and Correct -> Cancel. When a previous workflow is not specified, the action must be New. |
| Create_RejectedWorkflowStep | takes | Represents the rejection of a proposed instruction that results in a workflow step containing the rejection flag, message details, identifiers, event timestamps, parties and accounts involved in the step. The previous workflow step input must exist to provide workflow lineage. This function will be further developed to provide the reasons for rejection. |
| FilterTradeLot | takes | Filter list of TradeLot based on TradeLot->lotIdentifier. |
Open Identifier 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.