February 2021, 4.24 Release Notes

In this article

Key New Features in SnapLogic

Platform:

  • Universal Search includes new Pipeline search 

  • Snaplex-based Scheduler

  • Notifications via Slack 

API Management:

  • API Dashboard UX improvements 

eXtreme:

  • Cross account IAM support

ELT for Cloud Data Platforms:

  • Support for Azure Synapse

  • Ease-of-use improvements

New Snap Packs:

  • HubSpot, MS Power BI, Marketo, OpenAPI, MS Teams

Updated Snap Packs:

  • Enhancements to the Confluent Kafka Snap Pack
  • Redshift and Amazon SQS support for cross domain IAM roles


Important

  • Per the SnapLogic Release Process, all remaining Snaplex instances across Orgs are auto-upgraded to the recommended version at 9 p.m. PT on March 20, 2021. Orgs migrated to the 4.24 GA version prior to the auto-upgrade are not impacted. 
  • To use the new SnapLogic features and Snaps in the 4.24 release, ensure that your Snaplex nodes are upgraded to the recommended version.
  • This 4.24 release includes the patches deployed to SnapLogic after the 4.23 release, as listed in the 4.24 Dot Releases section. 


4.24 UAT Delta

This section tracks the changes made during the iterative pushes to the UAT server and the GA release. The following is the release schedule:

  • UAT: Friday, February 05, 2021 – Use Snaplex Version: 4.24_rc2-9059 - 4.24 GA 

  • GA: Saturday, February 13, 2021 (9 p.m. PT) - main-9488 - Patch 3 

The SnapLogic GA release build on the production server is also deployed on the UAT server.

UAT Fixes

Snaps

  • Fixes an issue in the JDBC Snaps to output the data time values in the same format as the 4.23 release (November, 2020) to support backward compatibility in the output view.


4.24 Dot Releases

Platform

Date of UpdateSnaplex BuildUpdates
 main-9488 - Patch 3 (Recommended)
  • Fixes issues with the Snaplex-based Scheduler:

    • The expressions task.start and task.end are not initializing correctly.

    • The Task Details page displays null details and/or duplicate/unscheduled executions for some tasks. 
  • Fixes an issue where the error and JCC logs do not rotate as expected if they exceed the configured log file limit of more than 50MB (default value).

  • Fixes an issue with a node in maintenance mode, which shuts down every five minutes due to an unresponsive JCC.

 N/A

Control Plane update:

  • Fixes an issue with the Snaplex Management API that moves all nodes in maintenance mode instead of a single node. 

  • Fixes an issue where some Ultra Tasks periodically restart after upgrading to the Platform Patch 1. 
main-9292 - Patch 2
  • Fixes an issue with the Snaplex-based Scheduler where Scheduled Task execution is not stopping when execution frequency is changed from one minute to one week.
  • Fixes an issue where in some cases a re-enabled Task records multiple missed execution in the logs.
  • Fixes an issue where Salesforce Update Snap errors do not route to the error Pipeline despite being configured to do so.
  • Fixes an issue with the Script Snap where active threads persist even after the Pipeline completes execution.
  • Enhances SnapLogic Platform security by not including encrypted user credentials for Snowflake Snap accounts in the logs. 
  • Changes the logging behavior of Snaps to log only the FQID information.
 
main-9191 - Patch 1
  • Fixes an issue wherein invalid tasks from deleted Pipelines cause other valid scheduled tasks from executing.
  • Fixes an issue with the Snaplex scheduler that is triggering duplicate task executions.
  • Fixes an issue with Ultra Tasks that fail beyond planned Control Plane downtime.
  • Reduces Ultra Tasks latency in some cases when executing the task after a period of inactivity.

We currently recommend you to use main-9488 - Patch 3 as your Snaplex version.

UI

Date of UpdateUpdate
 
  • Fixes an issue where after resetting the password, a user with disabled UI access, is not redirected to the log-in page. 
  • Fixes an issue on the SnapLogic log in page where the right and left arrow to toggle product messages is not visible on a white image.
  • Fixes an issue with the Task dialog where some of the new time zone labels are incorrect after the 4.24 release.

  • Fixes an issue with the Compare Pipeline feature where the source Pipeline and target Pipeline now correctly display as Deleted and Added, respectively. 
  • Fixes an issue with resetting the SnapLogic log-in password, wherein an error message and a redirecting message display simultaneously, instead of displaying only the error message. 
  • Fixes an issue with the "error_id": 1015 message for accessing the SnapLogic Designer now displays the right error message. 
  • Adds a tooltip describing the password input rules for the SnapLogic log-in page.

Known issues:

  • In the SnapLogic log-in page, a right arrow displays in the image displaying the password rule tooltip.
  • When logging in using the single sign-on option, no error displays when an incorrect Organization name is entered in the field.
 

Fixes an issue with Orgs using enhanced encryption that run into an error decrypting sensitive information with non-ASCII characters when connecting with end-point accounts. 

Standard-mode Snaps

SOAP Snap Pack uses the 4.23 GA version (main7430)

Due to an upgrade to the CXF library, SOAP Execute Snap that uses the CXF client targeting SOAP 1.2 endpoints can fail. We also observe increased thread counts related to this upgrade. Hence, during the 4.24 auto-upgrade on , we did not update the SOAP Snap Pack and are moving the stable version for all your Orgs to main7430 (4.23 GA) instead of main8556 (4.24 GA). This should not impact your existing Pipelines. 

You can also use SOAP Snap Pack version 423patches7441 that was deployed as 4.23 dot release on , if needed.  

Snap PackDate of UpdateSnap Pack Build NameUpdates
Binary 424patches9044Enhanced the S3 File Writer to use an MD5 checksum that automatically checks for data integrity and corruption while uploading the file.  
Box 424patches9242
  • Enhanced the Box Snap Pack with the Retry mechanism that includes the following settings:

    • Number of retries: Specifies the number of attempts the snap should make to perform the selected operation in case of connection failure or timeout.
    • Retry interval (seconds)Specifies the minimum number of seconds the Snap must wait before each retry attempt.
