The availability of the following new features, enhancements and corrected issues is dependent on the installed edition of the product and licensed features.
Upload Tableau node
A new "AsyncUpload" property has been added to the Upload Tableau node.
Setting this property to "True" enables you to upload files asynchronously. The node output provides the job URL that you can use outside of the node to get the status of the async file upload.
By default, this property is set to "False" and files are uploaded synchronously.
Publish to DQ+ node
The previously experimental Publish to DQ+ node is now fully supported.
New Proxy and Retry connection properties have been added to the node.
ERP nodes
Updated the ERP nodes to support long ("Int8", ABAP Type "8") and large floating point ("DECFLOAT34", ABAP type "e") types which are present in newer SAP systems.
These changes require at least SAP JCO library version 3.1.8 to be installed. The ERP nodes have been verified against SAP JCO 3.1.8.
When upgrading a Data360 Analyze instance which was using the ERP nodes, the JCO library in use will also need to be updated. The locations and file names for the libraries required by the node have not changed.
Error messages
The text for all unexpected error messages returned by REST APIs, and thus by the UI, can be configured to be redacted for security purposes. The error codes for the errors will still be reported, but the error messages themselves will be replaced by a message indicating to check the application logs. Errors for data flow execution related problems will still be reported correctly to the Errors panel.
To enable redaction of all error messages, set the following in the <site-dir>/cust.prop file and restart the web application:
ls.framework.ls.web.rest.restErrorMessageRedactorName="allText"
Note that by enabling this feature, some UI features, especially with regard to configuration, may be affected and require the ability to consult the application logs to diagnose problems, for example authentication configuration.
Third party library updates
A number of third party libraries have been updated to take advantage of any security and feature updates, including:
- Amazon Corretto JDK - 11.0.21.9.1
- PostgreSQL Database - 13.13
- Tomcat - 9.0.83
Other changes
- Updated a number of HTTP headers to improve application security.
-
Added
laeConfigsubcommand for managing key pairs in the secure store. - When using execution containers, Data360 Analyze will wait longer by default for the container to start. You can now configure the retry and wait options.
- Updated to new version of General SQL Parser (GSP) to fix parsing issues in the DeepSQL node.
- Added a keep alive page at /html/keepalive.html which renders the text "alive" and can be used to ensure that the web application is running.
- Robots.txt is now accessible from the root path /robots.txt.
Corrected issues
|
Issue summary |
Issue number |
|---|---|
| Fixed an issue that prevented you from enabling or disabling a schedule that was created by another user. | LAE-32009 |
| Fixed an issue that prevented the Excel File node from importing files with unsupported characters in the headers. | LAE-32026 |
| Fixed an issue that caused file descriptor leaks on Linux when using a non-default property to specify socket communications. | LAE-31974 |
| Fixed an issue where setting invalid IdP Metadata in the SAML SSO authentication settings returned an uninformative error message. | LAE-31911 |
| Fixed an issue that in some cases caused null pointer exception errors during the execution of a data flow. | LAE-31990 |
| Fixed an issue where the input field on the "Rename" dialog was blank and was not pre-populated with the current name of the object when renaming a data flow, library node or folder from the directory page. | LAE-32462 |
| Fixed an issue where it was not possible to exactly horizontally align a connection point pin to another pin or bend point. | LAE-32461 |
| Fixed an error that occurred when you dropped a node on a data flow, ran the node, then tried to open the pop-out data viewer before saving the data flow. | LAE-32435 |
| Fixed an issue where the Download Logs menu option was not available from the node context menu in read-only mode. | LAE-32431 |
| Fixed an issue where clicking an error on the Errors panel did not navigate to the node on the canvas when the node was at a different composite level to the current view. | LAE-31772 |
| Fixed an issue where nothing was displayed in the node log dialog if an error occurred when retrieving logs that no longer exist. | LAE-30613 |
| Fixed an issue where, if the Download for SharePoint 365 node was run on a Linux environment, then the "_Output" field was incorrectly returning Windows style paths. | LAE-32167 |
| Fixed an issue that sometimes prevented the Upload Tableau node from publishing the datasource. Now, all hyper files should be consistently published. | LAE-31965 |
| Fixed an issue where SharePoint 365 nodes created in 3.8.5 caused errors after upgrading to 3.10.2. | LAE-30539 |
| Fixed an issue where specifying multiple email addresses in the Schedule "On Failure" notification list could cause no emails to be sent for some SMTP servers. | LAE-31906 |
| For Data360 Analyze instances with a very large number of historical runs, the scheduled backup process could possibly fail with an OutOfMemory error. This has been fixed. | LAE-32432 |
| Fixed an issue where the Database Profiler node could not be executed due to missing library entries in its Classpath property. | LAE-31785 |
| Fixed an issue where some scheduled runs would not be executed when the system was under high load with lots of schedules starting at the same time. The missed scheduled runs were not visible in the system. | LAE-32165 |
| Fixed an issue where the use of certain characters in node outputs and connection points would lead to incorrect results or errors on connection filters applied against those names. For instance, applying a connection filter to select an output with parentheses in its name would incorrectly select data sets which matched the name without parentheses. | LAE-32080 |
| Fixed an issue that caused the Azure Datalake Storage Delete, Azure Datalake Storage Get and Azure Datalake Storage Put nodes to stop responding when authenticating. | LAE-31881 |
| Fixed a Jython installation issue. The Java that is packaged with the install is now configured in the Java home environment variable for any processes created from the installer. | LAE-31809 |
| Fixed an issue where the license file could not be accessed when setting up a multi-user configuration. | LAE-31771 |
| The Execute Data Flow node now outputs the full path to the run state in the RunState field, not just the run state name. | LAE-27698 |
| Fixed an issue that could cause backups to fail. | LAE-32268 |
| Fixed an issue that caused connection errors on Azure Datalake Storage nodes. | LAE-32191 |
| Fixed an issue where file patterns on the Azure Datalake Storage List node incorrectly applied to the entire file path, rather than applying to the name only. | LAE-31845 |
| Fixed a timezone issue in the Jython script where the datetime calculations were not returning the correct time offset. | LAE-30042 |
| Fixed an issue where the Azure Datalake Storage List node was not configured correctly for format detection for CSV parsing. | LAE-31788 |
| Fixed an issue that prevented you from unlocking documents locked by a different user. | LAE-30967 |