Highlights

The SnapLogic® December 2023 Release includes the following:

Admin Manager

• Manage Allowlists for Cloudplex and CORS with an easy-to-use interface

API Management

• Outbound OAuth2 Policy for Proxies

AutoSync

• On-premises endpoints: PostgreSQL as a source and MySQL as a target

• Replace empty values (null handling) transformation

Platform

• Additional Org changes are reported in the Activity log

• Task failure notifications for Not Started state

• Support for untracking Assets from Git

Snaps

• Introduced the PDF Snap Pack

SnapGPT

• Supports generation of a SnapLogic expression from natural language

• SnapGPT is now available in the EMEA region (Europe-Middle East-Africa)

Dot Releases - Platform

Dot Releases - Snaps

Admin Manager

Features

Introduced a user-friendly interface, to manage Allowlists for Cloudplex and CORS.

Open

Open

 

API Management

Features

The Outbound OAuth2 Policy allows users to connect Proxies to backend APIs and systems that use OAuth2 for authentication with preconfigured OAuth2 Accounts. You can access these preconfigured accounts from the Account Tab.

Enhancements

• Group and classify the APIs as per the category and filter selection to include enhanced features that help in easy navigation of the APIs:

  • View the selected API category in the search bar after you browse the API documentation.

  • The API Catalog page subtitle shows the count and selected category.

  • To easily navigate specific APIs, this enhancement now only allows selection of a single category with multiple filters.

Fixed Issues

• Fixed an issue with the JWT Validator policy where token expiration was not checked.

• Fixed an issue with the Generic OAuth2 Policy that would cause request errors when the API was called by a browser in incognito mode.

• Fixed an issue where the Developer Portal Welcome email body did not contain reset password links.

• Fixed an issue where the Swagger Editor accessed from the publish dialog displays the incorrect specification file when you choose a different one.

• Fixed an issue where the Alerts/Activity Notifications did not track versions created from APIs.

Behavior Changes

When you create an API from a Project, assets now appear in the API Version gradually (instead of by bulk update) because of a change made to the migrate API to support file and asset movement asynchronously. This improves the copy operation when there are a large number of assets involved.

Known Issues

When creating an API from a Project and you select individual assets, the API Verison is not populated with the assets.
Workaround: Select the parent asset category from the picker. Then, once the API version is created and populated with all of the assets from the Project, you can delete the individual assets from the API version that should not be included.

AutoSync

Features

• New on-premises endpoints: PostgreSQL as a source and MySQL as a target.

• Transform your data before loading to the destination by handling null values. The wizard now includes a Replace empty values screen:

  Select the suggested value based on the data type, or enter a custom value. For example, the suggested value for a string field is an empty string:

  Learn more about null handling with this feature.

Enhancements

For all endpoints except MySQL, if the destination supports it, AutoSync now stores timestamp values with up to nanosecond precision.

Fixed Issues and Behavior Changes

The December 2023 release fixes the following issues and introduces some changes to behavior. Fixes and changes to the underlying implementation do not automatically propagate to existing integrations. Check the endpoints mentioned in this section to determine whether you need to refresh any integrations. If yes, edit the data pipeline and save it. The simplest edit is to make a minor name change. Any edit that requires a save updates the data pipeline to the latest behavior.

• For the Salesforce endpoint, AutoSync cannot synchronize objects that do not support the bulk load API. Previously, these objects were available to select but caused synchronization to fail. Now, objects that are not eligible for synchronization are not in the table selection dropdown. Refer to Salesforce documentation for a list of objects that do not support bulk load.

• Data pipelines with Oracle as the source and Snowflake as the destination now correctly report the number of updated records when using Incremental load.

• Data pipelines with an Amazon Redshift destination using the SCD2 load type now store timestamps up to nanoseconds. Historical records stored before the December 2023 release have a timestamp limited to 3 fractional second digits. (Historical records are those with a value of N (to indicate No) in the destination table autosync_currentrecordflag column.) Records updated after the December 2023 release store timestamps up to nanoseconds.

• For integrations with Google BigQuery as a source or destination, the Filter columns data preview now contains data.

• For integrations with MySQL as a destination, if the source does not define precision for a column that AutoSync maps to a varchar type, AutoSync now creates columns with precision of 255 to avoid MySQL’s row size limit.

• AutoSync does not support some Account types created in the IIP. Previously, you could select a non-supported Account type, such as Salesforce OAuth, in AutoSync to edit. Now, the AutoSync Edit/Remove Credentials screen only lets you edit supported types.

• For integrations that load from Google BigQuery to Google BigQuery, failures can occur if a source BIGNUMERIC column does not have precision and scale set and contains a. value with precision larger than 76. This happens because when the precision and scale for a BIGNUMERIC column are not set in the source, AutoSync sets it to (76, 38) when creating the target table. BigQuery can actually store a BIGNUMERIC value with a precision and scale of (76.76, 38).