Hadoop 424patches9262

Enhanced the AWS S3 Account for Hadoop to provide role-based access when you select the IAM role check box.

Anaplan 424patches9313Fixes an issue related to Index out of range in the Anaplan Upload Snap when the separator is not present or does not match the one in the upload file. 
Binary 424patches9020

Fixes the file operation error of copying large S3 files in the File Operation Snap by supporting the transfer of zero-byte S3 files while uploading the file.

Snowflake424patches8905

Enhances the Snowflake - Bulk Load Snap to allow transforming data using a new field Select Query before loading data into the Snowflake database. This option enables you to query the staged data files by either reordering the columns or loading a subset of table data from a staged file. This Snap supports CSV and JSON file formats for this data transformation.

DynamoDB 424patches9031
  • Supports autoscaling by adding retry logic with exponential backoff to the Snaps.
  • Enhanced the DynamoDB Account to support the Expression Enabler for account properties and creation of dynamic accounts.
  • Improves memory consumption in DynamoDB Bulk Write and Bulk Get Snaps.
SOAP  424patches9077
  • Fixes the incremental thread count issue in the SOAP Execute Snap by ensuring that only instance of SoapCustomAsyncHTTPConduitFactory should pass throughout the execution of the Snap.
  • Fixes an issue in SOAP Execute Snap where the Snap fails as the default value of Content-Type field was modified after upgrading the Snap in the 4.24 release.
JMS 424patches9098Enhances the JMS account in the JMS Snap Pack by updating the JNDI properties (java.naming.security.principal, java.naming.security.credentials) with username and password, to support the requirements of certain JMS servers.
JMS 424patches9104Fixes an issue in the JMS Consumer Snap, where different JMS SQS accounts interfere with each other when running on the same JCC node by using the AWSStaticCredentialProvider instead of the SystemPropertiesCredentialsProvider.
Salesforce  424patches9024
Microsoft Power BImain80

Enhances the following Snaps in the Microsoft Power BI Snap Pack by adding two values, Dataflow and Dataflow Storage Accounts to the Entity Type field.

Twilio main80Introduces the Twilio Snap Pack that enables you to perform various communication functions programmatically, such as making phone calls and sending text messages using Twilio's Web Service APIs. This Snap Pack offers the following Snaps:
SQL Server 424patches8657

Enhances the SQL Server - Select Snap by introducing a new field, Query Hints, which helps to customize and optimize the database engine to process query statements.

Exchange Online 

 

424patches8965

Fixes an issue in the Snap Pack by handling the conflict of users having same email IDs by accepting only the first user’s email ID returned by the API and ignoring the duplicate ones.

Twitter 424patches8617Fixes an error handling issue in the PostTweet Snap, where data and error are now routed to the error view.
Transform424patches8938
  • Fixes the timestamp issue in JSON Formatter Snap that changed the time zone offset to include colon by default after upgrading to 4.24.
  • Fixes the null pointer exception at runtime in Fixed Width Parser Snap by setting the Trim column data field to false for empty columns.
  • Enhances the Group By N Snap to process the records efficiently by adding a Flush Timeout field that enables the Snap to flush a partial group of records if the time specified in this field passes with no new input.
NetSuite424patches8891

Introduces the new Snap NetSuite Call RESTlet that enables you to call RESTlet scripts through token-based authentication. This Snap provides the functionality of the NetSuite RESTlet framework that supports the HTTP methods (GET, DELETE, POST, PUT) and MIME types.

RabbitMQ424patches8750

Fixes the handling of RabbitMQ Headers in the RabbitMQ Consumer Snap, including the x-death header.

JDBC424patches8903Fixes the Pipeline execution failure issue when using the JDBC Snaps with a Microsoft Access account by setting the correct quotation handler for the configured account.
Binary

Hadoop

Hive


424patches8876
  • Fixes the missing library error in Binary, Hadoop, and Hive Snap Packs when running Hadoop Pipelines in JDK11 runtime.
  • Enhances the Binary Snap Pack by adding a new account - Two-Factor Auth Account that supports two levels of authentication (2FA) for SFTP protocol to access SFTP.
Salesforce 424patches8569

Fixes an issue in Salesforce Bulk Upsert, Salesforce Bulk Update, and Salesforce Bulk Create Snaps that fail to process Related object and Related external ID values by modifying the input schema that formats the CSV data.

Potential Breaking Change (now fixed in 424patches9024)

This Salesforce Snap patch contains an issue affecting the Salesforce Subscriber and Salesforce Publisher Snaps. If you do not use these Snaps in your Pipelines, then you can use this patch version. Else, we recommend you to not use this patch version as Pipelines will fail. 

Confluent Kafka 424patches8805Fixes an issue with the Kafka Producer Snap by removing the account validation, which is not required, when the Snap initializes in a Pipeline execution.
Teradata 424patches8799
  • Enhances the Teradata Execute Snap by adding a field, Advanced options, which extends support with microsecond precision for TIMESTAMP data type.
  • Fixes an issue in the TPT Load Snap where the Snap fails to load data into the table when creating an output.
  • Fixes an issue with the TPT Load Snap where both null and empty string values loaded as null, such that a null value loads as null and an empty string loads as empty string, respectively.

    • This fix may cause existing Pipelines to fail if empty string values are expected to be loaded as null.

    • Following are the new configurations:

      • VARCHAR QuotedData= Optional

      • VARCHAR OpenQuoteMark= \”

      • VARCHAR NullColumns= Yes

Google Directory 
 
424patches8638

Enhances the Google Directory Read Snap by introducing two field attributes, projection and customFieldMask, to retrieve custom schema fields.

Data Automation

Snap PackDate of UpdateSnap Pack Build NameUpdates
ELT
 
