Release Notes 1.16.x

Updated 1 week ago by Robert Galetzka

Release Notes 1.16.0

2024-12-10
Hinweis:
The numbers in brackets refer to the support ticket numbers.

New Features

As previously announced, we have started to update parts of the application and improve the user experience. With version 1.16 dab Nexus gets an updated workspace view, the Package Studio has been refreshed and we introduce the Monitor.

Highlights of the new version

Updated workspace view

The workspace view has been completely redesigned to provide a clearer structure and more intuitive operation.

Revised Package Studio

The Package Studio has been redesigned and minor changes have been made.

Introduction of the Monitor

The new Monitor allows you to monitor all Nexus activity such as runs, tasks or resources from a central location.

Connections

SAP data can now be written to Microsoft Fabric Open Mirror, Fabric Lakehouse, Fabric SQL Database or Snowflake using dab Nexus.

Changes on the workspace view

We realised that the previous overview of workspaces had become confusing. So we have reduced it to the essentials. The previous workspace tiles are now individual entries in the new workspace navigator, with an indicator showing how many tasks are in each workspace.

Click on a workspace to see all the tasks in that workspace. New filter and view options make it easier to find and view specific tasks.

Of course, all previous permissions are taken into account.

Package Studio

As this is one of the oldest modules in Nexus, it was time to update it based on your feedback. These are mainly visual and usability improvements.

  • The SAP System Selector now provides a better overview of available systems, a search function and controls.
  • The 'Known' filter is now called 'Lookup' to better reflect its function.
  • The required configuration options for the package elements have been reduced and updated, and the data strategy selection has been simplified.
  • Field descriptions, which were previously hidden in the tooltip, are now in the foreground.

In addition, the search for SAP tables has been extended to include table descriptions. This means, for example, that SAP tables with suppliers in the description can be found by searching for 'suppliers'. This is useful for those who do not know the technical names of all SAP tables. The search terms must of course be entered in the language set for the SAP connections.

Monitor

In this release, the monitor is available in the dab Nexus, which can be found in the navigation bar. This view gives you comprehensive information about runs, tasks and resources, such as when which tasks and runs were executed, their status and statistics. You can filter by date, task type, last run time, data volume, tags or connections used and more. The columns in the dashboard can be customised and moved around depending on the view selected (Runs, Tasks or Resources). For more details on each view, see the corresponding articles.

Connections

For some of our users, the final destination of the data is not SQL Server, but Snowflake or Microsoft Fabric. Nexus can now store the extracted data directly into these sources, without SQL Server as an intermediate storage location.

Microsoft Fabric

Once the data has been extracted, it is uploaded directly into the Microsoft Fabric environment, either the Lakehouse or the Open Mirror. Once uploaded, a delta merge is automatically performed in Microsoft Fabric.

If a connection exists, a replication task can be created with this connection to extract the SAP data to the specific connection.

A licence upgrade is required to use the Connection feature, please contact sales@dab-gmbh.de.

Bugfixes

  • Fixed a problem that could crash the application [#272009]
  • Fixed a problem where it was not possible to enter date values for the Fixed value filter type in Package Studio [#272092]
  • Fixed a problem when splitting Excel files [#7125]

Sonstiges

  • Negative offset can now be specified in the scheduler [#272042]
  • New application preference option 'Skip Resolve Warning'. This option causes resolve warnings to be ignored during data extraction. Non-existent tables and fields are ignored, allowing the extraction to continue without interruption. Data from unresolved sources is not included.


How did we do?


Powered by HelpDocs (opens in a new tab)

Powered by HelpDocs (opens in a new tab)