Key New Features
Redesign of the Developer Portal.
Connect to on-premises Oracle and SQL Server data sources.
New supported endpoints: Microsoft Dynamics 365 for Sales, SFTP, and Zendesk.
Option to track deleted Salesforce records.
Create GitHub projects in SnapLogic Manager.
Introduced the Workday REST Snap to connect to Workday REST APIs. This Snap supports the following new accounts:
The Snowflake and the PostgreSQL Snap Packs support geospatial data types.
This release introduces 21 new Pipeline Patterns.
Dot Releases
Platform
Date of Update | Component | Updates |
---|---|---|
Snaplex build: main-15408 - 4.31 Patch 4 |
|
Snaps
Snap Pack | Date of Update | Snap Pack Version | Updates |
---|---|---|---|
| 431patches19770 | Fixed a memory issue that occurred when the Kafka Producer Snap was used to produce many records in a long-running pipeline. | |
| 431patches19781 | The Oracle-Stored Procedure Snap works as expected and does not fail with the error | |
431patches19581 |
|
API Management
New Features
Redesigned APIM Developer Portal. The new design offers the same color scheme and element style as the SnapLogic Studio UI, creating a consistent user experience.
The following list summarizes the key changes:When you log in, you find a redesigned home page that displays your Applications and featured APIs.
Both Applications and APIs have dedicated pages, and the left navigation shows new icons for navigating between the pages:
APIs and Applications are displayed as cards only. The List View option is removed.
You can now use Category filters when searching for APIs and Applications.
The Application and API card style is redesigned.
The Copy to clipboard and Edit icons on the Application card are redesigned.
The following images show the Developer Portal home page before and after the January release:
Enhancements
Support for APIM expressions in the Proxy URL enables you to use variables:
The Generic OAuth2 API Policy also supports OAuth 1.0.
AutoSync
New Features
Using a self-managed Snaplex, connect to on-premises data sources for Microsoft SQL Server and Oracle. An Org admin must add execute permissions for the fastdataloader@snaplogic.com user in the Project space of the self-managed Snaplex.
Integration sources:
Microsoft Dynamics 365 for Sales: AutoSync can load and reload or insert new records and update changes (upsert). When using upsert, only select tables with primary keys for synchronization.
SFTP: AutoSync supports load and reload of CSV and JSON files.
Zendesk CRM: AutoSync supports the following synchronization types:
For Redshift and Snowflake, load and reload, insert new and changed records (upsert), or synchronize and track history with SCD2.
For SAP-DWC, load and reload or insert new and changed records (upsert).
For Google BigQuery and Databricks, load and reload.
For Salesforce: AutoSync can track deleted records by adding an IsDeleted column to the destination. On the first load, AutoSync adds previously deleted records to the destination with a value of True in the IsDeleted column. On synchronization, AutoSync inserts True in the IsDeleted column for records deleted since the last load or synchronization. To enable this behavior, select the Include deleted records checkbox when creating or editing an integration.
Behavior Changes
Amazon S3: Before the January release, when loading from an Amazon S3 bucket, AutoSync used the exact file name for the table it created in the destination, such as
accounts.csv
orcustomers.json
. Some destinations do not support table names that include periods. Now, AutoSync replaces the period with an underscore. For example, to upload a file namedaccounts.csv
, AutoSync creates a table namedaccounts_csv
.Coupa: Before the January release, AutoSync required an API key to create a new connection configuration. Now, a new Coupa connection configuration uses OAuth 2.0 for authentication.
Limitations
The AutoSync dashboard includes integrations created by you. It can display up to 100 integrations.
Cloud data warehouses do not support objects. For all sources that store data as objects, AutoSync converts objects to strings using the JSON
stringify()
method. Thestringify()
method escapes special characters.Microsoft Dynamics 365 for Sales: To use Insert new and update changed for synchronization, you should only choose tables with primary keys.
SAP columns have a limit of 5,000 characters. AutoSync truncates source strings that are over the limit to 5,000 characters when loading them to SAP.
SAP counts each escape character,
\
, as two characters and adds them to the character limit. The example string shown below has 16 escape characters, which SAP counts as 32 characters in addition to the string itself. For long strings, these additional characters might push a string over the 5,000-character limit.
Example string with escape characters:"events": "[{\"id\":12272218027803,\"type\":\"Comment\",\"author_id\":1267681935310,\"body\":\"Hello Sunshine,\\n\\nPlease find the summary below of actions taken\"}]"
SFTP: Data loaded from SFTP converts to strings in the destination.
If you do not have a Zendesk Suite Enterprise account, an error occurs if you try to synchronize the
audit_log
object.If you do not enable the voice feature, you cannot synchronize the following objects:
line
greeting
greeting_category
ivr
call
call_leg
The upsert and SCD2 synchronization types cannot track changes for the
line
,greeting
,greeting_category
,address
, andivr
objects because Zendesk does not provide time stamps for them.
Data Automation
Known Issues
If you define a HAVING predicate in the HAVING Predicate List field set of the ELT Aggregate Snap (to apply on the Snap’s output data), the Snap connected downstream of this ELT Aggregate Snap returns an error corresponding to this predicate during the Pipeline execution.
Platform
New Features
Create new GitHub projects when creating Projects in SnapLogic Manager:
Enhancements
With Git integration, the following more detailed statuses for tracked assets are available:
Tracked, Modified Locally
Tracked, Modified Remotely
Tracked, Conflict
Known Issues
The Memory panel in Snaplex Dashboard displays less value than previous releases because the chart shows max JVM heap memory instead of hardware memory.
In Orgs using the Git integration, the Pattern Project option is available for Git Checkout in the Manager > Create Project dialog; however, this creates a standard Project, not a Pattern Project.
During the Snaplex cooldown state, the FeedMaster for an Ultra Pipeline Task continues to accept and dispatch incoming requests. The Snaplex never actually enters maintenance mode as long as the incoming requests continue.
Upcoming
Coming soon in the February 2023 release: Ultra enhancement
The upcoming Ultra enhancement will significantly speed up the creation, restart, and disabling of Ultra Tasks by reducing scheduling times. Ultra Task will be decentralized by moving it out of the Control Plane and into the production Snaplexes. Extensive internal and private beta testing for a few months has shown startup times reduced from several minutes down to several seconds.
This change will be automatically applied with no action required from customers and will have little to no impact on the resource use of Snaplex nodes.
Snaps
The Snaps mentioned in this section are deployed on the Latest distribution type. To access the updated Snap Packs, your Org admin will need to select the mentioned Snap Pack version in Manager > Snap Packs.
New Snaps
Introduced the Workday REST Snap to connect to Workday REST APIs. This Snap supports the following new accounts (431patches19450):
Enhancements
The Azure SQL Active Directory and the Azure SQL Active Directory Dynamic accounts now include an Authentication Mode dropdown list, which allows you to choose the Active Directory authentication mode you would like to use. This enhancement adds support for Active Directory Service Principal authentication for the Snap Pack. (431patches19493)
The Azure Synapse SQL Insert, MySQL Insert, SQL Server Insert, and Vertica Insert Snaps no longer include the Preserve case-sensitivity checkbox because these databases are case-insensitive. The databases store the data regardless of whether the columns in the target table and the input data are in sentence-case, lowercase, or uppercase. (431patches19263)
The Encrypt Field Snap supports decryption of encrypted output in Snowflake Snaps. (431patches19441)
The DynamoDB Snap Pack supports the IAM role in the DynamoDB account. (431patches19383)
The Google BigQuery Bulk Load (Streaming) Snap works as expected, with no active Timer threads remaining when the Pipeline execution fails. (431patches19301)
The JWT Generate Snap includes the following new fields: (431patches19481)
Issued At Epoch, Not Before Epoch, and Expiration Epoch enable you to specify the custom instants in milliseconds for generating JSON Web Token (JWT).
Skip Key ID for removing the Key ID parameter from the JWT when selected. Some APIs (such as Bloomberg) do not accept Key IDs; this option is useful for these APIs.
The Oracle-Stored Procedure Snap supports stored functions with OUT and INOUT parameters and displays these parameter values in the output with the
returnval
key. (431patches19275)The Snowflake and the PostgreSQL Snap Packs support geospatial data types. As the Snowflake Snap Pack requires using our custom Snowflake JDBC driver for full support of all data types, contact support@snaplogic.com for details. (431patches19454)
The Snowflake S3 OAuth2 Account supports expressions for external staging fields. (431patches19220)
Fixed Issues
Fixed the Azure SQL - Execute Snap using the Azure SQL Active Directory Account that failed with
SQL operation failed
errors in environments using federated authentication. (431patches19493, Latest and Stable)The Azure Synapse SQL - Bulk Load Snap no longer fails when loading the JDBC driver from SLDB as it now uses the uploaded JAR driver when performing all bulk load operations. (431patches19493)
Known Issues
The create table operation in the Snowflake Bulk Load Snap fails if it contains a geospatial data type column.
Work-around: Create the table manually ahead of time or use the Snowflake - Execute Snap to create the table.In PostgreSQL - Insert and PostgreSQL - Bulk Load Snaps, if database metadata from an upstream Snap contains geography column data such as modifiers, those modifiers may not be written to the target table.
Work-around: Create the table using the PostgreSQL - Execute Snap.
Studio
New Pipeline Patterns
The following Patterns are added to Studio:
Asynchronous Parent and Child Pipelines to Transfer Data
Check Host and Port Connection
Export Pipelines into a Zip File
Extract Employee Contact Information from Workday
Generate Apache Avro Schema and DDL based on Oracle Table Metadata
Get Fiscal Periods for Input Date from File
Get the list of Service Accounts in a SnapLogic Org
Load Analytics Data from Purple to Amazon Redshift
Migrate from a Groundplex to a Cloudplex
Monitor the Performance of Integrations
Quote to Cash from Salesforce to Workday or SAP
Radiant Systems Point of Sale to Microsoft Azure SQL Server
Relational-like Data Pivot
Salesforce Cases Microservice API
Salesforce to John Galt Atlas
Salesforce to Multiple Endpoints
Synchronize Account Events from Salesforce to Microsoft Azure SQL Database
Transfer Data from SAP to ServiceNow
Transfer the Attachment from Amazon S3 to Salesforce
Workday Extract Employee 401K Contributions
Workday Extract Employee Manager Hierarchy