424patches8793
  • Fixes the column name collision issue in the Snap's output when two tables being joined have columns with the same/identical names. You can specify the extent of prefix (that is, to prefix all columns, only duplicate columns, or no prefix) using the Resultant Column Names Prefix Type drop-down list. Based on the prefix you choose, a table alias name is prefixed to the identical columns in the output.
  • Fixes the issue of production job failures due to ELT Insert Select Snap after upgrading to 4.24 GA by updating the ELT Transform Snap to continue allowing duplication of fields in the expression list for the Pipeline to complete successfully.

No changes are needed to your existing Pipelines.


Behavior Change

The behavior of ELT Load Snap for Load Action during Pipeline validation across the supported databases is as follows:

  • Append rows to existing table: Does not append the data from the source files into the target table.
  • Overwrite existing table: Does not overwrite the data in the target table.
  • Drop and Create table: Does not drop the target table even if it exists, but the Snap creates a new target table if a table does not exist.
  • Alter table: Does not modify the schema of the target table.
Spark SQL 2.x 
 
424patches8724

Fixes an issue with eXtremeplex that is unable to read Parquet files written from a Groundplex (and hence displays base64 enabled in output columns upon validation), by changing the data encoding from Base64-encoded to plain text format. This issue does not occur during Pipeline execution.


Important

  • Per the SnapLogic Release Process, all remaining Snaplex instances across Orgs are auto-upgraded to the recommended Snaplex version main-9105 - 4.24 GA at 9 p.m. PT on March 20, 2021. Orgs migrated to any of the other 4.24 versions prior to the auto-upgrade are not impacted. 
  • To use the new SnapLogic features and Snaps in the 4.24 release, ensure that your Snaplex nodes are upgraded to the recommended version.
  • This 4.24 release includes the patches deployed to SnapLogic after the 4.23 release, as listed in the 4.23 Dot Releases page. 


Groundplex Support for Java 11 and Sunsetting Java 8

  • Groundplex––Per the 4.22 release announcement, we are only supporting Java 11 and have ceased support for Java 8. Your nodes on Java 8 will not work. Hence, ensure that you upgrade to Java 11.0.8+ version for all your Groundplex instances. If your infrastructure is still using Java 8, you will see class file version errors when running your Groundplex. 

Platform 

New Features

  • Snaplex-based Scheduler: Introduces a new mechanism for activating your Scheduled Tasks. The Snaplex-based Scheduler improves the timeliness and reliability of Scheduled Task executions. Previously, the scheduler in the SnapLogic Control Plane handled all Scheduled Tasks executions. The Snaplex-based Scheduler shares the scheduling duties with the Control Plane scheduler, making Scheduled Task executions timelier and more reliable.

    Enabling the Snaplex-based Scheduler

    • We encourage you to enable the Snaplex-based Scheduler for all Scheduled Tasks in your Org. To plan for this adoption, see details about Snaplex-based Scheduler
    • We recommend that you use main-9292 - Patch 2 as your Snaplex version to use the scheduler feature.
    • In the 4.25 Release (May 2021), the Snaplex-based Scheduler will be the default mechanism for scheduling all Tasks.
  • Activity Notifications Via Slack: Introduces support for the Slack messaging app within the SnapLogic platform communication system, enabling you as an Org admin to add Slack channels and recipients for your SnapLogic communications. Slack notifications support is in the following areas of the SnapLogic UI:

    • The alerts and notifications in Manager > Settings.


    • The Create Snaplex and Update Snaplex dialogs in Manager > Project Spaces also support adding Slack recipients.


      The integration setup follows an easy workflow, which is also in Manager > Settings, and requires that you grant permission to access the Slack channels and recipients in your workspace.

      After adding Slack, you can send notifications and alerts to Slack recipients through Slack channels or directly to Slack users, making it easier to communicate with team members who are either users or nonusers of the SnapLogic platform. 

  • Pipeline Search: Introduces a new search category in the Universal Search, you can now browse through search results that include high quality Pipelines in your Org. Pipelines deemed as high quality have successfully executed repeatedly. Similar to Configured Snap search, you can narrow the results by Project. You can also open the Pipeline or copy it to another Project.


  • Snaplex Version Manager: Introduces a new page in SnapLogic Manager that lists all the Snaplex instances in an Org and their versions. The selector enables you to choose the Snaplex version for each Snaplex in your Org. For example, you can select all your test Snaplex instances to update to the latest version, while leaving all others as is, and only the selected Snaplex instances are updated.


Enhancements to Existing Features

  • API Dashboard: Improves the user experience with the following updates: 
    • Replaces non-intuitive tabs on All API Details widget with modal window for consistent experience.
    • Expands the All API Details widget and improving navigation to the request log for the target API and back to the All API Details.
    • Adds the ability to download all request details from the API Details widget.



  • Login Page: Refreshes the appearance of the SnapLogic login page. As part of this new branding, you will see a new SnapLogic login page, along with refreshed Password Recovery and SSO Login screens. However, the functionality is the same.


  • Task Details: Enhances the UI display for the Task Details page, with a redesign that features better organized information, including headers, a streamlined look, and for Task runs, a search field and date selector for narrowing target Tasks.

New in 4.24

4.23 and Earlier


  • Additional Time Zones: Adds support for the following time zones in the 4.24 release:

    New DisplayTime Zone
    Europe/LondonGMT/BST
    Europe/ParisCET/CEST
    Asia/Hong KongHKT
    Asia/BangkokICT
    Asia/DubaiGST


  • Task Monitoring Dashboard Wall: Adds a new drop-down list for Invoker Type. You can now sort Tasks by type (Ultra, Scheduled, Triggered). Additionally, access permissions to the Task subtab on the Dashboard are changed in the 4.24 release:

    Access permissions in 4.24 release Access permissions in 4.23 release and earlier
    An Org admin or any user with read access to the Project where the Task resides can view the Task monitoring Dashboard.Only Org admin or user with read and write access to the Task and underlying Pipeline can monitor Tasks.


  • Extra Details: Updates the Extra Details page to display whether a Pipeline is running in Resumable Mode.

  • IP Address Management: Changes Whitelist/Blacklist labels in the UI to Allowlist/Denylist.

  • Child Pipelines: Changes the method for load balancing across Snaplex nodes to achieve improved node election for Pipeline executions.

