I’m pleased to announce the Data3Sixty™ Analyze release is now available.
The application formerly known as Dataverse is now part of our enterprise data intelligence platform - Data3Sixty™ that provides robust data governance, data quality, data preparation and analytics. To learn more about the Data3Sixty™ platform please visit the Infogix website.
This generally available release introduces additional governance and user management controls, and provides greater software deployment flexibility.
The branding of the application has been updated to align with the Data3Sixty platform.
After upgrading an existing installation users may need to refresh their browser cache to view the latest branding changes.
Data3Sixty Analyze Server editions now provide granular control of user permissions on objects displayed in the Directory view, including:
- Data flows
- Library nodes.
Users with the Administrator role can manage the permission and assign ‘grants’ to objects for individual users, groups and roles. The effective permissions of a user are determined by the set of permissions:
- Assigned to the individual (principal)
- Inherited from the role(s) assigned to the principal
- Inherited from the group(s) of which they are a member.
The user’s effective permissions on an object are shown in the Directory view properties panel
The permissions for a folder can be accessed from the context menu in the structure on the left of the Directory view. The Edit Permissions option is only displayed when the user has been granted the ability to edit permissions.
The permissions for a selected folder or other object can also be accessed from the properties panel menu.
A user can control permissions for sub-folders of their ‘My Documents’ folder, and objects contained in the ‘My Documents’ folder and sub-folders.
While a user can create a sub-folder in the ‘Public Documents’ folder they cannot, by default, edit the permissions of the sub-folder. An Administrator can grant the user the ability to control permissions of a sub-folder in the ‘Public Documents’ folder – i.e. enabling the user to be a local administrator of that sub-folder.
An Administrator can set the permissions on a sub-folder in the ‘Public Documents’ folder – e.g. to create a shared folder that is accessible to only members of a group.
When an object is moved to a new folder the permissions of the destination folder override any custom permissions that had been configured for the object.
The following example illustrates one use of the permissions capability:
An Administrator (or the ‘owning’ user) creates the shared sub-folder in ‘Public Documents’
An Administrator sets the shared folder permissions to:
- Remove the inherited permissions from the folder - which allows the permissions to be explicitly set on the folder (1)
- Change the access for the ‘User’ role to No Access, to deny access for all individuals by default (2)
- Grant ‘Edit Properties’ to the individual who is to be the local administrator (3).
The ‘owning’ user can then access the folder and make other adjustments to grant varying levels of access to:
- Provide a specified individual with Write and Execute access, to allow them (subject to their role-based feature access) to run data flows in the folder, edit objects and add or delete objects in the folder (4)
- Provide members of the Testers group with Read Only access, to allow them to view objects in the folder (5).
Note, the permissions on objects in the folder and sub-folders can be changed to provide granular access controls, which override the permissions inherited from the folder.
The application’s user roles have been changed to make the ‘Scheduler’ role a distinct attribute.
The base role is the ‘User’ – which is required for all users and enables the user to log into the application and view the Directory.
A user’s profile would typically also be provisioned with an additional role or roles , e.g. ‘User’ + ‘Designer’ – which allows the user to build and run data flows but not schedule runs.
Users inherit permissions from all of the roles assigned to them, and override permissions set explicitly at the user level.
Local User Password Management
When an Administrator has created a user profile in Data3Sixty Analyze using the ‘Create New User’ dialog the user is classed as a local user. Local users can now change their password.
Session Lock for API Access
The Server editions of Data3Sixty Analyze allow external system to access the application using the published REST API.
When Data3Sixty Analyze is accessed via the API, there is a remote session timeout period of four hours – after which you will need to sign-in again to continue to use the application. The duration of the remote session timeout period cannot be changed.
Data3Sixty Analyze is now supported on SUSE Linux Enterprise Server 12 SP3.
Desktop Edition Silent Installation
System administrators can now streamline the deployment of the Data3Sixty Analyze Desktop edition to desktop machines using a silent (unattended) installation mechanism.
The silent installation mechanism can be used to install or uninstall the application from a desktop machine without user interaction.
See the Data3Sixty Analyze Desktop Installation Guide for further details.
- LAE-9849, LAE-10023, LAE-10333, LAE-10334, LAE-10338
- LAE-10373, LAE-10414, LAE-10433, LAE-10455, LAE-10470
- LAE-10511, LAE-10523
See the release notes for details of the resolved issues.