Release Notes 8.1.0
(Released June 2026)
Overview
This release of Resolve Actions Pro introduces a Dynamic MCP server, usability improvements, security improvements, and a tech stack upgrade.
Dynamic MCP Server
Users can now dynamically create MCP servers that expose selected Runbooks as tools. Authentication can be configured directly within the MCP server, and invocation details are automatically generated for use with agents and external integrations.
Usability Improvements
- Adds the ability to exclude Runbooks from job schedule export scans.
- Adds the option to export Gateway filters without including the assigned automation.
- Adds support for uploading CSV files to Custom Tables.
- Adds the ability to clear the content of SSH Gateway connections.
- Introduces GraalPy support in the Actions Pro 8.x RSControl and RSRemote Docker images.
- Adds support for Kafka 4.1.1.
Security Improvements
- Fixes an issue with password visualization in the result screen.
New Features and Functionality
- Updates Log4j libraries to version 2.25.3.
- Updates GitHub Actions workflow to build all Actions Pro artifacts.
- Updates Helm Charts with the latest
docker-compose.ymlconfiguration. - Updates tika-core JAR to version 3.2.3.
- Updates RabbitMQ to version 4.2.1 and Erlang to version 27.3.4.6.
- Introduces GraalPy to Pro version 8.x RSControl and RSRemote Docker images.
- Upgrades ELK stack to version 8.19.
- Adds
resolve_useras a default to theRS.actiontask.PropertyDefinitionsapplication security setting. - Upgrades Spring library to version 6.x.
Resolved Issues
The following issues have been resolved with this Actions Pro version.
| Ticket | Summary |
|---|---|
| 49029 | Fixed issue where the RESULT output was incorrectly populated in the RAW section of worksheets. |
| 53638 | Fixed issue where form dropdowns displayed incorrectly on initial load in preview mode and wiki pages. |
| 8451 | Fixed issue where ActionTasks reverted to previous versions when edited. |
| 8347 | Fixed issue where ActionTasks with images rendered with errors in Automation Designer. |
| 4918 | Fixed issue where passwords were exposed during Runbook execution. |
| 4857 | Fixed issue where Embedded Python ASEESS ActionTasks retained environment variables and module-level state across executions within the same session. |
| 5825 | Fixed issue where RSMgmt alert email functionality stopped working. |
| 8309 | Fixed issue in Gateway Builder Pull Script templates where RS_LAST_* values were not properly initialized and error handling/logging in the initial try block was incomplete. |
| 8307 | Fixed issue where exporting Gateway filters automatically included the assigned automation. |
| 8336 | Adds a method to clear content from an SSH (or Telnet) gateway connection. |
| N/A | Fixed issue where updating the standalone Windows version of RSRemote from 7.9.0.6 to 8.1 failed. |
| N/A | Upgraded Jackson libraries from 2.18.3 to 2.18.6. |
| N/A | Fixed issue where the List Log Files API returned a 500 error. |
| N/A | Fixed issue where the BASH ActionTask did not work with the ${INPUTFILE} command. |
| N/A | Fixed issue where users could delete active worksheets. |
| N/A | Fixed issue where the Page Model component returned an HTTP 400 Bad Request error. |
| N/A | Fixed issue where users who logged in using a password reset link were redirected to a "Page Not Found" error page. |
| N/A | Fixed issue with the Kafka Gateway where creating a new gateway generated an error. |
| N/A | Fixed issue with the Splunk Gateway where newly added filter fields were not displayed. |
| N/A | Fixed issue when importing data into new custom tables. |
| N/A | Fixed issue where an exception occurred when the system automatically executed the System.RSControlHealthCheck runbook. |
| N/A | Fixed issue where one of the selected automations was not copied during a bulk copy operation to a new namespace. |
| N/A | Fixed issue where an exception occurred when adding or removing user roles. |
| N/A | Fixed issue where users logging in with a password reset received an HTTP 403 Forbidden response. |
| N/A | Fixed issue where Logstash did not start after upgrading to version 8.1.0. |