Release notes – LDP – data-4.6.17
Release date: 2025-09-23
Bug fixes
DATA-35660
Fixed comm-log operations leading to DB-constraint errors when AS2-reception and processing happen on different systems.
DATA-43427
Fixed the X12-parser regarding X12-messages containing a TA1 segment as invalid.
DATA-43449
Profiles: Unlock closed system doesn't release profiles.
DATA-43469
HTTP nested exceptions by adding base64 placeholder.
DATA-43491
JMS: Fixed Phase 1 client id.
DATA-43510
Phase3: Fixed import and export business logic errors with lists and maps in paths.
DATA-43514
OAuth2: Fixed JSON body content.
DATA-43517
HTTP Channel: Generic Bearer Token error when response body is empty but token could be received via Header.
DATA-43518
Phase6: Added Password obfuscation for XML exports.
DATA-43526
EngDAT: Removed "new" button in in/outbound views.
DATA-43527
Profile settings: Obfuscate excel and zip passwords of exported profile.
DATA-43529
ControlCenter: client refresh fix in profile selection.
DATA-43531
Phase3: Added missing trigonometry functions.
DATA-43532
Certificates: TLS client auch certs are now considered for usage report
DATA-43534
Phase3: Functions: Fixed result numbering when using drag&drop into source field parameter.
LDP-3689
Fixed Metric REST API endpoint returns wrong result occasionally when using parameters json=true or openMetrics=true.
LDP-3770
Fixed issue in profiles leading to empty files not being processed despite being configured to do so.
LDP-3849
DataCockpit: Fixed illegal Dates caused by minutes as month.
LDP-3953
Fixed TRADACOM parser ignoring characters in value after "=".
LDP-3966
Constants view: Fixed constants not updating properly in NC.
LOB-235
Fixed issue leading to stale temporary directories on the DMZ after pickup if Pickup-via-DMZ is used as response in a profile.
LOB-244
Fixed a NullPointerException that occurs when handling mails that are missing essential parts in their headers.
LOB-263
MQTT: Deactivated test logging if buffering with functions is used.
Improvements
DATA-43541
Kafka: Client ID can now be resolved from constants and variables (phase 6 only).