Added a new workflow action to clone a container environment (req. Virtualize)
Show amount of rows affected of executed queries inside logging
Fixed DB2 z/OS connection issue using direct connection
Fixed issue when runtime agent is closed prematurely
Fixed UI issue in upgrade screen
Fixed issue when dropping tables giving warning (Postgres)
Fixed issue when trying to run Runtime on different ports
Fixed missing logging issue
Fixed issue finishing the run too early
Note: versions 4.8.2 to 4.8.4 are internal releases not released to end-users.
Date
Version
4.8.1
Description
This release contains a bugfix
Fixed an issue in which application names with white-spaces can cause the Runtime UI to load incorrectly in some edge-cases
Date
Version
4.8.0
Description
This release contains improvements, bugfixes and the introduction of database virtualization
Added global environment search to quickly find the right environment
Improved logging of executed sql commands
Fixed "No run data available" message
Fixed transaction management for DB2i to prevent journaling issues
Introducing database virtualization We are excited to unveil a new approach to managing and controling test data with the latest release, fully integrated within DATPROF Runtime. This innovation enables testers and developers to quickly clone or branch their test and development databases without requiring extra storage. Through the use of snapshots, it is now feasible to timetravel not just the test data, but the database's structure as well. Creating and restoring snapshots is incredibly fast, completed in just seconds without requiring extra storage space. This efficiency makes it an powerfull tool for running automated tests or making significant changes within your database.
To utilize DATPROF Virtualize within Runtime, a specific license key is necessary. For information on license options, please reach out to sales@datprof.com.
Date
Version
4.7.3
Description
This release includes a security fix:
Upgraded encryption method for storing database passwords to AES-256. Existing passwords will be upgraded during starting up Runtime.
Date
Version
4.7.2
Description
This release includes bugfixes: • Fixed an issue testing an unsaved trigger • Fixed an issue with JWT error token poluting the runtime-service.log • Fixed an issue with SQL Server Integrated/Windows authentication • Updated Velocity dependency
Date
Version
4.7.1
Description
This release is an internal release not published for customer usage.
Date
Unreleased
Version
4.7.0
Description
This release includes the following new features and bugfixes:
Expanded the SQL module to accept multiple statements within a single template
Improved formatting SQL queries generated by velocity templates
Enforce default password complexity for new passwords (see documentation)
Added account locking when wrong password is entered 5 times in a row
Date
Version
4.6.0
Description
This release includes the following new features and bugfixes:
IBM DB2 z/OS (Mainframe) support has been added to prepare for upcoming Privacy / Subset releases
Added an option to forcefully abort a run
Improved service and agent communication
Fixed an issue when the group menu was not always loaded
Date
Version
4.5.1
Description
This release includes the following new features and bugfixes:
Resolved an issue where certain scenarios were missing within the Workflow.
Resolved the problem where the scenario was being reset within the Workflow.
Addressed the redirect problem that occurred after the run was completed.
Fixed the unresponsive behavior of the abort/pause/retry functionality.
Rectified the graphical issue where the start node of the workflow was not rendered correctly.
Date
Version
4.5.0
Description
This release includes the following new features and bugfixes:
Synchronization of LDAP user groups is now possible. Please read the comment below for more information.
The LDAP implementation has been improved to support various LDAP servers, providing greater flexibility and compatibility.
A "Download run data" button has been added to the run history for added convenience.
An issue where upgrading the application did not update the schema mapping has been fixed.
The Workflow email module now supports username/password authentication.
Trigger email issues have been resolved for a smoother experience.
LDAP Upgrade Notice: With the new enhancements to our LDAP implementation and the added capability of synchronizing LDAP user groups, the configuration process has changed, making automatic upgrades impossible. After upgrading to Runtime 4.5, the synchronization interval will automatically be set to 0 to prevent synchronization with a potentially invalid LDAP configuration. As a result, attempting to log in with LDAP credentials could lead to errors, depending on the configuration.
To ensure a smooth experience, we recommend logging in with the local Runtime administrator and verify the LDAP configuration. Once the configuration has been updated, you can reset the synchronization interval to your preferred duration, in which the Runtime service should synchronize with the LDAP directory.
Thank you for your attention, and please feel free to contact our support team if you have any questions or concerns.
Date
Version
4.4.2
Description
This update features a few bug-fixes
Fixed a permission issue when migrating from before Runtime 4.4.x to 4.4.x where users had no permissions
Fixed an issue in which certain LDAP users could not login
Fixed a concurrent modification error while Retrieving identity column action
Date
Version
4.4.1
Description
Runtime Permission Hotfix
Fixed an issue of receiving a 'forbidden' message when attempting to view run details despite having proper permissions granted at the group or environment level.
Date
Version
4.4.0
Description
New User management
New User Management system introduced, allowing users to create more verbose authorization setups
API keys can now be bound to specific users
Other improvement and bug-fixes
Runtime agents are now started and stopped automatically when required. There is no need to add/start agents anymore.
Added option to duplicate a Workflow
Fixed issue with Windows Authentication when environment is created using the API
Deprecated API As a part of Runtime´s version 4.4 release, we´ll be removing a few deprecated API functions in order to improve the user experience and stability of our REST API. This can impact existing Runtime automation scripts that rely on sending commands through the API, but as these functions have been deprecated for more than a year now, we suspect the impact of this change will be minimal. Nevertheless, in the following article is an overview of removed functions and their alternatives, should you have to partially rework your scripts. https://docs.datprof.com/knowledgebase/api-commands-deprecated-in-runtime-4-4
Date
Version
4.3.1
Description
Fixed small Workflow user interface issues
Fixed format issues in API documentation
Fixed writing errors multiple times inside log file
Date
Version
4.3.0
Description
Introducing 'Workflow' After months of development we are very excited to introduce our new Workflow module inside DATPROF Runtime.
Workflow is a powerful module-based automation tool that allows testers and developers to combine Runtime’s ability to provision test data with the option to execute proprietary software, use powerful PowerShell scripts, execute SQL scripts, send emails, alongside other modules.
Why use Workflow? In the test data generation/subsetting/masking pipelines there are usually many processes that happen before or after test data is created. Think of an e-mail being sent out to testers notifying them that their environment is ready to be used, or the renaming and storage of audit files for later reference by a security officer. Workflow is intended to give you the tools to perform a multitude of tasks to further automate the workflow of administrators and testers alike.
Workflow comes with an easy the use drag and drop canvas style editor in which users can easily connect different kinds of modules and link them to each other. Many of the workflow modules have output properties that can be used directly in other modules.
Date
Version
4.2.5
Description
Fixed issue with LDAP authentication
Fixed issues when using seedfiles for masking and generation
Fixed wrong icon and progress text on details of running run.
Improved error handling when websockets connection could not be established
Fixed issue where no error is shown when an agent fails to start
Added parser for SQL Server custom connection strings
Added extra JDBC properties for MySQL for improved performance
Date
Version
4.2.3
Description
Fixed "Remember me next time" issue
Fixed issue saving LDAP config
Fixed issue with template processes not able to use velocity parameters
Date
Version
4.2.2
Description
Upgraded Spring Dependencies to Spring Boot 2.5.12 and Spring Framework 5.3.18
Date
Version
4.2.1
Description
Fixed issue in which you could not delete an application
Fixed UI alignment issue
Date
Version
4.2.0
Description
LDAP configuration can be configured using the webinterface
Faster retrieving of applications
API keys are now sorted alphabetically
Installations are now sorted alphabetically
Username and password are now seperated from Custom JDBC string
Date
DATPROF Runtime 4
DATPROF Runtime 4 offers a complete renewed user interface with some great new features. Managing, executing and automating different Subset, Privacy, Generation applications for different database is easier than ever. This major release bring some changes to the license model. However, for existing customers with a valid Runtime license, this will be a free upgrade! Please contact your sales@datprof.com to find our more about the changes.
Single environment - Multi installations One of most requested features was the ability to install multiple applications inside a single environment. For example if you have multiple Subset applications and also a Privacy application that you want to deploy on the same target database, you don't have to create multiple environments anymore. This greatly reduces the amount of environment that you have to manage
New dashboard We've added a complete new dashboard view in which administrators and self service users can monitor environments that are executing applications. Also from this dashboard you have a new method to start a new run. Just pick the right environment, installed application and scenario you want to execute and click the Start run button. You will return to the dashboard to monitor this run.
Applications In previous versions applications were uploaded under a Project and could only be installed inside an environment that was within the same project. In Runtime 4 applications are moved to a higher level central repository that can be used in all of the environments. Also the terminology of Project has changed to prevent some confusion. Projects are now called Groups and can be used to cluster your environments to find them more easily. Applications are now visually identifiable as a Subset, Privacy or Integrate application by using the icon throughout the Runtime 4 portal.
Improved installation When installing an application you sometime have to change certain parameters like schema mapping or the database link. With Runtime 4 you can now directly change this during the installation instead of making it consistent after installing. Off course you still have the option to change this settings later on.
Dropped support for Internet Explorer 11 Unfortunately Runtime 4 offers no support for Internet Explorer anymore. The successor of Internet Explorer - Edge has been introduced in 2015 and has been actively developed. Most computers already have a modern secure browser installed, if not; install Edge, Chrome, Brave or Firefox.
Backward compatibility Runtime 4 is completely backwards compatible with Runtime 3.x installations. Just upgrade like you have done before and make a backup of your Runtime Home data folder before upgrading. For information about upgrading Runtime, we refer to the upgrade documentation ( https://docs.datprof.com/runtime/latest/runtime-installation/upgrade-instructions).
JavaScript errors detected
Please note, these errors can depend on your browser setup.
If this problem persists, please contact our support.
