May 2018, 4.13 Release Notes

In this Page

Before you begin

You may need to clear your browser cache before you log into the latest SnapLogic Intelligent Integration Platform (IIP). See the applicable documentation for your browser:

You may see an Upgrade Notice dialog informing that you will be logged out immediately to complete the update process. Because the SnapLogic platform consists of multiple applications, you will likely see this message a few times.

Accounts and Platform updates

Some accounts may have a fixed time for refresh tokens, such as Google accounts that must be refreshed every hour. If that refresh needs to occur when the platform is down for an update, the refresh does not occur. To prevent these accounts from failing after a new platform deployment, we recommend you to refresh your accounts before the designated down time. If the platform is down for longer than an hour, you will need to refresh those accounts once the platform is back online.


Platform

Enhancements

Designer and Manager 

  • Next Snap suggestions in Integration Assistant now include personalized recommendations based on your username, org, and current project. SnapLogic takes these items into consideration to provide the best possible Snap recommendations based on your current situation. For example, users working on a project to migrate from Oracle to ServiceNow would see different Next Snap suggestions than users working on a project to migrate from Oracle to Salesforce.
  • For additional security, you can configure a Groundplex Whitelist to control where nodes in a Groundplex can originate, in order to be authorized to connect with the SnapLogic control plane. This enables you to make sure only nodes inside your network safety zones can connect.

  • The Lifecycle Management feature and related references are removed from the SnapLogic user interface and user documentation.

  • When you migrate accounts from an org with standard account encryption to an org with standard or enhanced account encryption, the source org must recognize the destination org as a "trusted" org. Previously, you had to work with SnapLogic Support to establish trust between orgs. Now, org admins can establish trust between orgs by configuring Trusted Orgs in Organization Settings.

General

  • Starting from 4.13, customers enjoying Platinum support have an option to upgrade the org Snaplex (Groundplex or Cloudplex) and Snap Packs within 35 days after GA. This gives you an opportunity to ensure that the new Snaplex and Snap Packs are stable and working as expected, before rolling out across your orgs in the company. Read more about the new upgrade process

  • Groundplex nodes can now be containerized, allowing customers to optimize their IT infrastructure for costs and performance.  
  • SnapLogic now supports API management integration with Apigee Edge, a popular platform for managing API services. You can export Triggered Tasks, and Ultra Tasks in your SnapLogic environment and manage them as APIs in the Apigee Management Console. API services provided by Apigee Edge include:

    • Specification Publishing
    • API Proxy/Protocol Translation
    • Throttling/Traffic Shaping
    • Market Place
    • Developer Portal
    • Analytics

    As part of this solution, we have augmented defining the pipeline parameters that conform with the Open API specifications. This enables SnapLogic to deliver a complete and seamless API management solution that customers can benefit from. 

  • SnapLogic extends support to Swagger. You can now download the specification of the SnapLogic Tasks as REST APIs in .yaml file format and view the APIs in SwaggerGenerate the OpenAPI (Swagger) description of the SnapLogic Task APIs in a project with a new option in Manager.
  • Enhancements to the Snap schema propagation, to make it easier to build pipelines which do data transformations.
  • Increased the default compressed size limit from 1GB to 2GB for Groundplex and Cloudplex, if the JVM heap size is detected to be more than 10GB. This allows customers to improve utilization of Snaplex nodes.
  • Added high availability (HA) support for Ultra tasks, wherein you can deploy tasks on multiple Snaplexes. The fail over functionality will trigger in any aliased locations, if any of the Snaplexes where the task is running goes down.
  • Enhancements to support updated SAML (Security Assertion Markup Language) specifications for Single Sign On.
  • Enhancements to the SnapLogic expression language:
    • Enhancements to expressions that are dynamically validated and an output preview displays with the result of each sub-expression as well as the final result. View a sub-expression's result by clicking or moving the cursor to the sub-expression. Refer to Expression Language Usage.
    • Performance improvements in the expression evaluation engine to allow for faster processing of complex expressions. 
    • Added error recovery functionality for Ultra pipelines, making it possible to use error pipelines to recover and retry the original request via two new methods – original.load() and original.id

