Release Notes 1.12.x
Updated 10 months ago
by
Stephanie Krenz
Release Notes 1.12.5
Bugfixes
- Fixed a problem with Analytic Groups that prevented the group from being saved when Custom Analytics and UserExit variants were used.
Release Notes 1.12.4
Bugfixes
- Invalid dates in the SAP system are now saved as 1900-01-01 instead of failing the extraction
Further Changes
- Updated Microsoft.Data.SqlClient to 5.1.3, fixing CVE-2024-0056
Release Notes 1.12.3
Bugfixes
- Email notifications now correctly use the configured
ApplicationUrlfor links
Release Notes 1.12.2
Bugfixes
- Fixed an issue where the HTTPS certificate password was not properly decrypted
- Fixed an issue with online activation
Release Notes 1.12.1
New Features
Email notifications: You can now receive notifications for succeeded, failed or canceled Analytic Runs. After configuring SMTP in the application settings, you can follow an Analytic Task to receive email notifications for the runs of that task.
Report extraction: In addition to tables, you can now also extract SAP reports by adding them to your extraction package in Package Studio.
Permission for SAP and SQL connections and packages: To facilitate collaboration, it is now possible to define the use of SAP and SQL connections for specific users and teams. The use of certain extraction packages can also be restricted.
SAP WebService: dab Nexus now also supports HTTP-based SAP connections using the Web Service / Process Integration formats.
Azure Managed Application: dab Nexus is now available as a Managed Application in the Microsoft Azure Marketplace, enabling you to deploy dab Nexus on Azure in minutes.
Bugfixes
- Fix UserExits not being saved for implicit BaseTables
- Fix the Shift+V shortcut for adding new virtual tables in Package Studio
- Fix a bug with the table search in Package Studio where search wouldn't work if the new search term was already part of the previous search term
- Cloning a task whose analytic group was deleted no longer pre-fills the analytic parameters
- Fix some analytic steps not properly appearing in Content Studio depending on the license
- Improve/fix validation of various form fields
- Fix Package Studio not cleanly differentiating between filters & tables, leading to issues if a filter and a table share the same name
- Prevent using a strategy other than "Discard" for virtual tables
- Fix workspace / team / analytic group assignments not being saved when creating a new user
- The visibility of the "Activies" button now only depends on the "Users can see activities" switch
- When cloning an Analytic Task, changing the Extraction Package / Analytic Group now updates the Third-Party Services as well (if applicable) to prevent non-existant tables breaking the Third-Party Service
- Fix editing a user leading to an unknown error
- Fix the "Ended" column in the run view not being filled properly
- The note "Output not included in license" now properly depends on the the license at the time the run was executed instead of the current license
- Fix an empty menu showing if the user did not have role "Custom Analytics Editor"
- Fixed an issue with the performance of the activity log causing long loading times or issues when saving changes
Further Changes
- "Content Suite" is now called "dab:AnalyticSuite (SQL)"
- Creating multiple custom analytics with the same output table names is now possible
- Support Packages now contain a Environment.txt file with detailed information about the dab Nexus installation
- The individual end dates for each licensed analytic step are now considered
- The number of records are now also shown for analytic tables, not just extracted tables
- The SAP system selection in the Package Studio now has a search bar