Known Issues

  • Scheduled Tasks that are migrated to a different Project do not reset their run counters.
  • Scheduled Tasks continue executing, even when the frequency for a task is updated from 1 minute to 1 week.
  • If your Org uses Snaplex Scheduling, disabling and then enabling a Scheduled Task should prevent the Task from executing while disabled, but it does not.
  • Fixed in a UI patch on 3/11: Some of the new time zone labels in the Task dialog need to be updated.
  • When upgrading your Snaplex to the 4.24 GA version, if a node is under maintenance mode, then the node fails to upgrade.

  • In some cases, Ultra Pipeline Tasks duplicate messages that are being processed from the FeedMaster node, resulting in failed Retry errors. If you see this issue in your Org, see Enabling the Prevention of Duplicates Enhancement.

Behavior Change

  • Project Migration API Parameter: You can now only use the dest_path parameter to specify a target Project. You can no longer use this parameter to specify Project Spaces as the destination path in the public API for Project migration.
  • Ultra Pipelines: In 4.23 release (November 2020) and earlier, you could enable and disable Ultra Tasks in Manager despite unsubscribing from the feature. Starting the 4.24 Release, you cannot access Ultra Tasks if the subscription expires.


Standard-mode Snaps

New Snaps

  • HubSpot Snap Pack (dot release deployment during 4.23): Enables you to integrate with your HubSpot instance. This Snap Pack includes the following Snaps:
  • Marketo Snap PackIntroduces the Marketo Snap Pack to enable you to automating the process of performing operations to the Asset database and Lead database that manage the potential data for an organization in the marketing industry. This Snap Pack offers the following Snaps:
    • Asset Read: Queries the Asset database to retrieve assets using commands.
    • Asset WriteInteracts with the assets using commands and make modifications to the Asset database.
    • Lead Read: Queries the Lead database to retrieve leads using commands.
    • Lead WriteInteracts with the leads using commands and make modifications to the Lead database.
    • Bulk Lead ExtractRetrieves leads in bulk from the Lead database.
    • Bulk Lead UpsertInserts/Updates large number of leads in the Lead database.

  • Microsoft Power BI Snap Pack (dot release deployment during 4.23): Enables you to access and control entities such as datasets, reports, gateways, and dashboards in the workspace. The Microsoft Power BI Snap Pack contains the following Snaps:
  • OpenAPI Snap PackIntroduces the OpenAPI Snap Pack to enable you to connect to your OpenAPI endpoints. This Snap Pack contains a single Snap that supports OpenAPI Specification versions 2.0 and 3.0.
    • OpenAPICalls the OpenAPI endpoint associated with your application to perform operations, such as GET or PUT, based on the endpoint's configuration.

  • Teams Snap Pack: Introduces the Microsoft Teams Snap Pack to enable you to perform various operations on channels and teams. This Snap Pack offers the following Snaps:

We strongly recommend you to use the new form UI enabled in Designer > User Settings () for using the complete functionality in new Snap Packs from 4.23 release onwards. 

