Today, we’ve published a new release of TimeXtender Orchestration & Data Quality that contains the changes listed below.
New
- Added support for setting the number of times a failed package should retry.
- New schedule type - ‘Continuous’ - that starts a new execution right after previous execution finishes
Improved
- Redesigned the start page and fixed a bug where buttons/links did not always work.
- Improved user experience and execution for Data Transfer merge.
- Added clearer error messages for the execution of Azure package types.
- Improved an error message shown when running an invalid Data Factory package.
- Removed the Subscription field from the Power BI Refresh package type UI, as it is no longer required.
- Web URLs have been updated to use ‘timextender’ instead of ‘exmon’ (i.e., https://dev.odq.timextender.dev/cmdservice/ExpectusCommandService.svc).
- In the Gateway desktop client, some paths in ‘ExmonClientConfig’ file is changed to ‘timextender’ (from ‘exmon’) during service startup.
- Increased the length of the data fields in Azure Data Providers so that Tenant Ids and App Ids will be fully visible
- The flow for sending emails from ODQ has been simplified.
- The default timeout for TDI package type is 6 hours and is now properly indicated in the TDI package UI in the Desktop client.
Fixed
- Fixed a bug where compare query previews sometimes showed the wrong number of variance errors.
- Fixed bug in the Initializing database step in On-Premise install
- Fixed bug where upgrading the Command Service failed when upgrading On-Premise
- Fixed an issue where Schedule Groups would show an incorrect icon for the Databricks package type
- Fixed an issue where Active Directory queries in ORC would not work if they returned 0 rows
- Fixed an issue where Azure Function packages would not check for the validity of credentials before starting execution
- Fixed an issue with the duplication and renaming of packages
- Fixed an issue with the duplication of Ingest packages
- Fixed an issue with VM names disappearing and not being saved in Cloud Optimization packages
- Fixed an issue where trying to create a Fabric package without any Fabric Data Providers present resulted in an "index out of range" error
- Fixed an issue with saving Properties changes in packages
- Improved error messages when Azure packages fail without any further information about the problem being sent from Azure
- In ODQ Portal, the ETA in the process popup now handles time zone differences between local machine and time zone setting in ODQ Desktop.
- Most unit tests (149) fixed (12 still failing).
- Fixed an issue where images were not displayed correctly in emails
- Fixed an issue where pressing sync for TDI Data provider in Turnkey would timeout
- Better error message when there is an issue finding Entra Groups
- Fixed an issue where TDI packages would not sync correctly to object groups
- Fixed an issue with creating Entra groups and new users in ODQ Desktop
- Fixed an issue where execution of Databricks packages would not work
- Fixed an issue with duplication of Azure Cloud Optimizer packages where the Capacity option would be disabled in the duplicated package
- Fixed issue for Gateway trying to log control characters like esc via xml serialization.