PartyChangeInstruction
Type CDM 7.2.0Specifies instruction to change the party on a trade. This primitive instruction is used in a number of scenarios including: clearing, allocation and novation. The instrution must include a trade identifier, because a change of party effectively results in a different trade.
Attributes
All 4 declared on PartyChangeInstruction. Cardinality in amber is required.
| Name | Type | Card. | Description |
|---|---|---|---|
| counterparty | Counterparty | 1..1 | The new counterparty who is stepping into the trade. The stepping out counterparty is inferred based on the counterparty role that is being updated. |
| ancillaryParty | AncillaryParty | 0..1 | Specifies an ancillary party to be added onto the new transaction, e.g. the original executing party in an allocation. |
| partyRole | PartyRole | 0..1 | Specifies an additional party roles to be added on to the new transaction. |
| tradeId | TradeIdentifier | 1..* | The identifier to be assigned to the new trade post change of party. |
Referenced by
2 types hold a PartyChangeInstruction as an attribute.
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 |
|---|---|---|
| MapPartyChangeInstruction | returns | — |
Open PartyChangeInstruction 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.