Data360® Analyze 3.6.3 is Now Available - LTS Release

 

 

ATTENTION: In order to continue receiving product update notices, please Sign In and select “Follow” on the Data360 Analyze announcements page here.

 

We are excited to announce the Data360 Analyze 3.6.3 release is now available.

Product downloads are available within our Data360 Analyze Download section.

 

What’s New?

This Generally Available Long Term Support (LTS) maintenance release provides a number of operational, performance and stability improvements, including:

• Greater flexibility in accessing information stored in Amazon S3 buckets across organizational structures
• Selective access to information stored in an Amazon S3 bucket or a Microsoft Azure Blob
• Improved performance when updating information stored in Salesforce
• Ability to edit the contents of a node's code property in a pop-out window
• Ability to highlight a connection
• Streamlined access to error reporting log data
• New 'Reviewer' user role for operational support users
• Ability to configure the retention period for temporary data generated by ad hoc execution of a data flow
• Application installation, upgrade, start-up and audit logging improvements.

  

 Node Enhancements

S3 Nodes
The S3 List, S3 Get, S3 Put and S3 Delete nodes now support cross-account access using Instance Profiles, allowing you to access a S3 bucket in a different AWS account (that you also own).

The nodes provide two new properties to support this use case:

The RoleARN is used to specify the Amazon Resource Name of the role that is assumed when using an Instance Profile to access. The AWS default strategy is used if this property (and the AccessKey) is not set.

The RoleSessionName enables you to specify the role session name that will be assumed when accessing resources in the other account.

S3 Get Node

The S3 Get node now provides two optional properties that enable you to limit the amount of data retrieved from a file in a S3 bucket:

The RangeStart property specifies the initial byte offset of the contents to be retrieved.

The RangeEnd property specifies the last byte offset of the contents to be retrieved. If the RangeEnd property is not set the contents will be retrieved up to the end of the file.

Azure Blob Get Node

The Azure Blob Get node now provides two optional properties that enable you to limit the amount of data retrieved from a file in an Azure blob:

The RangeStart property specifies the initial byte offset of the contents to be retrieved. If the RangeStart property is set, the RangeEnd property must also be set.

The RangeEnd property specifies the last byte offset of the contents to be retrieved. If the RangeEnd property is not set the contents will be retrieved up to the end of the file.

Data360 Update for Salesforce Node

The Data360 Update for Salesforce node has been enhanced to process data in batches using the Salesforce Bulk API 2.0. Previously, this node performed updates on a record by record basis.

The use of the Bulk API overcomes some usage thresholds imposed by Salesforce and can improve update performance. Note: You must have version 41.0 or later of the Salesforce API to use this node.

The node provides two new optional properties that can be used to modify how the node batches data uploaded to Salesforce and how it monitors the progress of the job:

When data is uploaded to Salesforce, the data is split into batches. The BulkApiBatchSize property specifies the size of each batch between 1 and 100 MB (defaults to 30MB). 

When all batches for the job have been uploaded the node polls Salesforce to check the processing status and retrieve the results. The MinimumPollingInterval specifies the interval between checks in seconds (defaults to 30 seconds). Note: polling checks count to Salesforce API usage limits – depending in overall usage of the API, setting the polling interval too low may cause the usage limits to be exceeded.

The properties are hidden by default – use the property panel’s menu option to make them visible:

 

Application Enhancements

Pop-out Code Editor
Nodes with code-type properties now provide the option to edit the property in a pop-out window:

 

The pop-out code editor window can be resized and moved to another monitor – offering greater flexibility when working with larger code segments. 

You can have multiple pop-out code editor windows from different properties open at the same time, allowing you to compare the contents and copy/paste between them.

When a property panel is popped-out the contents of the docked panel are washed-out and the panel becomes read-only:

You can update the docked panel with any changes made in the popped-out panel using the Sync button. You can also bring the popped-out code editor panel to the front using the arrange windows button.

Connection Highlighting

 To make it easier for you follow a connection between nodes you can now hover the cursor over an input pin or output pin and the color of the connection will become black:

Download Node Logs

When troubleshooting issues with nodes, you can now download node data together with node log information:

Analyze Server admin users can specify whether non-admin users are permitted to download node logs and/or data:

The setting also controls the ability for non-admin users to export data from the data viewer as a CSV file and the download of data files from the server.

User Roles

Analyze Server editions now provide an additional user role – a Reviewer.

The Reviewer role provides functionality similar to the Explorer role except that a user who only has this role cannot access the data viewer when viewing a data flow. An example use case for using the Reviewer role would be to allow operational support staff to monitor the execution of scheduled runs without offering the ability to access the data within a data flow.

Management of Temporary Data

The Analyze Server edition now allows an admin user of an Analyze Server instance to configure the retention period for temporary data generated when data flows are run ad hoc (interactively) by users.

Other existing settings control the retention strategy for temporary data associated with scheduled runs.

Application Start-up and Login

When you first launch an Analyze Server instance and navigate to it in a browser, you will see a loading page while the application starts. The login page will only appear once the system is ready.

Installation and Upgrade Improvements

When installing an Analyze Server instance, the installer now allows you to choose where to store temporary data generated by data flow execution. When upgrading the Analyze Server application software, the upgrade process has been improved to require less memory.

Audit Log Improvements

The Analyze audit log now provides additional logging events: 

• A dataflowProcessing event is logged when a scheduled data flow begins execution
• A dataflowProcessed event is logged when a scheduled data flow execution is complete
• The existing nodeProcessed event now includes the following attributes:
  • Start time
  • Execution duration
  • Number of records generated on each output pin.

Database Driver and Other Software Library Updates

The MariaDB JDBC driver has been upgraded to mariadb-java-client-2.6.0.jar.

The Snowflake JDBC driver has been upgraded to snowflake-jdbc-3.12.6.jar.

A number of third-party software libraries have been updated, allowing them to benefit from the latest security updates.

 

Resolved Issues

The following issues have been resolved in this release:

LAE-23512, LAE-23642, LAE-23742, LAE-23807, LAE-23863

LAE-23867, LAE-23869, LAE-23871, LAE-23873, LAE-23931

LAE-23936, LAE-23938, LAE-23965, LAE-23972, LAE-24033

LAE-24049, LAE-24109, LAE-24117, LAE-24121, LAE-24122

LAE-24123, LAE-24144.

 

See the release notes for details of the resolved issues.