...

• New endpoints, Google BigQuery, Amazon S3 (for CSV and JSON files), Marketo, and CSV files

• Synchronize with SCD2 between Salesforce and Snowflake

• For a Salesforce source, AutoSync automatically handles changes to the column precision, scale, or character limit by propagating the changes to the target.

Platform

• The new Pipeline Cache feature (private beta) enables you to leverage in-memory lookup

• New APIM Public APIs allow you to publish, unpublish, deprecate, or retire a set of API versions

• Support for CyberArk Conjur in Secrets Manager

...

Fixed Issues

Fixed an issue where calling an API Proxy called from the Developer Portal did would not initiate execute the request on the specified Groundplex selected to run it.

AutoSync

New Features

• AutoSync now supports the following endpoints:

  • Google BigQuery as a target. Learn more.

  • Marketo as a source. Learn more.

  • CSV or JSON files stored in Amazon S3 as a source. Learn more.

  • Upload CSV files from a local or network drive as a source. Learn more.

• The ability to change load type for synchronization. The types available depend on what AutoSync supports for the source and endpoint. AutoSync supports loading from Salesforce to Snowflake using SCD2. To change the load type:
  After creating a data pipeline, edit it. From the Auto Synchronize tab, select the Load type. Learn more.
  

  

• For a Salesforce source, AutoSync automatically handles changes to the column precision, scale, or character limit by propagating the changes to the target. Learn more.

...

• When creating a new project from a Git repository, you can also create a new branch for the new project. Learn more.

• Support for HashiCorp KV Secrets Engine Version 1 is available, in addition to KV Search Engine Version 2.

Known Issues

• The Bearer tokens for Tasks not being stored in their associated Git repositories.Token value for the Triggered Task changes when migratws from one Org to another.
  This will lead to issue as wherever triggered task URL is configured customer will need to manually change the bearer token.Project Space: SnapLogic Admins

• The subscription feature Secrets Management -CyberArk is displayed with the indicator (Coming soon…) when in fact, the feature is already available.

...

• The Bouncy Castle library version is upgraded from bcpg-jdk150n[1.69] to bcpg-jdk180n[1.73] in all our Snap Packs. This upgrade brings in the latest security features to enhance the performance of the SnapLogic platform.

• The Generic Database Account now supports the SSH Tunneling connection. You can now encrypt the network connection between your client and the database server, ensuring a highly secure connection.

• The Hive Snap Pack is Cloudera-certified for Cloudera Data Warehouse (CDW). You can use the Hive Execute Snap to work with CDW clusters through a Generic Hive Database account.

• The Marketo Bulk Extract Snap works successfully in the non-lineage path in an Ultra task.

• The Key passphrase field in the Private Key Account now supports expressions, allowing dynamic evaluation using pipeline parameters when the expression button is enabled.

• Snowflake

  • Snaplogic is specified as a partner tag in all requests directing to Snowflake, making it easier for Snowflake to identify the requests coming from Snaplogic.

  • The default JDBC JAR for the Snowflake Snap Pack is upgraded to version 3.13.28 to support the GEOMETRY data type.

Known Issues

• A SnapLogic Account configured with a JKS truststore fails on a Groundplex that has the JVM option -Dsnaplogic.security.provider=BC. To fix any errors, try removing this option. Learn more about Configuring Bouncy Castle as the first Security Provider in your Snaplex

  • .

Fixed Issues

• Fixed an issue with the Encrypt Field Snap, where the Snap failed to support an RSA public key to encrypt a message or field. Now the Snap supports the RSA public key to encrypt the message.

...