Release Notes 1.18.x
Updated 1 week ago
by
Stephanie Krenz
Release Notes 1.18.964
Managed App Version: 1.18.964
Published: November 14, 2025
New Behavior for SAP System Slot Management
With this release, Nexus now respects the system slot configuration defined for each SAP system. This setting determines how many parallel connections are allowed for a specific SAP system configuration. By actively enforcing these limits, Nexus ensures that each SAP system will only run the maximum permitted number of concurrent connections. This prevents system overloads and leads to more stable processing.
Intelligent Run Handling Based on Available Slots
If not enough slots are available for a run, it will not start immediately and instead remains in the "Queued" status. The queue for each SAP system is processed sequentially.
Dynamic Slot Usage
A run may begin even if only a portion of its required slots is currently available. As more slots free up, Nexus automatically expands the run’s resource usage until it reaches the configured slot limit.
Automatic Slot Release
Reserved slots remain allocated until the run is either successfully completed or canceled. When a retry occurs, the run is placed back into the queue like any newly created or scheduled run.
Manual actions
If a run in the "Queued" status is manually canceled, Nexus immediately removes it from the queue and updates its status to "Canceled."
Unchanged Behavior for Individual Actions
Certain functions—such as Package Studio connections, SAP connection tests, or lookup parameters (e.g., company code)—continue to ignore slot settings and behave as before.
Pending State Indication
If a run is already in the “Running” state but still requires additional slots and thus maintains a queue position, this is represented as a pending state. This is indicated by the “Running” status together with a queue position greater than zero, visible per SAP system in the run view.
These enhancements promote controlled use of SAP system resources and help ensure more stable processing in highly parallelized environments.
Changes
The former “Re-Analyze” option is now called “Analyze Again”. It remains in the run view but is no longer shown as a standalone button and has been moved into the three-dot menu.
Fixes
- On the “Schedule & Status” page in the run view, schedules spanning daylight-saving transitions displayed incorrect UTC offsets. For example, schedules created in winter for summer months showed UTC +01:00 when UTC +02:00 would have been correct.
- Tables or aliases beginning with “/” caused ADLS replication to fail with an invalid URI error (Status 400, “The request URI is invalid”). This has been fixed by automatically replacing “/” with “_” in file names. [#272986]
- If a package contained a table not present in the selected SAP system, the extraction task failed even when “Skip Resolve Warning” was enabled. This has been corrected so that unresolved tables are now skipped as intended, and the task does not fail as a result. [#273042]
- The permission check for SQL users has been corrected. Permissions are now validated against the database used in the run instead of the master database. As a result, having db_owner on the target database is sufficient to execute the scripts, and the previous workaround of granting permissions on master is no longer required. [#273059]
Release Notes 1.18.892
Managed App Version: 1.18.892
Published: October 28, 2025
With version 1.18, dab Nexus significantly expands the capabilities of the Extraction and Replication task types. A single task can now combine data from multiple SAP systems and multiple extraction packages. In parallel, both the Task View and Run View have been redesigned to make complex task configurations easier to understand and manage.
New
Multi-SAP System Selection
Extraction and Replication tasks can now include multiple SAP systems. These are processed sequentially within a single run, eliminating the need for creating multiple tasks for similar extractions.
Multi-Extraction Package Selection
Tasks can now contain multiple extraction packages. dab Nexus automatically checks the compatibility of the selected packages and merges them into one combined package for execution. If a package cannot be merged, the user receives a clear error message explaining why. This feature enables use cases where certain tables only need to be extracted occasionally and can be included on demand.
Modernized SAP Interface
The internal SAP communication layer has been technically modernized. It controls how dab Nexus communicates with SAP and executes RFC calls. As part of this update, it may be necessary to update the SAP RFC libraries on the dab Nexus application server and review SAP authorizations. Further details are available in the Tech Notes for the new SAP Interface.
SAP Reports Export
The SAP Report Export has been completely redesigned. This ensures that more SAP reports are now compatible for export and that SAP reports targeting SQL destinations are delta-capable. dab Nexus also assigns more suitable data types to exported report data, based on the existing structure of the destination table when available.
Email Notifications
The authentication options for email notifications have been extended to include OAuth. This allows dab Nexus to support modern and secure authentication methods, especially for Microsoft 365 and Exchange environments.
Changes
Task & Run View
Both views have been fundamentally redesigned to better present complex information, especially for multi-SAP and multi-package tasks. A new Health Check feature verifies before execution whether all required resources (licenses, connections, analysis availability, etc.) are in place. This prevents failed runs due to missing prerequisites.
Monitor
The Monitor has been simplified and but still provides a cross-workspace overview of all tasks and runs the user has access to. Telemetry data such as data volume metrics and graphical displays have been removed since they provided little value and negatively impacted run performance, especially for real-time extractions.
Toast Messages
Notifications now appear uniformly in the lower right corner in a redesigned layout.
Other Adjustments
- Extracted record counts now use comma-based thousand separators.
- Task names in the Monitor are now fully displayed.
- For Replication tasks, target table deletion (for example in Snowflake) now occurs before the upload starts.
- The upload of Parquet files to Snowflake is now limited to 150 MB per file.
Managed App Specific
- The log warning "Unknown Proxy" has been resolved.
- A new "HTTPS only" option enforces automatic redirection from HTTP to HTTPS.
Bug Fixes
- When cloning tasks, certain values (for example, selected SQL database) were not carried over.
- Measuring data sizes (especially in Fabric) slowed down extractions and has been removed. [#272805]
- The workspace table view now supports horizontal scrolling.
- In Analytic Tasks, the parameter Exclude Intercompany was not correctly inherited from the Analytic Group.
- If a Custom Analytic used the same output table name as an Analytic Suite analysis, an error is now displayed when saving.
- Within Analytic Groups, filters using the same value but different conditions can now be created.
- Scheduled runs that became invalid due to configuration changes (for example, modified packages) are now correctly shown as failed.
- It was previously possible to schedule runs in the past due to time zone inconsistencies; this has been fixed.
- Issues launching the SAP GUI for SAP Report Export have been resolved.
- The Run Log can now once again be filtered by "Error". [#272651]
- In Package Studio, tables containing "/" in their names are now correctly displayed in the canvas. [#272685]
- A new validation check prevents users from selecting multiple analyses with the same output table name within an Analytic Group. [#272904]
