In this article

Key New Features in SnapLogic

Platform:

4.24 UAT Delta

4.24 Dot Releases

Platform

UI

Standard-mode Snaps

Data Automation

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.

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

  New Display	Time Zone
  Europe/London	GMT/BST
  Europe/Paris	CET/CEST
  Asia/Hong Kong	HKT
  Asia/Bangkok	ICT
  Asia/Dubai	GST

• 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:
  • HubSpot Read: Retrieves the specified entity's details from HubSpot.
  • HubSpot Create: Creates an entity in HubSpot.
  • HubSpot Update: Updates an entity in HubSpot.
  • HubSpot Delete: Deletes the specified entity from HubSpot.
    
    

• Marketo Snap Pack: 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. This Snap Pack offers the following Snaps:
  • Asset Read: Queries the Asset database to retrieve assets using commands.
  • Asset Write: Interacts with the assets using commands and make modifications to the Asset database.
  • Lead Read: Queries the Lead database to retrieve leads using commands.
  • Lead Write: Interacts with the leads using commands and make modifications to the Lead database.
  • Bulk Lead Extract: Retrieves leads in bulk from the Lead database.
  • Bulk Lead Upsert: Inserts/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:
  • Power BI Delete: Delete entities from the workspace.
  • Power BI Post: Add/create entities in the workspace.
  • Power BI Post Import: Import PBIX, RDL, XSLX files or files from OneDrive into the workspace.
  • Power BI Push Dataset: Create datasets or modify tables or table schema in the workspace.
  • Power BI Read: Read entities in the workspace.
  • Power BI Read Groups: Read/retrieve entities matching a specified search criterion in the workspace.
  • Power BI Update: Update entities in the workspace.
    
    
• OpenAPI Snap Pack: Introduces 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.
  
  • OpenAPI: Calls 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:
  • Teams - Channel Operations: Allows performing channel operations like add/remove/list channel members and rename channel. 

  • Teams - Create Channel: Allows creating a public or private channel within an existing team.

  • Teams - Create Team: Allows creating a new team in the Microsoft Teams environment.
  • Teams - Send Channel Message: Allows sending messages and replying to messages to members in a channel.
  • Teams - Team Operations: Allows to manage teams, channels, and member participation within the organization.
    
    

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 Pack: Enhances the Snap Pack to support Cross-Account IAM role that allows to access the queues residing in another AWS account.
  
  
• Binary Snap Pack: Enhances 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 batch, batch_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:
  • Enhances the Oracle - Stored Procedure Snap to ignore the parameters evaluated as null by using the Ignore Null Parameters check box. This applies for parameters with defined default values.
    
    
  • Stored Procedure Snaps: Enhances the Stored Procedure Snaps to accept parameters from input documents by column keys. If the values are empty, the parameters are populated based on the column keys for easier mapping in the upstream Mapper Snap. This enhancement impacts the following Snaps:
    • Azure SQL - Stored Procedure
    • MySQL - Stored Procedure
    • Oracle - Stored Procedure
    • SAP HANA - Stored Procedure
    • SQL Server - Stored Procedure
      
      
  • Select Snaps: Enhances the Database Select Snaps to return only the selected output fields or columns in the output schema (second output view) using the Fetch Output Fields In Schema check box. If the Output Fields field is empty all the columns are visible. This enhancement impacts the following Snaps:
    • Cassandra - Select
    • Generic JDBC - Select
    • MySQL - Select
    • Oracle - Select
    • PostgreSQL - Select
    • Redshift - Select
    • SAP HANA - Select
    • Snowflake - Select
    • SQL Server - Select
    • Teradata Select
    • Vertica - Select
      
      
• Google Spreadsheet Snap Pack: Enhances 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 V4. Originally 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 Pack: Fixes 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 Pack: Enhances the Snap pack by adding two accounts, Redshift Cross-Account IAM Role Account and Redshift Cross-Account IAM Role SSL Account to support Cross-Account IAM Role in Redshift Snaps.
  
  
• SOAP Snap Pack: 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. Originally deployed as 423patches7411 (Latest), this Snap Pack is now part of 4.24 GA (Stable).
  
  
• Splunk Snap Pack: Enhances 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).
  
  

• /wiki/spaces/AP/pages/1438313: 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 Pack: Fixes 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 Pack: Updated 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

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

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. 

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 Username, Password, Port 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.

Updated eXtreme Snap Packs

• eXtreme Execute Snap Pack: Enhances the eXtreme Execute AWS Account to support the use of cross-account IAM roles. JAR Submit - Spark SQL 2.x and PySpark Script - Spark SQL 2.x Snaps can now be used with cross-account IAM roles. See Configuring Cross-Account IAM Role Support for eXtreme Snaps for instructions to define a Cross Account IAM role in your AWS environment. 
  
  
• eXtreme Redshift Snap Pack: Enhances the /wiki/spaces/AP/pages/836534651 Snap by adding the Enable SQL query editor check box to enable you to enter the SQL query in a separate editor window.
  
  
• eXtreme Snowflake Snap Pack: Enhances the /wiki/spaces/AP/pages/722010467 Snap by adding the Enable SQL query editor check box to enable you to enter the SQL query in a separate editor window.
  
  
• Spark SQL 2.x Snap Pack: Enhances the AWS Account for Spark SQL 2.X to support the use of cross-account IAM roles. File Reader - Spark SQL 2.x and /wiki/spaces/AP/pages/410091608 Snaps can now be used with cross-account IAM roles. See Configuring Cross-Account IAM Role Support for eXtreme Snaps for instructions to define a Cross Account IAM role in your AWS environment. 
  
  

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.

• The excerpt 'ME_Chrome_Saving_Account_Credentials' was not found in the space 'AP' or you may not have the necessary permissions to access it.

Prior 4.23 eXtreme Dot Releases are Merged into 4.24 GA 

None.