- You can create a schedule for a selected data flow from the details panel of the Dataverse Directory view
- The name and descriptive information can be specified for the schedule. The schedule can be active on creation or be initially set to disabled.
- The interval between scheduled runs is set using the schedule editor options.
- You can specify run properties to enable parameterized execution of the scheduled data flow.
- Schedules can be viewed and managed from the Dataverse Directory view.
- You can control whether a schedule is enabled or disabled, as well as delete redundant schedules.
- You can view the scheduled runs associated with a selected schedule. The execution status indicates the progress or final status of the runs. You can drill-in to examine a particular data flow run and inspect the intermediate data and run properties associated with that run.
- You can set and manage the scheduled run purging rules from the Directory view. The purging rules apply to each individual schedule (e.g. keep 50 runs will retain the most recent 50 runs for each schedule).
- Where desktop automation is to be frequently used, it is recommended that the Dataverse application is configured to automatically start in the background when the user logs onto the machine. Scheduled execution of a data flow requires the Dataverse user to be logged into the machine and the Dataverse application to be running. The Dataverse installer provides an option to configure the Dataverse application to automatically start the Dataverse processes when the user for whom Dataverse was installed logs into the machine.
Script-free Configuration of Sort Node
- The Sort node now provides an easy-to-use editor that enables the node to be configured without using Dataverse script.
Improved Interactive Performance
- The responsiveness of the user interface has been improved when performing common actions such as dragging nodes from the node palette to the canvas, editing node properties, etc – enhancing user experience.
Improvements to Storage of User Preferences
- User preferences such as the visibility and width of the Node Palette and Properties panels are now saved within the application.
- This allows the user preferences to be consistent when multiple browsers (Chrome, IE) are used to access the Dataverse application.
Default Run Properties
- The Canvas properties panel now includes three standard run properties that are automatically generated by Dataverse: CurrentTime, CurrentDateTime and CurrentDate.
- These run properties are typically used with scheduled runs. When used in an interactive data flow execution the property values are set to the time/date-time/ date when the node is requested to run.
- If required, the default value can be overridden by entering a value in the property.
Overriding Default Property Values
- Some nodes provide default values for properties (e.g. the Static Data node). Previously it was not possible to ‘blank out’ these default (inherited) values as the default values were reinstated if the entered property was blank (empty).
- Now, if the default property is blanked out, the blank value is retained by that instance of the node.
- If a value has been blanked out or modified, the original default value can be restored using the property’s context menu.
Improved layout of Properties panel
- The layout of the node Properties panel has been changed to allow you to focus in on the properties that are most pertinent for each node.
Only sections of the properties panel that contain mandatory properties are expanded by default when a node is added to the canvas.
For existing nodes, property sections are also expanded when you have entered a property value or you have changed a property value from its default value.
Optional input pin placeholders
- Nodes that accept optional input connections now display a placeholder pin. This aids usability by highlighting when you can source input data or node properties from an upstream node in the data flow.
Splash Screen on Dataverse start-up
- The application displays a page to indicate the Dataverse application is loading.
- When the application has loaded, the Dataverse directory view is displayed.
- Information relating to the licensing status of the Dataverse application can now be viewed using the ‘Licensing’ option in the Dataverse information menu or from the licensing link in the ‘About Dataverse’ panel.
- The Simba Hive ODBC drivers are no longer shipped with Dataverse.
- Hive ODBC drivers are available from Hadoop commercial distribution vendors such as Cloudera, Hortonworks, MapR, etc.
- Record Count Tooltip: For data with large numbers of records, the record count displays an abbreviated form of the number, for example "112K“ for "112,451". You can now view the full numerical value in a tooltip by hovering over the record count. LAE-7808
- Import LNA fails on a system with a non-English Locale: Previously, the import of a data flow (.lna file) would fail if the system used a non-English locale e.g. “nl_NL”. The internationalization improvement now allows a data flow to be imported in this situation. LAE-7811
- Right-click menu sometimes doesn't go away in IE11: Occasionally when using Internet Explorer 11, right-click (context) menus remained visible when they should have been removed. This issue is now resolved. LAE-7261
- Right-click menu in Data Viewer gets "stuck" sometimes: In some circumstances when usng the ‘Copy’ option in the Data Viewer’s context menu, the context menu would not disappear until the page had been refreshed in the browser – which resulted in an error. This issue is now resolved. LAE-7683
- After an existing Dataverse installation has been upgraded to 3.0.5 and the installer has finished it is necessary to Stop and then Start the Dataverse application using the ‘Stop Dataverse’ program shortcut and ‘Start Dataverse’ program shortcut on the Windows Start menu.
- If this is not done you will see errors similar to the following when running java-based nodes: “The specified cache directory (C:\Users\<username>\Dataverse\site\data\executions\cache\brain) does not exist”.
- This issue does not affect users who are installing Dataverse 3.0.5 as a new installation rather than upgrading.