Updated Snap Packs

  • Active Directory Snap Pack:
    • Adds the Pass through check box in all the Snaps to include pass-through functionality. Select this check box to embed the upstream input documents under the original field of the output document along with other records. Originally deployed as 423patches7454 (Latest), this Snap Pack is now part of 4.24 GA (Stable).

    • Fixes an issue of fetching search records in the Active Directory Search Snap by adding a new field, Limit, wherein you can specify the number of search records to fetch from the Active Directory. Originally deployed as 423patches8210 (Latest), this Snap Pack is now part of 4.24 GA (Stable).

      Behavior Change

      • Previously the Page Size field worked similar to the Limit field, that is, it sets the limit on fetching records instead of fetching all the records. 
      • The Active Directory Search Snap output now displays the number of records that you specify in the Limit field under Settings. If your Pipelines use the Snap with the Page Size field, they may fail to execute if the downstream Snap expects the same count. To retrieve all the records, configure the Snap with default settings, that is, Limit: 0 and Page Size: 1000.
  • Amazon SQS Snap PackEnhances the Snap Pack to support Cross-Account IAM role that allows to access the queues residing in another AWS account.

  • Binary Snap PackEnhances the File Poller Snap by adding a field, Exit on first matches, which when set to true stops the Snap from executing after the first file paths matching the filter are written to the output view. If the field is not configured or is set to false (default value), then the Snap continues to poll the directory until the Polling timeout is reached. Originally deployed as 423patches7660 (Latest), this Snap Pack is now part of 4.24 GA (Stable).

  • Kafka Snap Pack Originally deployed as 423patches7900 (Latest) , this Snap Pack is now part of 4.24 GA (Stable):
    • Removes the Confluent prefix from the Snaps and accounts in the Snap Pack. However, the Snap Pack name continues to be Confluent Kafka Snap Pack.

    • Adds Wait For Full Count check box to the Kafka Consumer Snap to determine how a positive value for the Message Count field must be interpreted.

      • Enabled (by default): The Snap continues polling for messages until the specified count is reached.

      • Disabled: If there are fewer messages currently available than the specified count, then the Snap consumes the available messages and terminates.

    • Adds support for writing and reading record headers:

      • The Kafka Producer Snap has a new Headers table to configure the Key, Value, and Serializer for each header to be written.
      • The Kafka Consumer Snap reads any headers present on the records it consumes. It provides two new fields to configure how the header values should be deserialized – Default Header Deserializer and Header Deserializers, for any headers that require a deserializer other than the default.
    • Adds support for writing and reading each record’s timestamp:

      • The Kafka Producer Snap has a new Timestamp field that can be configured to set each record’s timestamp, which is the number of milliseconds since the epoch (00:00:00 UTC on January 1, 1970). This can be set to an expression that evaluates to a long integer, or a string that can be parsed as a long integer, or a date. If you specify no expression, or the value is empty, then the timestamp is set to the current time.

        The Timestamp field is only relevant if the Kafka topic is configured with message.timestamp.type = CreateTime (which is the default). For more information, see the official Kafka documentation.

    • The Kafka Consumer Snap has a check box, Include Timestamp, which by default is disabled for backward compatibility. If enabled, the output for each record includes its timestamp in the metadata.
    • The Kafka Producer Snap has a check box, Output Records, to determine the format of each output document when configured with an output view:

      • Disabled (by default): The Snap’s output includes only the basic metadata (topic, partition, offset) for each record, along with the original input document.

      • Enabled: Each output document contains a more complete representation of the record produced, including its key, value, headers, and timestamp.

    • The Kafka Consumer Snap has a field, Output Mode, with two options:

      • One output document per record (the default): Every record received from Kafka has a corresponding output document.

      • One output document per batch: Preserves the batching of records as received from Kafka. Every poll that returns a non-empty set of records results in a single output document containing the list of records as batchbatch_size and batch_index. This mode is especially useful when Auto Commit is disabled and Acknowledge Mode is Wait after each batch of records, depending on the nature of the processing between the Kafka Consumer and the Kafka Acknowledge Snaps.

    • Removes the Add 1 to Offsets check box from the Kafka Consumer Snap.

    • Removes the Account tab from the Kafka Acknowledge Snap, as it no longer needs an account.

  • Data Snaps:
  • Google Spreadsheet Snap PackEnhances the Snap Pack by migrating from v3 to v4 API as Google announces sunsetting the v3 API on June 8, 2021. For more information, see Migrating Google Sheets Pipelines from V3 to V4Originally deployed as 423patches7848 (Latest), this Snap Pack is now part of 4.24 GA (Stable).
     
  • LDAP Snap Pack: Adds the Pass through check box in all the Snaps to include pass-through functionality. Select this check box to embed the upstream input documents in the original field of the output document along with other records. Originally deployed as 423patches7454 (Latest), this Snap Pack is now part of 4.24 GA (Stable).

  • MongoDB Snap PackFixes an issue in the MongoDB accounts to connect to Atlas Free Tier and Shared Cluster database using the Use cursor timeout option in the MongoDB cursor properties. If selected, this option enables the server to close a cursor automatically after a period of inactivity. For the existing accounts that does not have this field, the value for this check box returns false, which is backward compatible.

  • Redshift Snap PackEnhances the Snap pack by adding two accountsRedshift Cross-Account IAM Role Account and Redshift Cross-Account IAM Role SSL Account to support Cross-Account IAM Role in Redshift Snaps.

  • SOAP Snap PackEnhances the SOAP Execute Snap by including an additional output view. When named debug (all lower-case), the Snap outputs the SOAP request headers, envelope, and the output document that is written to the default output view. Originally deployed as 423patches7411 (Latest), this Snap Pack is now part of 4.24 GA (Stable).

  • Splunk Snap PackEnhances the Splunk Search Snap by adding a field, Response Mode, which allows receiving either JSON or XML response from the Splunk server. The default mode is XML, to enable backward compatibility.  Originally deployed as 423patches7504 (Latest), this Snap Pack is now part of 4.24 GA (Stable).

  • Tableau Snap Pack (Deprecated)Fixes an issue when updating user information in the Tableau REST Snap by not overwriting the the site ID or user ID if the entries already exist.

    Behavioral Change

    In the 4.23 release, the Tableau REST Snap had a defect where it used site ID and user ID from the Tableau Account even if the selected REST operation required a site ID and/or user ID from the input document. This issue is fixed in the 4.24 release, so that the Snap uses values for the said IDs from the input document when available. Since this fix changes the Snap behavior, it is possible for production Pipelines to fail after the 4.24 release. Hence, you need to reconfigure the Tableau REST Snap using the site ID and user ID values from the input document.

  • Teradata Snap PackFixes an issue with TPT Load Snap wherein now a null value is load as null and empty string is load as empty string.

    • This fix may cause existing pipelines to fail if empty string values are expected to be loaded as null.

    • Following are the new configurations:

      • VARCHAR QuotedData= Optional

      • VARCHAR OpenQuoteMark= \”

      • VARCHAR NullColumns= Yes

Documentation Enhancements

Snowflake Snap PackUpdated the Snap documents in this Snap Pack to include the following:

  • Security Prerequisites required to execute the Snaps.
  • Minimum permissions required to execute the Snaps.
  • Commands the Snap uses internally to execute the Snaps.

Deprecated Snaps

  • Starting from 4.24 GA, the following Snap Packs are deprecated. Contact support@snaplogic.com, if your existing Pipelines use Snaps from any of these Snap Packs.
    • Adobe Experience Platform Snap Pack
    • Concur Snap Pack
    • Google DFA Snap Pack
    • SAP Analytics Cloud Snap Pack

Google DFA and Adobe Experience Platform Snap Packs are now supported by the SnapLogic Professional Services team as private Snaps, in case you want to use them in your Pipelines. Contact your SnapLogic account manager for more information.

Known Issues

  • Cassandra - Select Snap: This Snap supports inet Data Type that stores the IP address values. Upon validation, the Snap must display a blank space followed by the corresponding IP address value in its output view, which is the expected behavior. However, in the 4.24 Release, the Snap incorrectly displays empty string as null for inet Data Type followed by the IP address value in its output view.
  • Salesforce Create Snap: The Snap passes downstream data even when the Pass through check box is not enabled.