Pipeline Asset Fix Resulting in Functional Change

  • In the 4.12 release, a bug was introduced wherein if parent and child pipelines are running on the same node, but belonged to separate project folders, then files required by the child pipelines were accessed from the parent pipeline's project. This was seen when using relative paths to access assets like files and expression libraries. While this is fixed in 4.13, it is likely to impact a small set of pipelines that are designed as stated.
  • We recommend you to run any impacted Pipelines in your test orgs, after ensuring that the dependent assets are present in the child pipelines' project folder, before upgrading your Groundplex and Cloudplex instances in your production orgs. Storing the required files in both the project folders also avoids the issue. Pipelines using absolute paths are not affected.
  • Contact SnapLogic Support if you have any follow-up questions on this functional change as a result of this fix.

Snaps

This section provides the Snap updates for the Spring 2018 (4.13) release. This release also includes the patches made to Snaps in the 4.12 release, as listed in the 4.12 Dot Releases page. 

New Snap Packs

Adobe Cloud Platform: This Snap Pack reads and writes data sets in Adobe Cloud Platform. This Snap Pack includes the following Snaps:

  • Adobe Cloud Platform Read
  • Adobe Cloud Platform Write

SAP Analytics Cloud Snap Pack: This Snap Pack enables you to connect to the SAP Analytics Cloud instance and perform CRUD operations in it. This Snap Pack includes the following Snaps:

  • SAP Analytics Cloud Read
  • SAP Analytics Cloud Create
  • SAP Analytics Cloud Upsert
  • SAP Analytics Cloud Delete 

Updated Snap Packs

Binary: 

Hadoop:

 RabbitMQ:

  • Added a new Snap, the RabbitMQ Acknowledge Snap to perform an acknowledge, reject or a recover action on the received message from the RabbitMQ server.
  • Added a new property “Message Acknowledge Mode” in the RabbitMQ Consumer Snap to specify the mode of message acknowledgement -- Auto Acknowledge or Pipeline Control (if the RabbitMQ Acknowledge Snap is used).

Redshift: Added the KMS encryption support to the Redshift Snaps -- Redshift Unload, Redshift Bulk Load, Redshift Bulk Upsert, and Redshift S3 Upsert.

Reltio:

Salesforce:

  • Fixed the Salesforce Read Snap that fails to download the PK-Chunking CSV file due to network failure or being out of disk space.
  • Fixed the SFDC Account (standard) that fails to validate.
  • Fixed the Salesforce Lookup Snap that does not match a data type with the bulk API. For instance, boolean data type returns as string.
  • Fixed the Salesforce SOQL Snap that does not preview data in pipelines. 
  • Fixed the PK-Chunking files that do not delete from the "tmp" directory.

ServiceNow: Added Jakarta support to the ServiceNow Snap Pack.

Tableau: Enhanced Tableau Snap Pack to support Tableau version 10.5. This includes support for REST API calls related to Refresh tasks in the Tableau REST Snap.

 

Big Data

  • Fixed a memory leak issue in Hadooplex, caused by Spark pipeline executions.
  • In view of the new upgrade process mentioned in the Platform section above, we recommend that you bring down your current Hadooplex and start again with the new bits, before using the latest SparkSQL Snap Pack version. 

Known Issues

Snaps:

  • Expression parameters from upstream Snaps do not get parsed in HDFS Writer, Parquet Writer, and ORC Writer Snaps. Nonetheless, the pipeline parameters do parse as expected.
  • Using unicode characters in file path or file name result in the files not being read in HDFS Reader, HDFS Writer, Parquet Reader, Parquet Writer, and Binary Snaps.
  • File and Directory suggestion does not work in case of a Groundplex using name service in HDFS Reader, HDFS Writer, Parquet Reader, and Parquet Writer Snaps.


UAT Delta

4.13 Dot Releases