Changes in behavior
This topic describes behavior in Tungsten RPA 2025.2 that has changed from previous releases.
Design Studio changes
This topic describes Design Studio changes in behavior.
Project referencing changed
To support environments with multiple Management Consoles, in Design Studio Settings > Management Consoles, the "Use as Primary" option is removed. This means that Robots located in local projects can no longer use project scoped services provided by Management Console, such as Vault, Robot File System, TotalAgility, OAuth, Document Transformation Service, and Constants. In Design Studio, to execute Robots that use such services, place your Robots in the shared project.
In Basic Engine Robots, on the Lookup Password step, the "Project Name" property is removed.
Library protocol discontinued
You can no longer use the Tungsten RPA non-standard library protocol used to refer to a file in the robot library.
Modify your Robots to use the Robot File System instead.
Modify your Basic Engine Robots to get the files as input or place the files on a web server.
Create Robot Library File option removed
In Design Studio > My Projects > Local project context menu, the "Create Robot Library File" option is no longer available.
Nine-grid finder discontinued
The nine-grid finder is decommissioned.
Robot URL prefix renamed
The prefix for the robot URL used to open a robot file in Design Studio, changed from kofaxrpa: to tungstenrpa:.
Local desktop automation and Bundle step discontinued
Local desktop automation is removed.
In Robots, the Bundle step is no longer available.
Mail step discontinued
In Robots, the Mail step is discontinued. You can no longer run your existing robots that use this step. Use the Email step instead.
Browse step changes
The Browser option is removed. Robots created in older RPA versions require no further changes.
Calculate Key step changes
In Robots, the Variable property of the Calculate Key step changed its name to Record Value.
Execute SQL and Query Database step changes
For Stored Procedure Call > Input and Input/Output properties, the "Manual Parameter Details" option is renamed to Manual Parameter.
Convert Using JavaScript changes
In Basic Engine Robots, the Convert Using JavaScript converter no longer requires a semicolon at the end of the script.
Warnings changed to errors
In Robots, expressions consisting only of constants, now generate and display errors instead of warnings if these constants are evaluated as failing. This change in behavior ensures better robot building and prevents robots from execution on Management Console. Previously, it was possible to start execution of such a robot on Management Console and the robot would fail when the execution reached the step with a warning.
Heuristics for generating finders changed
Generation of finders in CEF is improved.
Improved animation detection in CEF
Guards now delay while the found object is affected by an animation on the web page (such as being shifted in or out).
Improved context menu
In the Recorder View, if the context menu contains a long list of variables, another "More" submenu appears.
Try-Catch step and finder analysis
Finder analysis determines which finders may exist at a given flow point in a robot. Also, it shows errors when a finder that cannot be guaranteed to exist at a given flow point, is used there. When a robot executes, it removes such finders from the state before proceeding to the next flow point.
Finder analysis did not work correctly with the finders after the Try-Catch step, and this issue has been resolved. However, this fix may affect some robots:
Some robots created in older RPA versions, if they are edited in this or newer version of RPA, may not run any more.
Some robots created in older RPA versions will still be able to run on RoboServer, if they are not edited in this or newer version of RPA.
The following is an example of a robot that did not have an error before the finder analysis fix, but has an error if edited and saved in RPA 2025.2.
The Press Key step uses a finder from the Extract Value step. The Extract Value step is actually a Guarded Choice step that contains Extract Value step. The Finally block removes the finder. If the extraction times out and no finder is added to the state by the Extract Value step, there is no guarantee that the finder exists after the Try-Catch block.
To fix the robot, move the steps following the Try-Catch step inside the Try-Catch block.
When execution reaches the Press Key step inside the Conditional step, we can be sure that the finder exists.
Save As dialog in CEF
Previously, when you saved a file in CEF using the Save As dialog, after selecting Save, the application tab was left open. After implementing the fix, the tab now closes automatically. This change may affect robots created in older RPA versions that have a step that closes the save dialog application tab.
Management Console changes
This topic describes Management Console changes in behavior.
CyberArk
OAuth
Password store
Password Store Client role renamed
Revoke tokens option removed
License
Add/edit password access for robot renamed
Auto-selected cluster in database mappings
Date and time added to logs
Email trigger for shared account
CyberArk
CyberArk is now integrated with the new Vault feature.
In Management Console > Settings, the "CyberArk configuration" section is renamed to CyberArk and the "CyberArk applications" section is removed. You can now configure your CyberArk applications on the Secrets tab located on the Target systems tab in Repository > Vault. Be aware that Secrets tab is hidden unless CyberArk is enabled.
OAuth
OAuth apps and users are migrated to the new Vault feature. Additionally, the following changes are made.
OAuth is removed from Robot Lifecycle Management. In Management Console > Admin > Projects > Repository, OAuth is removed from the list of the objects that can be synchronized.
"OAuth user" is renamed to OAuth clients.
Password store
Password store and passwords are migrated to the new Vault feature.
The "Move password entry" option previously available in Password store is removed. It is no longer possible to move password entries from one project to another.
Password Store Client role renamed
The "Password Store Client" role is renamed to Vault Client.
Revoke tokens option removed
In Management Console > Admin > Service authentication, the "Revoke tokens" option is no longer available.
License
The following values are now read-only and hidden behind asterisks if added using the configuration files:
Production license key
Non-Production license key
TotalAgility server URL
Add/edit password access for robot renamed
In Management Console > Repository > Robots, the "Add/edit password access for robot" context menu option is renamed to Modify robot access to Vault.
Auto-selected cluster in database mappings
In Management Console > Repository > Database mappings, when adding a database mapping, the cluster list is read-only and automatically contains the name of the cluster configured in the project, if in the related project, the Use only Service Cluster in project option is selected.
Date and time added to logs
On Tomcat, events from Management Console are now logged in with date and time by default.
Email trigger for shared account
It is now possible to set up email triggers to the Microsoft 365 shared account using IMAP with the user name in the format such as user@maindomain.com\shared-mailbox.
RoboServer changes
This topic describes RoboServer changes in behavior.
Options discontinued
In RoboServer Settings, on the Security tab, the following options are no longer available:
Allow File System and Command Line Access
In Docker, the ROBOSERVER_SEC_ALLOW_FILE_SYSTEM_ACCESS environment variable is removed.
User configuration
In RoboServer Settings, the "Project" tab is no longer available.
Shut down RoboServer
In <Tungsten RPA installation>/bin folder, the ShutDownRoboServer.exe file is removed.
To shut down RoboServer, navigate to Management Console > Admin > RoboServers and from the RoboServer context menu, select Stop RoboServer.
API changes
The following changes affect the APIs.
Legacy APIs discontinued
Legacy Java and .NET APIs are no longer available for use in this and future versions.
.NET deprecated constructs discontinued
The .NET deprecated constructs are no longer available for use in this and future versions.
New Java API in Kapplets
Kapplets now use the new Java API. A proxy connection is no longer supported.
Swagger UI discontinued
For the Management Console REST services, Swagger UI is no longer supported.
To create a REST API client application that works with the Management Console REST API, the Management Console now provides an endpoint for downloading the JSON API specification file.
Download and import the JSON API file into the API explorer using the URL path with the following syntax:
protocol://<host>:<port>/<context-path>/api/mc/api-docs
We recommend to use Postman, where the specification file can be imported.
The API is subject to change. With each Tungsten RPA release, you may need to adjust customized programming for the REST API.
Java API and .NET API documentation folders renamed
The robosuite-dotnet-api and robosuite-java-api documentation folders are renamed to rpa-api-dotnet and rpa-api-java, respectively.
Import projects
In Management Console, when importing projects using API, the system now returns an error if the import fails.
KCU cost of robots
The KCU cost of Robots is adjusted to align with Basic Engine Robots.
Added 10,000 point cost to these application steps:
Browse
Windows
Excel
Terminal
Document Transformation
PDF
Email
Open (deprecated)
Custom Action
The looping-step cost is reduced from 5,000 to 1 point-per-iteration.
If a robot connects to one or more Desktop Automation Services, it costs 10,000 points in the beginning.
For Basic Engine Robots, the KCU cost of the Call Robot action step is removed.
Naming and database collation rules
Robots and folders with the same name are no longer supported.
Consider the following guidelines when creating names in Management Console and Design Studio.
Names must be unique and cannot be duplicated, even if the case is different but the name is the same.
During backup, restore, and import operations, case is not considered, resulting in errors for duplicate names with different case letters such as "a.robot" and "A.robot." Duplicate names are not allowed, including robots, snippets, types, resources, and database mapping names. Duplicate names in parent folders are not allowed, including robots, snippets, types, resources, and database mapping names.
Important tips for collation:
If you are creating a new database and not restoring from backups, use case-insensitive collation.
If you are restoring backups from a database that used case-sensitive collation for database tables, the target database must use case-sensitive collation. Otherwise, the restore process may cause errors or unexpected results.
Permissions in roles.xml
This topic describes changes to permissions in the roles.xml file.
Changes to passwordStoreTabPermissions property
The passwordStoreTabPermissions property is renamed to vaultTabPermissions.
The view and modify permissions are renamed to viewTargetSystems and modifyTargetSystems accordingly.
The following permissions are added:
viewSecrets
modifySecrets
extractSecrets
viewOAuthClients
modifyOAuthClients
extractOAuthTokens
viewRobotAccess
modifyRobotAccess
OAuthTabPermissions property removed
The OAuthTabPermissions property and its related OAuthTab permission is removed.
Permissions in clustersAndSettingsTabPermissions property
The changeCyberArkSettings permission is renamed to modifyCyberArkConfiguration.
The viewCyberArkConfiguration is added.
The canManageHANodes and canViewDBTypes permissions are removed.
The canManageClusters permission is added.
ktaConfigurationPermissions property renamed
The ktaConfigurationPermissions property is renamed to totalAgilityPermissions.
messageOfTheDayPermissions property renamed
The messageOfTheDayPermissions property is renamed to messageOfDayPermissions.
constantsTabPermissions property added
The constantsTabPermissions property and its related modifyConstants permission are added.
TotalAgility acronym replaced
In Tungsten RPA, the KTA acronym is replaced with TotalAgility.
In Design Studio
In Robots, the "KTA" step is renamed to TotalAgility step. Also the "KTA Server" property is now TotalAgility Server.
In Management Console
In Management Console, the following "KTA" instances are replaced:
Admin > Service authentication, the "KTA" client name is renamed to TotalAgility.
In Admin > Projects > Permissions, "KTA Client" role is renamed to TotalAgility Client.
In Admin > License > License server, "KTA server URL" is renamed to TotalAgility server URL.
In Settings, the "KTA configurations" section is renamed to TotalAgility.
In configuration files
In Configuration.xml, the following updates are performed to the properties:
ktaServerUrl is renamed to totalAgilityServerUrl
ktaSharedSecret is renamed to totalAgilitySharedSecret
In Docker, the following updates are performed to the environment variables:
CONFIG_LICENSESERVER_KTASERVERURL is renamed to CONFIG_LICENSESERVER_TOTALAGILITY_URL
SERVICE_AUTHENTICATION_KTA_SHARED_SECRET is renamed to SERVICE_AUTHENTICATION_TOTALAGILITY_SHARED_SECRET
SERVICE_AUTHENTICATION_KTA_SHARED_SECRET_FILE is renamed to SERVICE_AUTHENTICATION_TOTALAGILITY_SHARED_SECRET_FILE
General changes
This topic lists general changes in behavior.
SSH implementation updated
The SSH implementation in the terminal drivers is updated and supports newer SSH features. This can result in the driver negotiating more secure protocols with the server. The driver might show a different, more secure server fingerprint during connection. This change may require robots to be updated if they validate the fingerprint and/or may require a cached copy of the host key to be updated.
Configurator.jar discontinued
Configurator.jar is removed and no longer available.
SMBv1 protocol obsolete
Robot File System does not support SMBv1 protocol.
ConfigureRSUser and ConfigureMC discontinued
Executable files ConfigureRSUser.exe and ConfigureMC.exe, as well as configuration files ConfigureRSUser.conf and ConfigureMC.conf are removed.
SSLv3 protocol obsolete
SSLv3 protocol is no longer supported.
Tungsten RPA 2025.2
© 2025 Tromba Technologies, Inc.