In this article
Platform:
Universal Search includes new Pipeline search
Snaplex-based Scheduler
Notifications via Slack
API Management:
API Dashboard UX improvements
eXtreme:
Cross account IAM support
ELT for Cloud Data Platforms:
Support for Azure Synapse
Ease-of-use improvements
New Snap Packs:
HubSpot, MS Power BI, Marketo, OpenAPI, MS Teams
Updated Snap Packs:
|
This section tracks the changes made during the iterative pushes to the UAT server and the GA release. The following is the release schedule:
UAT Fixes Snaps
|
Date of Update | Snaplex Build | Updates |
---|---|---|
main-9488 - Patch 3 (Recommended) |
| |
N/A | Control Plane update:
| |
main-9292 - Patch 2 |
| |
main-9191 - Patch 1 |
|
We currently recommend you to use main-9488 - Patch 3 as your Snaplex version. |
Date of Update | Update |
---|---|
Known issues:
| |
Fixes an issue with Orgs using enhanced encryption that run into an error decrypting sensitive information with non-ASCII characters when connecting with end-point accounts. |
Due to an upgrade to the CXF library, SOAP Execute Snap that uses the CXF client targeting SOAP 1.2 endpoints can fail. We also observe increased thread counts related to this upgrade. Hence, during the 4.24 auto-upgrade on , we did not update the SOAP Snap Pack and are moving the stable version for all your Orgs to main7430 (4.23 GA) instead of main8556 (4.24 GA). This should not impact your existing Pipelines. You can also use SOAP Snap Pack version 423patches7441 that was deployed as 4.23 dot release on , if needed. |
|
|
Groundplex Support for Java 11 and Sunsetting Java 8
|
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.
|
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.
New in 4.24
4.23 and Earlier
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. |
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.
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.Teams - Create Channel: Allows creating a public or private channel within an existing team.
We strongly recommend you to use the new form UI enabled in Designer > User Settings () for using the complete functionality in new Snap Packs from 4.23 release onwards. |
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).
|
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:
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 |
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.
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).Tableau Snap Pack (Deprecated): 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.
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.
|
Snowflake Snap Pack: Updated the Snap documents in this Snap Pack to include the following:
Google DFA and Adobe Experience Platform Snap Packs are now supported by the SnapLogic Professional Services team as private Snaps, in case you want to use them in your Pipelines. Contact your SnapLogic account manager for more information. |
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 Snaps require a corresponding JDBC JAR file to connect to your target database and to perform the load and transform operations.
Supported Database | Certified JDBC JAR File | Download Link |
---|---|---|
Snowflake | snowflake-jdbc-3.12.16.jar | Download this JAR file |
Redshift | redshift-jdbc42-1.2.43.1067.jar | Download this JAR file |
Azure Synapse | mssql-jdbc-8.4.1.jre8.jar | Download this JAR file |
We recommend you to use the listed JAR file versions for the current release. However, you may use a different JAR file version of your choice. |
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. |
COUNT_IF
in Snowflake.We recommend you to create ELT accounts for Snaps (where required) through the respective ELT Snaps in Designer. Avoid creating ELT accounts via Manager, since ELT accounts use the functionality of the new form UI, which is currently supported only in Designer. |
None.