Bug ID | Description | Resolution |
|---|---|---|
DCNG-30792 | Fixed an issue where consecutive Oracle database connections using the ODBC 3.x connector failed with an ORA-01005 “null password given” error after the first successful connection. The issue was reproducible in looping ODBC 3.x map executions, while ODBC 3.5, Oracle 21c connectors, and SQL Session connections were unaffected. | Fixed |
DCNG-30786 | Fixed an issue in versions 12.4 and 12.5 where maps processing XML data into DJMessage objects only output a single detail record instead of all expected records. | Fixed |
DCNG-30761 | CVE Security Scan Vulnerability List from ConnectYourCare (Studio Based) | Fixed |
DCNG-30760 | CVE Security Scan Vulnerability List from ConnectYourCare (Engine Based) | Fixed |
DCNG-30704 | An issue in v12.4 on AIX where HIPAA maps incorrectly reported schema mismatches as missing field errors. | Fixed |
DCNG-30434 | An issue in v12.4 where Doc Validator incorrectly processed EDI files with composite elements, causing blank trailing fields to be populated with previous values. This led to validation errors such as “Value not required,” “Maxlen exceeded,” and “Invalid numeric format,”. | Fixed |
DCNG-30404 | An issue in v12.4.0-63 where Unicode (Fixed) and ASCII (Fixed) data sources did not correctly handle short last fields in a record. | Fixed |
DCNG-29791 | An issue on AIX where running a map (CorrOP.map.xml) produced “Invalid XML character (Unicode 0x13)” errors. | Fixed |
DCNG-29532 | An issue in v12 where ODBC 3.5 connectors could not handle certain special characters (e.g., -, ') in field names within XML-style maps. | Fixed |
DCNG-29529 | An issue where DataConnect failed when opening certain workspaces in 12.4.0-67, showing an error referencing the .metadata\.log file. | Fixed |
DCNG-29506 | An issue where processes failed during transformation when using maps with names ending in a “+” symbol. | Fixed |
DCNG-29503 | An issue where XML processes containing FTP Queue 2.0.0 or 3.0.0 components failed to load in 12.4.0-67, showing errorCode 28004 and an unusable blank Step Builder UI. | Fixed |
DCNG-29484 | An issue where the command-line -D option did not correctly set macro values when running .XML maps. | Fixed |
DCNG-29459 | An issue where FileReadLine could not locate files containing a plus sign (+) in the filename or extension, resulting in incorrect file parsing and file-not-found errors. | Fixed |
DCNG-29453 | A data corruption issue in v12.4.0-63 where random invalid characters could be introduced during XLS-to-CSV conversion. | Fixed |
DCNG-29452 | Saving v9-style XML maps in v12 incorrectly overwrote target filter expressions with the last target field expression. | Fixed |
DCNG-29451 | Passwords configured in the FTP component were not always retained after saving a process. | Fixed |
DCNG-29444 | Enabling StripLeadingBlanks or StripTrailingBlanks in the ASCII (Delimited) source connector caused fields containing leading or trailing spaces to be read as blank. | Fixed |
DCNG-29427 | Some v9-style XML maps with long field names failed in v12.4, causing field index errors during map execution. | Fixed |
DCNG-29408 | An engine issue occurred when running a multimode map followed by a single-mode map against the same ODBC DSN. The issue was reproducible with large datasets and impacted customer migration to v12. | Fixed |
DCNG-29308 | When unload=false, RTC/Task Macro changes are ignored during submit, as macros are loaded into the engine but not updated on task submission. | Fixed |