Prior 4.23 Snap Dot Releases are Merged into 4.24 GA

Snap PackDate of UpdateSnap Pack Build NameUpdates
Transform  423patches7958

Fixes an issue in the JSON Splitter Snap by not logging a NumberFormatException error, that is, an error which is logged while converting a string into a numeric value.

Binary 423patches8453Fixes an issue in the File Writer Snap with the ADL protocol, to perform the correct action when OVERWRITE is selected from the File Action drop-down field.
 423patches8397Fixes an authorization issue in the Snap Pack by migrating to a verified Google OAuth application.
Binary 423patches8368Fixes an encryption issue with the File Operation Snap by implementing both SSE-KMS and SSE-S3 supports to the Snap.
JDBC 423patches8027Fixes a multiple connection issue in the JDBC Snap Pack that occurs when the Auto Detect field is enabled for each execution of the Snap by storing a copy of the database name.
Binary 423patches8368

Fixes an issue in the Binary Snap Pack by removing the plaintext credentials in the file URL from the JCC log messages.

Active Directory

LDAP

 423patches7454

Adds the Pass through check box in all the Snaps to include pass-through functionality. Select this check box to embed the upstream input documents under the original field of the output document along with other records.

Active Directory  423patches8210

Fixes an issue of fetching search records in the Active Directory Search Snap by adding a new field, Limit, to specify the number of search records to fetch from the Active Directory.

Your existing Pipelines that use Page Size for limiting records may fail to execute. Hence, modify your Pipelines using the Limit field.

SQL Server  423patches8190Fixes an issue with SQL Server - Execute to handle SQL statements that begin with special characters.
Binary 423patches8099Enhances the Snap Pack by upgrading the SMB client library.
Google Directory  423patches7817Fixes the authorization issue in the Snap Pack by migrating to a verified Google OAuth application.
Binary 

 

423patches7958Fixes an issue with the File Writer Snap by avoiding overwriting of documents when appending the data to a CSV file in SFTP.
Confluent Kafka 423patches7900
  • Removes the Confluent prefix from the Snaps and accounts in the Snap Pack. However, the Snap Pack name continues to be Confluent Kafka Snap Pack.

  • Adds Wait For Full Count check box to the Kafka Consumer Snap to determine how a positive value for the Message Count field must be interpreted.

    • Enabled (by default): The Snap continues polling for messages until the specified count is reached.

    • Disabled: If there are fewer messages currently available than the specified count, then the Snap consumes the available messages and terminates.

      Known Issue

      The Wait For Full Count check box activates only when you provide a positive integer value in the Message Count field. However, it does not activate when you use an expression for Message Count even if the value evaluates to a positive number.

      Workaround: To activate this check box, temporarily replace the Message Count expression () with a positive integer, select the desired state for Wait For Full Count, and then restore the original value in the Message Count field.


  • Adds support for writing and reading record headers.

    • The Kafka Producer Snap has a new Headers table to configure the Key, Value, and Serializer for each header to be written.

    • The Kafka Consumer Snap reads any headers present on the records it consumes. It provides two new fields to configure how the header values should be deserialized – Default Header Deserializer and Header Deserializers, for any headers that require a deserializer other than the default.

  • Adds support for writing and reading each record’s timestamp.

    • The Kafka Producer Snap has a new Timestamp field that can be configured to set each record’s timestamp, which is the number of milliseconds since the epoch (00:00:00 UTC on January 1, 1970). This can be set to an expression that evaluates to a long integer, or a string that can be parsed as a long integer, or a date. If you specify no expression, or the value is empty, then the timestamp is set to the current time.

      The Timestamp field is only relevant if the Kafka topic is configured with message.timestamp.type = CreateTime (which is the default). For more information, see the official Kafka documentation.

    • The Kafka Consumer Snap has a new check box, Include Timestamp, which by default is disabled for backward compatibility. If enabled, the output for each record includes its timestamp in the metadata.

  • The Kafka Producer Snap has a new check box, Output Records, to determine the format of each output document when configured with an output view.

    • Disabled (by default): The Snap’s output includes only the basic metadata (topic, partition, offset) for each record, along with the original input document.

    • Enabled: Each output document contains a more complete representation of the record produced, including its key, value, headers, and timestamp.

  • The Kafka Consumer Snap has a new field, Output Mode, with two options:

    • One output document per record (the default): Every record received from Kafka has a corresponding output document.

    • One output document per batch: Preserves the batching of records as received from Kafka. Every poll that returns a non-empty set of records results in a single output document containing the list of records as batchbatch_size and batch_index. This mode is especially useful when Auto Commit is disabled and Acknowledge Mode is Wait after each batch of records, depending on the nature of the processing between the Kafka Consumer and the Kafka Acknowledge Snaps.

  • Removes the Add 1 to Offsets check box from the Kafka Consumer Snap.

  • Removes the Account tab from the Kafka Acknowledge Snap, as it no longer needs an account.

The Confluent Kafka Snap Pack documentation will be updated along with 4.24 GA, scheduled for .  

Transform  423patches7898
  • Fixes an issue in the In-Memory Lookup Snap to correctly handle the Join path in the format like $['join path'].

  • Fixes an issue in the XSLT Snap, wherein null binary header values are now converted to blank strings when injecting them as parameters in the stylesheet.
Transform  423patches7792

Fixes an issue in the XML Formatter Snap when it fails to convert input JSON data, with the JSON property having a special character as its prefix, to the XML format by sorting the elements.

Binary  423patches7958

Rolls back the recent patch to Binary Snap Pack (File Writer Snap - 423patches7923) that might induce SSL handshake failures/terminations in existing Pipelines. 

Salesforce  423patches7888
Fixes the the following Snaps to ensure that they maintain lineage when using in Ultra Pipelines. 
This fix does not affect the bulk action Snaps in this Snap Pack that produce more than one output document for each input document.
Binary 

 

