The availability of the following new features, enhancements and corrected issues is dependent on the installed edition of the product and licensed features.
This release includes a number of features that were introduced in the 3.9.X releases, including execution sandboxing with Docker (server only) and new canvas alignment features.
Rebranded user interface
The user interface styles and colors have been updated to match the Precisely
brand.
Execution sandboxing with Docker (server only)
Execution sandboxing is a new security feature that enables you to secure user access to data file locations on the server. Through provisioning of Docker execution containers on a per user basis, users will only have access to their own file upload location, their own temporary execution data location, and the shared file upload location, ensuring that users cannot access each others data files.
Canvas alignment features
A new Smart Guide feature has been added to enable you to easily align items on the canvas. Additionally, a new align and distribute feature has been added which allows you to uniformly distribute items in a horizontal or vertical direction on the canvas.
Multi-user installation (Linux server only)
A new security feature has been added for Linux users to enable you to configure a multi-user installation.
Enterprise installations on Linux can now run the core components (Web Application, Execution Server, and Database) as separate Linux OS users. These users are assigned stricter levels of file access resulting in a much more secure running environment.
To configure a multi-user installation, it is recommended that you first create the required users, as detailed in the Server Installation Guide, and then follow the configuration steps to complete the setup immediately after installation.
For more information, see the Server Installation Guide.
SharePoint 365 nodes
Along with the Download for SharePoint 365 and List for SharePoint 365 nodes that were introduced in 3.9.2, the following two SharePoint 365 nodes have been added in this release:
- Delete for SharePoint 365 - Deletes the contents from a SharePoint document library or folder using the Microsoft graph API.
- Upload for SharePoint 365 - Uploads the contents to a SharePoint document library or folder using the Microsoft graph API.
These nodes integrate with SharePoint 365 online.
Required input pins
If a node requires a valid input connection to enable it to run, an orange circle is displayed within the required pin until an enabled input is connected. This enables you to easily trace missing input connections that can prevent your data flow from running.
Scheduled data flow email notification
A new run property URL_Link_To_Run has been added to the Data360 Failed Schedule Email Notification data flow. An admin user can reference this property in the schedule email template to include a direct link to the failed run in the email.
Database Metadata node
The Database Metadata node will now switch between using the correct queries for SQL Server or Azure DWH/Synapse when using the SQL Server driver.
Other changes
- A display preference option has been added to the canvas to enable you to show/hide run dependencies.
- The Privacy and Security option has been removed from the Directory Settings list in the Desktop edition of the product as it is now only relevant to the Server edition of the product. Previously, the Desktop product contained a "collect usage data" section in the Privacy and Security page, but this has been removed.
- Last known location information now appears in the Library Node Conflicts dialog.
- Improvements have been made to the look and feel of drop-down menus on the Designer page.
- Use of the EOL library log4j 1.2.17 has been replaced by the actively supported reload4j library. This addresses a number of vulnerabilities that have been identified with log4j-1.2.17.
- Upgraded the shipped JDK to Amazon Corretto 11.0.15.9.1.
- Upgraded OpenSSL to 1.1.1o to address various CVEs.
- Upgraded the embedded Postgres to 13.7.
- The Swagger API documentation page has been removed from the product. For information on supported APIs, see the link to the API documentation from the product help.
- A number of third-party libraries have been updated to benefit from the latest security updates.
Notes
Upgrading to 3.10.0
To upgrade to 3.10.X from 3.4.3 and below, you must do it in
two stages, as follows:
|
Current version |
Upgrade steps |
|---|---|
|
Any version between 3.2.0 and 3.4.3 |
First upgrade to Data360 Analyze 3.8.4, then perform the Data360 Analyze 3.10.X upgrade. |
| Before 3.2.0 |
First upgrade to Data360 Analyze 3.6, then perform the Data360 Analyze 3.10.X upgrade. |
LogicalTypeDefinitions property
If you have previously used the LogicalTypeDefinitions property on the Data Profiler or Database
Profiler nodes to specify custom semantic types, you will need to update your JSON specification
file to match the updated example in the node help page.
Teradata driver version
When using JDBC-based nodes to connect to Teradata, for example the Database Metadata node
and the JDBC Query node, it is recommended that you use the latest version of the Teradata
driver. Driver versions older than 17.10.0.26 can cause potential issues with the Database
Metadata node where views reference objects which no longer exist.
Java version
Data360 Analyze is built and runs on Java version 11. Please check the compatibility of any third
party Java libraries that you are using and upgrade them if required.
Data360 Analyze Command-Line Interface
For information on the latest release of CLI, see the Help pages here.
Corrected issues
|
Issue summary |
Issue number |
|---|---|
| Fixed an issue that caused a data flow run to fail if it contained a run property set with a password property with no value. | LAE-27989 |
| Fixed an issue where changes to property names and property group names in the Define tab of the Properties panel were being saved prematurely, causing an error in some cases. | LAE-28029 |
| Fixed an issue where the installer did not follow the specified choice on whether to backup temporary files on upgrade. | LAE-27667 |
| Fixed an issue where the installer did not use the specified location for temporary execution data. | LAE-28539 |
| Fixed an issue that prevented the import of legacy run property sets. | LAE-28014 |
| Fixed an issue where permissions that were set on the Data360 Nodes and Data360 Samples data flows were not preserved after an upgrade. | LAE-27512 |
| Fixed an issue with the Database Metadata node where table object definition information was not returned if it was not a case sensitive match. | LAE-27885 |
| Fixed an issue where if a username was changed it was possible that both versions of the username would count towards the amount of allowed user licenses. | LAE-27808 |