• For Google Analytics 4, you can now upload or select an existing JSON key file.

Known Issues

• The data pipeline wizard Replace empty values screen incorrectly shows non-nullable columns. If you specify a replacement value for a non-nullable column, AutoSync ignores it, which is the correct behavior.

• For integrations loading to MySQL, if the source does not define precision for columns that AutoSync maps to a varchar type and values in the source have greater precision and scale than 255, the integration fails. AutoSync sets the precision to 255 to keep under MySQL’s row size limit.
  Workaround: If a failure occurs, you can change the precision and scale in the source to be compatible with MySQL’s default precision and scale.

Monitor

Fixed issues

• The Metrics screen now displays the correct values for memory utilization:

  • Total CPU utilization: The percentage of use for the machine’s CPU.

  • CPU utilization by JVM: The percentage of use for the machine’s CPU by the Snaplex node’s JVM.

  • Memory utilization: The percentage of use of the maximum JVM heap size (not the machine’s physical memory).

Platform

Enhancements

• Changes made to your Git-tracked Assets are automatically indicated with Local modified status in the project asset table. This enables you to view the Projects that are updated in Git without clicking Git status.

• Added the new task status - Not Started to allow configuring alert notifications to a customizable list of users when a Scheduled Task does not start.

• Enhanced the Task scheduling capability to enable scheduling a task to run for every n number of hours, in addition to the existing yearly, monthly, and daily run scheduling options.

• You can now stop tracking SnapLogic Projects with Git via Public APIs.

Known Issues

• Snaplex memory utilization numbers in the IIP dashboard are inconsistent.
  Workaround: Refer to Monitor Metrics for the correct values.

• When scheduling a task to execute across different locales, the pipeline might not execute because non-ASCII characters in the date configuration result in an invalid signature.
  Workaround: If your Snaplexes use different language settings through a global property in the Snaplex, we recommend you set it to Duser.language.format=en -Duser.country.format=EN for the most reliable adherence to the schedule set in the task.

• When retrieving account details, if the SnapLogic Account is not in the same project as the pipeline, the SnapLogic Read Snap might incorrectly retrieve details of an account with the same name from a different project, even when you specify the absolute project path.

Fixed Issues

• Fixed an issue where the alerts debug log level displayed secrets in plain text.

• Fixed an issue where the expression toggle did not display with imported expression libraries.

Behavior Changes

The APIM Migrate Proxy Public API now requires the new dest_proxy_name parameter in the request body if migrating into the same Environment/Org.

Snaps

New Snaps

• Introduced the PDF Snap Pack, which contains the following Snaps:

  • PDF Formatter: Enables you to format an input document as an output PDF document

  • PDF Lock: Password-protects a PDF document to prevent unauthorized access to the PDF file

  • PDF Merger: Merges multiple PDF documents into a single PDF document

  • PDF Parser: Extracts text, images, or tables from a PDF document from any upstream binary source

  • PDF Splitter: Splits a single PDF document into multiple PDF documents

  • PDF Unlock: Removes password protection from PDF files

Enhancements

• Added the HubSpot Private App Account to the HubSpot Snap Pack

• Enhanced the Salesforce Read Snap by adding expression enablement to the following checkboxes:

  • Use PK chunking if supported

  • Include Deleted Records

• SAP Snap Pack

  • Enhanced the SAP IDoc Listener and SAP IDoc Document Listener Snaps with a new Halt on SAP error checkbox for better error-handling capability

Known Issues

• PDF Formatter Snap: Some special Unicode characters or symbols might not be parsed correctly

• PDF Splitter Snap: Some pages in the output might be blank for PDFs that are not parsed correctly

• The PDF Merger and Splitter Snaps do not work in Ultra Pipelines

• The PDF Parser Snap might encounter issues when it parses tables that are embedded images, lack borders, have a complex row-column structure, or span across multiple pages.

SnapGPT

• Supports generating a SnapLogic expression from natural language when you configure a Snap

• SnapGPT is now available in the EMEA region (Europe-Middle East-Africa)

Documentation Enhancements

Enhancements

• Introduced the Patterns Catalog document: The Patterns Catalog in SnapLogic Designer enables you to create your own patterns within your project space from the Patterns tab in the Designer.

• Enhanced the Error handling document with examples and use case scenarios.

• Reorganized the workflow and procedures in the Cache Pipeline document and restructured the Pipeline Cache Properties to enhance accessibility, ensuring easy comprehension for users.

• Improved the Pipeline Queuing documentation by addressing the gaps in information and aligning the content with the latest user interface.