423patches7923
Fixes the SFTP connection failure issue in the File Writer Snap by:
  • Ensuring that the BouncyCastleProvider is the first in the list of providers in the Security object.
  • Upgrading the BouncyCastle version to 1.67.

As of April 20, 2021, we recommend that you not use the 423patches7923 build for the File Writer Snap, because it causes connectivity issues with the Snaplex nodes.

Snowflake 423patches7905Fixes the performance issue in the Snowflake - Bulk Load Snap while using External Staging on Amazon S3.
Binary  423patches7795

Fixes an issue with File Writer Snap by skipping the validation of the SAS URI having write permission, if the SAS URI uses an access policy.

JDBC 

 423patches7800

Fixes an issue with JDBC account through a Test Query option to establish a database connection upon using Auto detect option for the Database name.

Google Spreadsheet  423patches7848Enhances the Google Spreadsheet Snap Pack by migrating from v3 to v4 API as Google announces sunsetting the v3 API on June 8, 2021. For more information, see Impact on Migrating Google Spreadsheet Pipelines from v3 to v4.
Marketo 423patches7812

Introduces the Marketo Snap Pack to enable you to automating the process of performing operations to the Asset database and Lead database that manage the potential data for an organization in the marketing industry.

  • Asset Read: Queries the Asset database to retrieve assets using commands.
  • Asset WriteInteracts with the assets using commands and make modifications to the Asset database.
  • Lead Read: Queries the Lead database to retrieve leads using commands.
  • Lead WriteInteracts with the leads using commands and make modifications to the Lead database.
  • Bulk Lead ExtractRetrieves leads in bulk from the Lead database.
  • Bulk Lead UpsertInserts/Updates large number of leads in the Lead database.
OpenAPI 423patches7812Introduces the OpenAPI Snap Pack to enable you to connect to your OpenAPI endpoints. This Snap Pack supports OpenAPI Specification versions 2.0 and 3.0.
SOAP 423patches7441

Enhances the SOAP Execute Snap by including an additional output view. When named debug (all lower-case), the Snap outputs the SOAP request headers, envelope, and the output document that is written to the default output view. 

Script 423patches7671

Fixes an issue with the PySpark Snap by removing the dependency on the json-path library, thus avoiding a conflict between the external library version and the SnapLogic json-path.jar.

MySQL  423patches7732

Fixes an issue in the MySQL - Bulk Load Snap to support the following versions:

  • MySQL 8.0.17 
  • MySQL 5.6.34
Microsoft Power BI  main76Updates the dependencies and documentation links for all the Microsoft Power BI Snaps.
Transform 423patches7753Fixes an issue with the JSON Splitter Snap's behavior in Ultra Pipelines that prevents processed requests to be acknowledged and removed from the FeedMaster queue, resulting in retries of requests that are already processed successfully.
Binary 423patches7660Enhances the File Poller Snap by adding a field, Exit on first matches, which when set to true stops the Snap from executing after the first file paths matching the filter are written to the output view. If the field is not configured or is set to false (default value), then the Snap continues to poll the directory until the Polling timeout is reached.
SharePoint Online main75

Fixes the error view issue in SharePoint Online - Upload File Snap by dragging a new instance of SharePoint Online - Upload File Snap to the canvas, since the existing Snap that is used with a version that contains the bug continues to fail.

Hadoop 423patches7440Fixes the issue in HDFS Reader Snap by supporting to read and write files larger than 2GB using the ABFS(S) protocol.
SAP HANA 
 
423patches7548Fixes the batch size issue in SAP HANA - Upsert Snap by using a prepare statement when sending the batch request.
Box
 
423patches7526Fixes the intermittent failure in access token refresh for the Box OAuth2 account by adopting the refreshAccessTokenIfExpired() method that checks and refreshes the access token within the last minute of its expiry.
SharePoint Online 
 
main74

Fixes the socket timeout issue in the Snap Pack by making the following changes:

  • Modifies the code to return the ProxyHttpClient instead of the basic HTTP client and handle the custom siteName.
  • Fixes the broken JUnit and code for pagination in the SharePoint Online - List Read Items Snap.
Adobe Experience Platform (Deprecated in 4.24 GA)
 
423patches7447Fixes the Adobe Experience Platform Execute Snap issue of not passing data correctly to the downstream Snap by creating Map obj = new LinkedHashMap(); inside loop. LinkedHashMap is a hash table and linked list implementation of the Map interface, with a predictable iteration order. 
Splunk 
 
423patches7504Enhances the Splunk Search Snap by adding a new field, Response Mode, which allows receiving either JSON or XML response from the Splunk server. The default mode is XML, to enable backward compatibility.
SAP
 
422patches7378Enhances the SAP Execute Snap to process the structure that contains nested Table Type fields in the output document by recursively parsing them into a Map or a List set.


Data Automation

SnapLogic's data automation solution speeds up the identification and integration of new data sources or the migration of data from legacy systems. The solution can automatically detect duplicate, erroneous, or missing data, or identify structures and formats that do not match the data model. Data automation can accelerate the loading and transformation of your data into the data warehouse, speeding up the data-to-decisions process.

ELT: New Feature

  • Adds support for Azure Synapse database. You can now use the ELT Snap Pack to transform tables for Snowflake, Redshift, and Synapse databases.

Supported JDBC JAR Versions

ELT Snaps require a corresponding JDBC JAR file to connect to your target database and to perform the load and transform operations. 

Supported DatabaseCertified JDBC JAR FileDownload Link
Snowflakesnowflake-jdbc-3.12.16.jarDownload this JAR file
Redshiftredshift-jdbc42-1.2.43.1067.jarDownload this JAR file
Azure Synapsemssql-jdbc-8.4.1.jre8.jarDownload this JAR file

Using Alternate JDBC JAR File Versions

We recommend you to use the listed JAR file versions for the current release. However, you may use a different JAR file version of your choice.

