Versions Compared

Old Version 7

changes.mady.by.user Cindy Hall (Unlicensed)

Saved on

compared with

New Version 8

changes.mady.by.user Cindy Hall (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Set the default Snap Pack version to use when running IIP pipelines.

  • Override the version for specific Snap Packs.

  • Select the New or Old distribution:

    • Current Snaplexe Snaplex versions runs Snaps from the New distribution.

    • Deprecated Snaplexes run Snaps from the Old distribution.

...

  • HTTP Redirect Policy: This new policy enables you to define the behavior of 3xx errors for your APIs. When you apply the policy, the client is sent an HTTP redirect message. For example, you can send an HTTP redirect to force a client to enter user credentials on an HTML login page if an HTTP cookie doesn’t already exist. Another use case is that you can send an HTTP redirect if a web page has moved to a new URL address.

Enhancements

  • The Callout Authenticator API policy now supports additional HTTP methods POST, PUT, & PATCH.

  • The Developer Portal supports referencing external API documentation when publishing. When you publish an API, you can open the specification editor and add the fields that reference external documentation for the API.

    Code Block
    externalDoc:
   Description:
   url:

...

  • The Azure Synapse endpoint supports schema change detection and reconciliation. Learn more.

  • In Orgs with a large number of Accounts and credentials, credentials should now load faster in the data pipeline wizard.

  • Error reporting tables in Snowflake are now created as transient tables to reduce storage costs.

  • Users with view permissions can now mark data pipelines as favorites.

...

Fixed Issues

  • When a data pipeline with Snowflake as a destination encounters an error, it now logs the error record and continues.

 

Behavior Changes

...

Known Issues

  • Users must add credentials for Gainsight PX and Zendesk in Autosync, not in the IIP or AutoSync Manager.

  • Integrations with Zendesk as a source and Google BigQuery as a destination may fail to load records when using the SCD2 load type.

  • Data pipelines with Oracle as the source and Snowflake as the destination incorrectly report the number of updated records when using the Incremental load type. For example, when a record is added, the details show that it was added and updated. The issue occurs because Oracle has the capability to store timestamps with precision down to a nanosecond (by default it is microsecond), but AutoSync timestamps are limited to millisecond precision. Incremental loads depend on the timestamp, and if a record update occurs only nanoseconds after the previous update, AutoSync does not recognize it as an update.

...

  • The APIM Public API - Export APIM policies accepts the query parameter policies_to_export, instead of policies_to_include.

  • The Public API Retrieve config info for a Groundplex accepts the query parameter version. If set to current, the returned configuration is based on the version currently installed on the Snaplex, instead of the latest available version.

  • The Activity Log tracks changes made to Org Settings in Manager. Your organization can now audit changes made to your SnapLogic Org by referring to the events in the Activity Log.

  • Scheduled Tasks improved with new misfire thresholds. This new mechanism offers granularity in tasks that run in intervals of less than 15, 10, 5 minutes, and even 1 minute.

  • The Scheduled Task dialog now displays an error when you enter an invalid number of task runs. When you select After # of Runs and enter a number above the maximum value supported by the field or a negative number, an error prompts you to enter a valid number range of 1 - 1,000,000. Previously, the dialog would allow you to save the Scheduled Task with the invalid number and then subsequently fail. Only upon viewing the Task Details page, would you discover the task failure resulting from the invalid field value.

...

  • Fixed an issue where the RunTime Archive did not display content.

  • Fixed an issue where the API response for Snaplex Configuration REST API gave the incorrect Snaplex version to download.

Behavior Changes

  • Org admins can no longer enter URLs into User Notifications. Before this release, if an Org admin entered text that resembled a URL, the UI would turn it into a clickable link in the notification display viewed by the user. This is no longer possible. Users have to copy and paste any valid links shared by an Org admin into a browser to access the target site.

  • When a task is copied to another Org, the Snaplex references are fixed by the runtime_path_id property and not by the Snaplex name. The values for the Location and Environment fields in the Snaplex dialogs should match - not the labels.

...

  • Fixed an issue with the Anaplan Action Snap that caused the File Not Found error to display when multiple instances of the Anaplan Upload Snap (which included empty files) were executed concurrently.

  • Fixed an issue with the Azure Active Directory Create Entry Snap that caused it to fail with a cast error when a boolean value was entered in a field where expressions were enabled.

  • Fixed an issue with the Google Analytics 4 Create Report and the Create Realtime Report Snaps that improperly rounded off decimal data. You can now view the precise value in the report.

  • Fixed an issue with the HTTP Client Snap that displayed incorrect cookie information, with a null value in the cookies when you have duplicate cookies in the header. The Snap now displays the cookie information correctly.

  • Fixed an issue with the JSON Splitter Snap that caused the pipeline to terminate with excessive memory usage on the Snaplex node after the 4.33 GA upgrade. The Snap now consumes less memory.

  • Fixed an issue with the Microsoft OneDrive Snap Pack where the Snaps displayed Duplicate key OneDrive error. The Snaps now hide the drive details stored in the PreservationHoldLibrary folder when displaying suggestions. You can use the Drive ID to search for items in the PreservationHoldLibrary folder.

  • Fixed an issue with the Oracle Bulk Load Snap that was not resilient to the errors previously when trying to auto-discover the existing SQLLDR utility paths in the node. The Snap is now robust to those errors.

  • Fixed an issue with the Pipeline Execute Snap that caused a null pointer exception during the retry when the input view was a Binary type. Retry is not supported for a Binary input view with this Snap.

  • Fixed an issue with the SOAP Execute Snap that caused it to be unable to parse some WSDL files.

  • Fixed an issue with the SQL Server Stored Procedure and Table List Snaps that caused no retries to be executed even though the user had selected a number of retries in the UI when a custom JDBC driver was used

  • Updated the input and output schema for the Marketo Snaps

Behavior Changes

  • When you select the Use datetime types checkbox in the Parquet Reader Snap, the Snap displays the LocalDate and DateTime in the output for INT32 (DATE) and INT64 (TIMESTAMP_MILLIS) columns. When you deselect this checkbox, the columns retain the previous datatypes and display string and integer values in the output.

...