Customer Development Environment (CDE)
This section covers: customer development environment (CDE)
CDE was decommissioned at the end of February 2022 and is no longer an active test environment. All information related to CDE was at a point in time only, but continues to be made available for historical reference purposes.
Children Pages
- CDE Known Issues & Limitations
- Support for CDE
- CDE Application Forms
- Technical Constraints
- CDE Test Tools
- CDE Self-Service Tools
- CDE Bid Finalisation of Takeover and Buybacks
- CDE Code Change
- CDE Daily Margin Settlement Advice
- CDE Instances for Issuer Registries
- CDE Market Trade and Batch Settlement
- CDE Instances for Payment Providers
- CDE Auto-responders
- CDE Issuer to Participant Transfer / Conversion
- CDE Bilateral Demand Transfer
- CDE Bilateral Demand Settlement Instruction
- CDE SRN / SRN Balance Enquiry
- CDE Collateral Creation / Removal
- CDE Investor Data - Bank Account Notification
- CDE Bilateral Settlement Instruction
- CDE Cash Market Margin (CMM) Change Margin Settlement Amount
- CDE Payment Provider Authorisation
- CDE Bid Election / Election Withdrawal
- CDE mFund Application and Redemption
- CDE Reserve Bank Information & Transfer System (RITS)
- CDE DRP/BSP Election and Election Enquiry
- CDE Connectivity
- CDE Test Data
Overview
CDE follows the development cycle of the CHESS Replacement project. Functionality, security features and test capabilities will be progressively added to the environment during the life of the project in iterative cycles of approximately 8 weeks, targeting full functionality by May 2020.
The Customer Development Environment (CDE) provides an isolated application development and low volume testing environment for CSP users and vendors.
The environment allows users to test connectivity options and progressively test functionality as it is made available. It will be seeded with static data, such as calendars, issuers, securities and participant information.
The Auto-responder account will also be provided to allow for the simulation of specific test scenarios; such as auto matching bilateral requests.
In case of environment reset, either due to functionality uplift or error, all data will be reset, including ASX seeded data and customer transaction data. It is recommended that users automate test preparation scripts to the fullest extent possible, so that client testing can resume quickly post the reset of an environment.
Objective
The objective of CDE testing is to assist users to:
- Validate different connectivity options and daily processing schedules
- Implement changes to internal systems, interfaces and communication links as required
- Undertake functional testing of their internal systems and interfaces
- Update internal operating processes and procedures
- Achieve internal audit/operational sign-off for all system and procedural changes
Approach
To assist all users and vendors, the ASX will:
- Deliver CSP Functionality incrementally every ~8 weeks, as per timeline
As part of each CDE release, the ASX will support CDE user testing by providing information on the following:
- Scope of each release,
- Connectivity options,
- Test Environment support (Test data),
- The Auto-responder feature,
- Any known issues and applicable workarounds, and
- Available environment support
This document provides general information only. ASX Limited (ABN 98 008 624 691) and its related bodies corporate (“ASX”) makes no representation or warranty with respect to the accuracy, reliability or completeness of the information. To the extent permitted by law, ASX and its employees, officers and contractors shall not be liable for any loss or damage arising in any way (including by way of negligence) from or in connection with any information provided or omitted or from anyone acting or refraining to act in reliance on this information.
© 2022 ASX Limited ABN 98 008 624 691