tsrv.009.001.01
The UndertakingAmendmentResponseNotification message is sent by the advising party to the party that issued the undertaking, either directly or via one or more other parties, to notify the recipient of the acceptance or rejection by the beneficiary of the amendment. On receipt of this message or the UndertakingAmendmentResponse message, the issuer may also send the UndertakingAmendmentResponseNotification to the applicant.
Message Construction
Every ISO20022 message has at the highest level what we call ‘building blocks’. Because the message is constructed as immutable records, the association is by composition. Below you can see the relationship between the message and its constituent building blocks: For comparison, see the ISO20022 official specification
classDiagram direction LR %% UndertakingAmendmentResponseNotificationV01 recursion level 0 with max 0 class UndertakingAmendmentResponseNotificationV01{ AdditionalInformation IsoMax2000Text } UndertakingAmendmentResponseNotificationV01 *-- "1..1" Amendment9 : UndertakingAmendmentResponseNotificationDetails UndertakingAmendmentResponseNotificationV01 *-- "0..1" PartyAndSignature2 : DigitalSignature
Now, we will zero-in one-by-one on each of these building blocks.
UndertakingAmendmentResponseNotificationDetails building block
Details related to the proposed amendment response notification. Details of the amendment. For comparison, see the ISO20022 official specification
classDiagram direction tb %% Amendment9 recursion level 0 with max 1 Amendment9 *-- "1..1" UndertakingAmendmentResponseMessage1 : UndertakingAmendmentResponseMessage %% UndertakingAmendmentResponseMessage1 recursion level 1 with max 1 UndertakingAmendmentResponseMessage1 *-- "1..1" Amendment7 : UndertakingAmendmentResponseDetails UndertakingAmendmentResponseMessage1 *-- "0..1" PartyAndSignature2 : DigitalSignature
Amendment9 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
UndertakingAmendmentResponseMessage | Contents of the related UndertakingAmendmentResponse message. | UndertakingAmendmentResponseMessage1 - Required 1..1 |
AdditionalInformation building block
Additional information reported by the beneficiary. Specifies a character string with a maximum length of 2000 characters. For comparison, see the ISO20022 official specification This message is declared as Max2000Text in the ISO specification. In our implementation, it is represented in source code as IsoMax2000Text. Due to global using directives, it is treated as a System.String by the compiler and runtime.
DigitalSignature building block
Digital signature of the response notification. Entity involved in an activity. For comparison, see the ISO20022 official specification
classDiagram direction tb %% PartyAndSignature2 recursion level 0 with max 1 PartyAndSignature2 *-- "1..1" PartyIdentification43 : Party PartyAndSignature2 *-- "1..1" ProprietaryData3 : Signature %% PartyIdentification43 recursion level 1 with max 1 class PartyIdentification43{ Name IsoMax140Text CountryOfResidence CountryCode } PartyIdentification43 *-- "0..1" PostalAddress6 : PostalAddress PartyIdentification43 *-- "0..1" IParty11Choice : Identification PartyIdentification43 *-- "0..1" ContactDetails2 : ContactDetails %% ProprietaryData3 recursion level 1 with max 1 ProprietaryData3 *-- "1..1" SkipProcessing : Any
PartyAndSignature2 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
Party | Entity involved in an activity. | PartyIdentification43 - Required 1..1 |
Signature | Signature of a party. | ProprietaryData3 - Required 1..1 |
Extensibility and generalization considerations
To facilitate generalized design patterns in the system, the UndertakingAmendmentResponseNotificationV01 implementation follows a specific implementaiton pattern. First of all, UndertakingAmendmentResponseNotificationV01 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, UndertakingAmendmentResponseNotificationV01Document implements IOuterDocument. Because UndertakingAmendmentResponseNotificationV01 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type UndertakingAmendmentResponseNotificationV01.
classDiagram class IOuterRecord UndertakingAmendmentResponseNotificationV01 --|> IOuterRecord : Implements UndertakingAmendmentResponseNotificationV01Document --|> IOuterDocument~UndertakingAmendmentResponseNotificationV01~ : Implements class IOuterDocument~UndertakingAmendmentResponseNotificationV01~ { UndertakingAmendmentResponseNotificationV01 Message }
Document wrapper for serialization
The only real purpose UndertakingAmendmentResponseNotificationV01Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:tsrv.009.001.01’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using UndertakingAmendmentResponseNotificationV01.ToDocument() method. The returned UndertakingAmendmentResponseNotificationV01Document value will serialize correctly according to ISO 20022 standards.
classDiagram UndertakingAmendmentResponseNotificationV01Document *-- UndertakingAmendmentResponseNotificationV01 : Document
Sample of message format
This is an abbreviated version of what the message should look like.
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:tsrv.009.001.01">
<UdrtkgAmdmntRspnNtfctn>
<UdrtkgAmdmntRspnNtfctnDtls>
<!-- UndertakingAmendmentResponseNotificationDetails inner content -->
</UdrtkgAmdmntRspnNtfctnDtls>
<AddtlInf>
<!-- AdditionalInformation inner content -->
</AddtlInf>
<DgtlSgntr>
<!-- DigitalSignature inner content -->
</DgtlSgntr>
</UdrtkgAmdmntRspnNtfctn>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_9iPoEnltEeG7BsjMvd1mEw_-78549695"
name="UndertakingAmendmentResponseNotificationV01"
definition="The UndertakingAmendmentResponseNotification message is sent by the advising party to the party that issued the undertaking, either directly or via one or more other parties, to notify the recipient of the acceptance or rejection by the beneficiary of the amendment. On receipt of this message or the UndertakingAmendmentResponse message, the issuer may also send the UndertakingAmendmentResponseNotification to the applicant."
registrationStatus="Registered"
messageSet="_SiMuI9n1EeGEPsbnW6ebrw"
xmlTag="UdrtkgAmdmntRspnNtfctn"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_9iPoE3ltEeG7BsjMvd1mEw_-1088327263"
name="UndertakingAmendmentResponseNotificationDetails"
definition="Details related to the proposed amendment response notification."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="UdrtkgAmdmntRspnNtfctnDtls"
complexType="_9_wDcHltEeG7BsjMvd1mEw_-868509945" />
<messageBuildingBlock
xmi:id="_Xldnk387EeGx884K2iQOLg"
name="AdditionalInformation"
definition="Additional information reported by the beneficiary."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="AddtlInf"
simpleType="_YYn11dp-Ed-ak6NoX_4Aeg_2132907481" />
<messageBuildingBlock
xmi:id="_9iPoFHltEeG7BsjMvd1mEw_1375957956"
name="DigitalSignature"
definition="Digital signature of the response notification."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="DgtlSgntr"
complexType="_k4nFNZKuEeGnRMFvqYmPBQ" />
<messageDefinitionIdentifier
businessArea="tsrv"
messageFunctionality="009"
flavour="001"
version="01" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.