The release notes detail the scope of the eighth drop of CDE code, released on 11 September 2020, including details of the available functionality in the CDE environment. This CDE code drop is accompanied by the September 2020 What’s New documentation update. Full details of the functionality are provided below.
CDE Drop 8 includes breaking changes to both the Business Application Header (BAH) and Ledger API Connectivity. For further information, refer to the September 2020 What's New.
Please note the following points for your consideration:
[Updated 21/09] On CDE reset, corporate actions with dates in the past will be removed from seeding to avoid incomplete corporate action lifecycles.
[Updated 17/09] To assist software provider testing of ISO message pagination the number of records included in the Netting Obligation Report (NOR) (sett_102) has been reduced from 100 to 10, software providers therefore can test pagination with a reduced number of trades. This value has been lowered in CDE8 for the purpose of testing, the number of trades which will be included in the production environment will be defined at a later date.
Takeover and Buy-back functionality introduced Bid Offerors. To opt-in as a Bid Offeror, click here.
Party Identification in CDE Drop 8 is limited to UIC format only. BIC support will be available in a subsequent release.
For Ledger API connectivity, both ISO 20022 ingress and egress instructions are supported. Please note, resultant state change contracts may be visible, but are not documented in this release and are subject to change.
Final security, resiliency and fail-over models are not present in the CDE Environment.
Transactional data may be lost in the event of a system restart or upgrade. The ASX will re-populate environments with seeded data.
For internal CDE maintenance, ASX may refresh environment every two weeks. ASX will always notify CDE Subscribers prior to any environment refresh.
As part of CDE Drop 7, CDE subscribers were unable to act as the ETO Clearing Member in the collateral management process via the Collateral Management Auto-Responder. This limitation has been resolved as part of CDE8. Refer to Collateral Creation / Removal for further details.
CDE 8 includes a breaking change discussed in earlier ISO 20022 Technical Committees to include the Business Date in the Business Application Header (BAH). As such, the BAH version must be adjusted from v1 to v2 to use the new ISO schema. Further details are available in the September 2020 What's New.
The ability to lock holdings of an account (the entire holding balance or a portion of the holding balance) in response to a request from an Issuer (Registry), ASX, Controlling Participant, Regulators or Law Enforcement Agencies.
CDE Drop 8 includes the workflow for Holding Administration Locking and Unlocking.
The ability for a Clearing Participant (who is a Settlement Participant) or a Settlement Participant (acting on behalf of a Clearing Participant) due to receive units from a failed Novated Settlement Obligation to request isolation of a number of units together with the disclosure of the UIC of the failing Clearing/Settlement Participant
CDE Drop 8 includes the workflow for Isolate Counterparty.
The ability for participants to use the RTGS payment service for Bilateral Demand Settlement Instructions where the required arrangements and Payment Facility set-up has taken place between the Payment Provider and the Participant.
CDE Drop 8 includes the payment provider authorisation for RTGS payments workflow for Bilateral Demand Settlement Instructions.