The release notes detail the scope of CDE uplift, available on 1 March 2021, including details of the available functionality in the CDE environment. This CDE uplift is accompanied by the February 2021 documentation update. Full details of the functionality are provided below.
AMQP users should be advised that as part of this release, any uncollected / egress ISO messages will be expired and subsequently purged after 10 business days. This is to support housekeeping activities.
Please note the following points for your consideration:
On CDE reset, corporate actions with dates in the past will be removed from seeding to avoid incomplete corporate action lifecycles.
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 from 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.
Party Identification in CDE 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.
Ledger API Connectivity Users Only: CDE9 introduced Public Parties and Public Contracts. Public Parties are observers created and on-boarded by ASX that have permission to access active public contracts available to all market participants such as Calendars, Securities and Issuers. Refer to Contracts Overview and Reference Data API Contracts for further information.
Payment Provider Environment Only: The Auto-Responder will be uplifted to respond as a Payment Provider in workflows involving funds obligations. Any customers who would like to test this functionality as a Payment Provider are required to opt-in by notifying CTS. Paying Payment Providers must not submit a rejection Funds Obligation Status Advice (sett_135) message in response to a Funds Obligation (sett_133) message with an Authorisation Reason of Funds Authorisation (PFAU) that is received during Batch Settlement. Providing a rejection response in this scenario will cause Batch Settlement to not complete and the only remediation will be an environment reset.