July 2025
The Continuous Compliance 2025.4.0.0 release adds support for CData Salesforce driver 24.0.9280, document store-type masking for JSON paths, and AI-powered search for product information. It also migrates database masking processing to Apache HOP and addresses several bug fixes, including issues with file formats, PDF parsing, and DB2 Iseries masking.
New features
Support for CData Salesforce driver 24.0.9280
The Salesforce driver version 24.0.9280 introduces support for Bulk API v2, enabling improved performance and support for larger data loads. This version also includes query optimizations that enhance overall data processing efficiency. Key benefits include parallel result downloads for query jobs, optimization for large payloads within Salesforce limits, and backward compatibility with Bulk API v1. For more information, see Salesforce JDBC Compliance documentation.
Support for Document Store-Type assignments for JSON paths in JSON file masking
This release supports document store-type masking assignments for JSON paths, allowing masking of embedded JSON data within JSON string fields. For more information, see Document Store-Type Masking topic.
Migration of database masking job processing to Apache HOP library
This release migrates the database tables masking job processing from Pentaho Kettle to Apache HOP library.
AI-powered search for product information
Locate information more efficiently with our new search experience. On the main Continuous Compliance documentation site, you can now enter questions and get AI-generated answers. You can also filter your search by product. Answers combine content from our current product documentation and the Perforce knowledge base.
Fixed issues
Release 2025.4.0.0
| Bug number | Description |
|---|---|
| DLPX-70803 | Fixed an issue where masking failed for fixed-width files when the defined file format contained more fields than present in the source data file. |
| DLPX-90987 | Fixed an issue where parsing the date from report PDF filenames failed during purge operations, causing an error c.d.t.s.PurgeReportingPdfFiles . |
| DLPX-92521 | Fixed an issue where profiling or masking failed on files with very long names. |
| DLPX-93765 | Fixed an issue where upgrading a masking engine will no longer update the sync state of built in algorithms |
| DLPX-94312 | Fixed an issue for DB2 Iseries where masking job was failing because some column names were reserved keywords in DB2. |
Release 2025.4.0.1
Fixes that take effect after upgrading and rebooting
| Bug number | Description |
|---|---|
| DLPX-94872 | Fixed an upgrade issue on CC engines where the masking service fails to start. |
| DLPX-94873 | Fixed an ability for Delphix Support to access the closed appliance via ssh session. |
Known issues
|
Key |
Summary |
Workaround |
|---|---|---|
| DLPX-80640 | masking drop Indexes task does not find and remove indexes on SQL Server partitioned tables in both on-the-fly and in-place masking jobs. | Manually script the drop and recreate indexes. |
| DLPX-81694 | When masking two columns with the same name but different casing, the same algorithm may be incorrectly applied to both. | None |
| DLPX-93701 | On the fly masking job fails when using different source and target connector types (mixed Cloud and On-premise connectors) for JSON, XML, and Parquet files. | None |
| DLPX-94308 | Masking jobs that exceed a runtime of 6 days are automatically marked as FAILED, even if the job is still actively processing. | None |
| DLPX-94655 | Missing '/var/delphix/sfdc/dxrt' directory after upgrade | Contact Delphix Support for workaround |
| DLPX-96175 | Inconsistent values in parquet masked file for null-heavy, dictionary encoded columns. | None |
Deprecated and end-of-life features
End-of-life features
Generic connectors
Generic connectors, deprecated in release 24.0.0.0, are officially end-of-life (EOL) as of 2025.4.0.0. Creation, modification, and execution of jobs using these connectors are disabled. When upgrading to this release, you must recreate any generic connectors using a natively supported or extended connector, replicate the associated rulesets, and update jobs to use the new configuration. Once verified, delete the deprecated connectors. For more information, see Migrating from legacy generic connectors and Delphix Community Post.