Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
minLevel1
maxLevel1
outlinefalse
typeflat
printablefalse

...

...

Dot Releases: Snaps

Snap Pack

Date

Snap Pack Version

Updates

Salesforce

439patches29014

Fixed an issue with the Salesforce Lookup, SOQL, and SOSL Snaps, where errors were not routed to the error pipeline when Route Error Data to Error View was enabled, and a referenced expression variable was missing in the upstream or pipeline parameters.

Oracle

439patches29008

Fixed an issue with Oracle Execute, Select, and Stored Procedure Snaps where the data was displayed in an unexpected structure and without the actual row address value when querying table columns of ROWID type. Now, the Snaps handle the ROWID type columns correctly to prevent the display of the nested output when ROWID is combined in the query with other selected columns.

Note

Breaking change:

With the 439patches29008Snap Pack version if any of your existing Oracle pipelines use the encoded ROWID(by manually handling the Base64 encoded data), your pipelines might break. To prevent your pipelines from failing, you must update your Snap Pack version to the latest version.

Behavior change:

Earlier, the ROWID columns were displayed in binary (Base64 encoded data) form in the output. With the 439patches29008, the Oracle Execute and Select Snaps display the ROWID columns in string form in the output (which can be used for other operations downstream).

Upgrading to this Release

Info

To use the new SnapLogic features and Snaps in the current GA release, ensure that your Snaplexes are upgraded to the recommended version: main-28252 28272 - 4.39 GA (Recommended).

All Snaplexes on older versions will be upgraded to the recommended version during the mandatory automatic upgrade, which is scheduled for 3 PM (PDT) on Saturday, . For other Snaplex versions released this year, view the SnapLogic Release calendar.

...

  • System Configuration now includes the Git Integration page for selecting a Git provider. This supports continuous integration and continuous development (CI/CD) across different environments. Learn more.

    image-20241101-072520.png
  • In the Security section, configure Enhanced Account Encryption (EAE) from the Account encryption page. With a subscription to EAE and use of a Groundplex, sensitive account data is encrypted with a public key in the SnapLogic domain control plane and decryped decrypted with a private key on the Groundplex. Learn more.

    account-encryption.pngImage Removedaccount-encryption.pngImage Added

  • In the Application settings section, configure Asset catalog visibility. The Asset catalog is available to enterprise SnapLogic customers by request. Learn more.

    image-20241106-104259.pngImage Removedimage-20241106-104259.pngImage Added

AgentCreator

AgentCreator represents the next major revision of the GenAI App Builder. It offers advanced features for enterprises to create agents that have the ability to reason and use tools to perform tasks autonomously. The tool can be any SnapLogic connector, pipeline, or API. It also includes comprehensive observability and validation capabilities that allow enterprises to understand and evaluate agent actions.

...

...

...

  • Enhanced the OAuth 2.0 Client Credentials article with an Okta integration example.

Monitor

Enhancements

  • The Integration catalog, available to enterprise SnapLogic customers by request, is now the Asset catalog. It includes the following enhancements:

    • With the new API described in the Platform section, you can add custom metadata columns to the table of tasks and add, update, or delete existing custom metadata values from a task.

    • With the new configuration described in the Admin Manager section, you can allow all users view-only access to the Asset catalog or restrict it to admins.

    • The new Pipelines tab displays standard pipeline metadata:

      catalog-pipelines-tab.png
    • Task details are easier to read, with important information moved to the header and execution statistics split out into a new tab:

      catalog-task-general-tab.png
    • The Custom tab on the Task details pane includes the ability to edit custom metadata values:

      catalog-task-edit-metadata2.pngImage Removedcatalog-task-edit-metadata2.pngImage Added

Known Issues

  • The Asset catalog Edit metadata functionality in the Custom tab of task details has an issue. When editing, if you click Clear to remove an existing value and then click Cancel, the value is deleted instead of being retained as expected.
    Workaround: Re-enter the cleared value and click Save.

  • The average number of documents processed for pipelines that contain a BigQuery Execute Snap is being incorrectly reported as zero. This impacts both the Asset catalog and the Execution overview.

  • In the Asset catalog Pipelines tab, when you filter by the Path column, a search might not return all pipelines that match.

  • The Asset catalog Execution statistics tab for task and pipeline details currently displays no data.

...

Note

Calls to SnapLogic APIs that contain non-RFC-compliant characters space: /? # [] @! $ & ' ( ) * +,; = need had to be corrected removed by 9 PM PT. Please remove delete unencoded characters from the following:

  • Cloud Triggered Tasks

  • SnapLogic Public APIs

  • APIM and Ultra Tasks on SnapLogic-managed Cloudplexes

Note that this issue does not impact customers using the EMEA Control Plane.

...

Important Updates from Snowflake

Deprecated Drivers:

