Add Change Data Capture beta to 11.12 release notes

content/en/docs/releasenotes/studio-pro/11/11.12.md

@@ -27,6 +27,12 @@ In 11.12.0 we are introducing module package identification. Each module now has
 For existing apps, Studio Pro automatically assigns a **Module ID** to every module when the app is opened. The ID is derived either from the Marketplace component ID, or from the **App ID** and module name. Studio Pro also generates a **SHA-256 Checksum** for every exported module package which will later be used for determining module integrity. 
 The **Module ID** and **checksum** are stored in a new *manifest.json* file inside the module package, alongside the existing *package.xml* for backward compatibility. For more information, see [Module Settings](/refguide/module-settings/#package).
 
+#### Change Data Capture (Beta)
+
+In Studio Pro 11.12.0, we introduced Change Data Capture (CDC) as a beta feature. With CDC, you can publish changes from Mendix domain model entities as Kafka events by adding the entities to a Change Data Capture Service document. Each added entity will have its own Kafka topic. When the objects are created, updated, or deleted, the runtime captures these committed changes and publishes them to the specified Kafka topic.
+
+CDC can be used with the Mendix Event Broker or with a Bring Your Own Kafka (BYOK) cluster. You can also use Event Broker Bridges to route CDC events to external destinations such as data warehouses, data lakes, or blob storage.
+
 #### Other New Features
 
 - We introduced an option to purchase Maia Units. This resource allows you add additional capacity for your company to use Maia Make. For more information, see [Maia Resources](/control-center/maia-resources/).