...
We plan to upgrade the Oracle Snap Pack to the latest JDBC JAR file 19c (19.18.0.0) in the July release.
Pipelines that use the default JDBC driver in the Oracle server accounts might be affected after the driver upgrade because the latest driver is backward-incompatible. We will soon communicate how to reconfigure to prevent accounts from being impacted.
Pipelines that do not use the default driver (bundled with the Oracle Snap Pack) are not impacted.
Enhancements
The Dynamics 365 for Sales Snaps include a new Enable continue on error checkbox to allow the Snap to continue executing the remaining batch requests, even if the previous request does not execute. (433patches21467)
The Dynamics365 for Sales Update Snap performs the update operation as expected when the Batch size is more than 1, and the Snap successfully executes when the batch size is 1. (433patches21467)
The pagination feature implemented for the ABFS protocol in the Hadoop Directory Browser Snap enables the Snap to return all the output documents as expected. (433patches21494)
The PGP Encrypt Snap now includes an Encryption key ID field, which allows you to specify the key ID for encrypting the data. If you do not specify an encryption key ID, the Snap uses the first key in the public key (master key). (433patches21482)
The following Transform Snaps include new fields to improve memory management: Aggregate, Group By Fields, Group By N, Join, Sort, Unique. (433patches21461)
The SQL Server Snap Pack is upgraded to the Microsoft JDBC Driver
12.2.0.jre11for SQL Server. Existing pipelines that do not use the default driver (bundled with the SQL Server Snap Pack) are not impacted. If you want to use NTLM or other authentications with the latest default driver (where the DLL file is mandatory), then you must copy the DLL file to the Snaplex path. (433patches21386)
...