As of February 1, 2024, Snowflake has ceased support of older driver versions in compliance with its Support Policy. You must upgrade to the latest driver version to access important security, performance, and functionality improvements. Ensure that your Snowflake pipelines use the Snowflake JDBC Driver v3.13.27 or a higher version. Learn how to check your current driver version. The Snowflake Snap Pack is bundled with the 3.16.0 JDBC driver, but if you are using your own version, it may be deprecated in accordance with Snowflake Guidelines.

Security Policies:

Snowflake recently signed the Cybersecurity and Infrastructure Security Agency (CISA) Secure By Design Pledge. In line with CISA’s Secure By Design principles, Snowflake recently announced several security enhancements in their platform — most notably the general availability of Trust Center and a new Multi-Factor Authentication (MFA) policy.

Effective October 2024, MFA will be enforced by default for all human users in any new Snowflake account. Service users (accounts designed for service-to-service communication) will not be subject to this MFA requirement.

Basic Authentication Accounts:

If you currently use Basic authentication to access Snowflake, we recommend one of the following:

  • Update your password to a maximum of 14 characters and a minimum of 8, and ensure it does not match any of the previous five passwords. Learn more.

  • Migrate to Key-Pair authentication: This method involves generating a public and private key pair, where the private key is securely stored and the public key is registered with your Snowflake account.

  • Migrate to OAuth2 authentication: This is a widely adopted standard for secure delegated access. It allows applications to obtain limited access to user accounts on an HTTP service, facilitating safer and more manageable authentication flows.

Implementing the above recommendations will secure your data and protect sensitive data, ensuring compliance with Snowflake's updated security policies. Learn more. For questions, contact support@snaplogic.com.

Breaking Changes

Note

JDBC Snap Pack:

Reltio Account deprecation by the end of October 2024

  • Reltio has announced the deprecation of basic authentication using username and password for API access by the end of October 2024 to enhance their platform security. All customers must adopt client credentials and stop using username/password for API access immediately. Reltio will disallow API access using username/password by the end of October 2024. Client credentials are required for any integration or API usage with Reltio.

  • Consequently, SnapLogic deprecated the Reltio Account in the October 2024 release. Any existing Reltio pipelines that rely on the current Reltio Account that uses a username/password for API access will not be supported by Reltio. To ensure the continuity of your pipelines, we recommend that you use the Reltio OAuth2 Account.

...

  • API Suite:

    • Enhanced the GraphQL Client Snap with the Include extensions checkbox to support extensions that enable you to access query content and extension data in a structure similar to the GraphQL response. The non-standard fields in the GraphQL response are now ignored to avoid a possible error.

    • The GraphQL Client Snap now includes an improved error-handling mechanism that emulates how errors are reported in the raw GraphQL response. This enhancement provides additional context and pagination to the error output, which was previously limited to one page. Learn more.

  • Amazon S3:

    • Enhanced the S3 Download Snap with an Enable Staging checkbox that enables you to download an S3 object into a local temporary file. This enhancement addresses the cases where some downstream Snaps take longer to process large volumes of data, potentially causing a connection reset error and pipeline failure.

  • Flow:

    • Added the PipeLoop Snap that enables you to loop on pipeline executions based on a stop condition or iteration limit. The execution of this Snap enables the parent pipeline to control and manage iterative processes using the child pipeline for scenarios where repeated processing is needed until a specific stop condition is met.

  • Kafka:

    • Enhanced the Kafka MSK IAM Account to support Cross-Account IAM Access on Amazon MSK Cluster configured through the Transit Gateway and multi VPC Peering.

    • Enhanced the Kafka MSK IAM Account to support debugging for the IAM configuration. When you enable the IAM debugging (Global properties and Logging Level) in the Snaplex configuration, the account logs the IAM credential identity in the Snaplex log. Learn more.

  • MongoDB:

    • Enhanced the MongoDB Replica and Mongo ReplicaSet Dynamic Accounts to define read preference options when querying data. The default option is Primary, so you cannot allocate the read load to the secondary node. Note that the Secondary preferred mode is not supported for the MongoDB Execute Snap.

  • RabbitMQ:

    • Removed the Route connection errors checkbox from the RabbitMQ Producer and RabbitMQ Consumer Snaps. As a result, any existing RabbitMQ pipelines that are configured with Route connection errors checkbox enabled will stop functioning as before.

      Suggested workaround

      To run your pipelines successfully, you must manually Route the errors to the error view under the Views tab.

    • Added 5672, the default RabbitMQ server value, for the Port field in the RabbitMQ Account.

  • Tableau:

    • Enhanced the Tableau Account and Tableau REST Account with Personal Access Token (PAT) authentication for flexibility and security of Tableau integrations. This enhancement ensures compatibility with MFA (Multi-Factor Authentication) or SSO (Single Sign-on) environments. PAT authentication is the default authentication type for the Tableau REST Account.

...

  • Improved the user experience in RAG menu options. When prompting SnapGPT to generate a pipeline, only one pipeline is generated, while and related pipeline patterns are suggested.

    snapgpt-response-related-patterns.png