Updated Snap Pack

  • ELT Snap Pack:

    • ELT Database Account:
      • Enhances the ELT Database Account to support the Azure Synapse database.
      • Enhances the JDBC URL support for connecting to Redshift and Azure Synapse databases to work with the following URL formats.
        • Redshift: 
          jdbc:redshift://endpoint:port/<databaseName>?<parameter1=value1>&<parameter2=value2> 
          OR
          jdbc:
          redshift://endpoint:port/database?ssl=true&UID=your_username&PWD=your_password
        • Azure Synapse: 
          jdbc:sqlserver://endpoint:port;<database=databaseName>;<parameter1=value1>;<parameter2=value2>;
          OR
          jdbc:
          sqlserver://yourserver.database.windows.net:1433;database=yourdatabase;user={your_user_name};password={your_password_here};encrypt=true;trustServerCertificate=false;hostNameInCertificate=*.database.windows.net;loginTimeout=30;

      • Alternatively, you can make use of the UsernamePasswordPort Number, and Database Name fields, along with the Advanced Properties > URL Properties field set to provide the parameters required for building your JDBC URL.

        Your existing account configurations need no changes

        The ELT Database Account continues to work with the existing way of specifying the JDBC URL for Redshift - jdbc:redshift://<endpoint> with the remaining parameters provided separately within the Snap Account.

    • ELT Aggregate: Enhances the Snap to:
      • Support Azure Synapse's T-SQL aggregate functions and the aggregate functions in Snowflake and Redshift databases.
        • General Aggregate Function COUNT_IF in Snowflake.
        • General Aggregate Functions in Snowflake.
        • Linear Regression Aggregate Functions in Snowflake.
        • Aggregate Concatenation Functions in Snowflake, Redshift, and Synapse.
        • Percentile Distribution Functions in Snowflake and Redshift.
      • Suggest appropriate column names to select in the Snap fields for Snowflake, Redshift, and Synapse databases.

    • ELT Insert Select: Enhances the Snap to:
      • Suggest appropriate column names to select in the Snap fields.
      • Create Hash-distributed tables using the Target Table Hash Distribution Column (Azure Synapse Only) field when using Merge Into statement.

    • ELT Join
      • Enhances the Snap to support Natural JOINS (NATURAL INNER JOIN, NATURAL LEFT OUTER JOIN, NATURAL RIGHT OUTER JOIN, and NATURAL FULL OUTER JOIN) in addition to the INNER, LEFT OUTER, RIGHT OUTER, FULL OUTER, and CROSS Joins in Azure Synapse Database. This enhancement also makes account configuration mandatory when using this Snap.

    • ELT Load: Enhances the Snap to:
      • Support the File Name Pattern option using Key Based Mechanism for Redshift database. 
      • Suggest appropriate column names to select in the Snap fields for Snowflake, Redshift, and Synapse databases.
      • Create Hash-distributed tables using the Target Table Hash Distribution Column (Azure Synapse Only) field when the Load Action is selected as Drop and Create table.

    • ELT Merge Into: Enhances the Snap to:
      • Suggest appropriate column names to select in the Snap fields for Snowflake, Redshift, and Synapse databases.
      • Include the Target Table Hash Distribution Column (Azure Synapse Only) field for the Snap to create hash-distributed tables.
      • Include the Update Expression List - When Not Matched By Source field set to allow defining one or more Update Expressions for the WHEN clause - WHEN NOT MATCHED BY SOURCE. This applies to Azure Synapse database.
      • Include the Target Table Alias field to specify the alias name required for the target table. The Snap is also equipped with the ability to auto-replace the actual table names (with the alias name), if any, used in the ON clause condition, secondary AND conditions, Update Expression list, or Insert Expression list. This applies to Snowflake, Redshift, and Synapse databases.

    • ELT Sample: Enhances the Snap to:
      • Support sampling type for tables by adding Number of Records and Percentage of Records fields. 
      • Support sample clauses for tables in Azure Synapse.

    • ELT Transform: Enhances the Snap to:
      • Display input schema and output schema based on the upstream and downstream Snaps connected to this Snap.
      • Delete fields mentioned in the Expression field from the Snap's output when the mappings have an empty Target Path.

    • ELT Window Functions: Enhances the Snap to support the following Window Functions in addition to the existing ones:
      • Value Based Analytic Functions
      • LEAD and LAG Analytic Functions

    • Fixes the issue of displaying generic error messages for Triggered Task failures with ELT Pipelines by displaying detailed error messages for ease in debugging.

We recommend you to create ELT accounts for Snaps (where required) through the respective ELT Snaps in Designer. Avoid creating ELT accounts via Manager, since ELT accounts use the functionality of the new form UI, which is currently supported only in Designer.

Updated eXtreme Snap Packs

Known Issues

  • ELT Pipelines that run successfully may fail during validation with the error class java.lang.Boolean cannot be cast to class java.lang.Number when fetching bit values from Azure Synapse database tables as the ELT Snaps currently do not support the use of bit data type.
  • Snaps in the ELT Snap Pack that contain the Schema Name field display schema name suggestions from all databases that the Snap account user can access, instead of the database selected in the Snap account or the Snap Settings.
  • The ELT Limit Snap does not currently support applying an ELT Limit Offset when fetching data from an Azure Synapse database.
  • Breaking Change for Pipelines consisting of PySpark Script, Parquet Formatter, or ORC Formatter Spark SQL 2.x Snaps: Due to an unexpected field name change internally, existing Pipelines (prior to 4.24 GA) will likely fail. You will need to recreate the said Pipelines for them to successfully execute.
  • No macro found named "ME_Chrome_Saving_Account_Credentials" on page "Configuring Spark SQL 2.x Accounts" in space "SD".

    If you're experiencing issues please see our Troubleshooting Guide.

Prior 4.23 eXtreme Dot Releases are Merged into 4.24 GA 

None.