Release Notes 8.1.0.0
(Released July 2026)
Overview
The purpose of this document is to outline the changes introduced in Resolve Actions Pro 8.1.0.0. Review these release notes before installing, upgrading, or deploying the platform.
Version 8.1.0.0 focuses on platform modernization, with upgrades across the runtime and dependency stack to current, supported Jakarta EE-based technologies. As part of this effort, legacy end-of-life components have been replaced, and the platform has transitioned from the javax.* namespace to jakarta.*.
This release also introduces the new Dynamic MCP module, which enables Actions Pro runbooks to be exposed as tools for AI agents using the Model Context Protocol (MCP). In addition, this release includes new features, usability improvements, platform enhancements, and numerous bug fixes.
Action Required for Existing Customers
Important: Version 8.1.0.0 introduces breaking changes for customer-developed content.
Actions Pro is an extensible platform that allows customers to develop custom components, including Groovy scripts, Action Tasks, SDK gateways, and third-party library integrations. Because the platform has been upgraded from the legacy Java EE (javax.*) namespace to Jakarta EE (jakarta.*), and from Java 11 / Groovy 2.5 to Java 21 / Groovy 4, existing custom code may require updates before upgrading to version 8.1.0.0.
Review and update the following customizations before or during your upgrade.
Update javax.* Imports
Any Groovy scripts, Action Tasks, or custom code that imports Java EE packages must be updated to use the corresponding Jakarta EE packages.
| Previous Package | Updated Package |
|---|---|
javax.mail.* | jakarta.mail.* |
javax.servlet.* | jakarta.servlet.* |
javax.persistence.* | jakarta.persistence.* |
javax.validation.* | jakarta.validation.* |
javax.annotation.* | jakarta.annotation.* |
javax.xml.bind.* | jakarta.xml.bind.* |
javax.jms.* | jakarta.jms.* |
javax.xml.ws.* | jakarta.xml.ws.* |
javax.xml.soap.* | jakarta.xml.soap.* |
Note: Core Java SE packages such as
javax.crypto,javax.net,javax.sql, andjavax.namingare not affected and do not require any changes.
Validate Groovy Scripts and Java Libraries
Retest all custom Groovy scripts against the Groovy 4 runtime.
If your deployment includes custom or third-party JAR files, verify that they are compatible with Java 21. Libraries compiled specifically for Java 8 or Java 11, or those that depend on the legacy javax.* APIs, may need to be upgraded to Jakarta-compatible versions.
Rebuild Custom SDK Gateways
Custom SDK gateways developed using the 3.x SDK must be rebuilt using the 4.0 SDK included with this release.
Review Code That Uses Upgraded Libraries
If your custom code interacts directly with platform libraries, review it for compatibility with the updated APIs. This includes libraries such as:
- Apache HttpClient 5.x
- Elasticsearch Java Client 8.19
- Hibernate 6.x
These libraries include API changes that may require updates to existing custom code.
Recommended Upgrade Process
Before upgrading to Actions Pro 8.1.0.0, we recommend the following:
- Inventory all custom Groovy scripts, Action Tasks, SDK gateways, and third-party libraries. Identify any
javax.*imports or references to older library versions that require updating. - Migrate and validate all customizations in a non-production environment running Actions Pro 8.1.0.0 before upgrading your production environment.
- Back up any customized Groovy Sandbox configuration files before upgrading. During the upgrade, the following files are replaced with the default 8.1.0.0 versions and any customizations must be reapplied and validated against the Groovy 4 runtime:
groovy_whitelist.propertiesgroovy_blacklist.propertiesgroovy_sandbox.properties
What's New
Platform Modernization
Java 21
Actions Pro now requires Java 21, replacing the previous Java 11 runtime.
Jakarta EE 10
The platform has been migrated from the legacy(javax.*) namespace to Jakarta EE (jakarta.*). This change affects customer-developed code that imports Java EE packages. See Action Required for Existing Customers** for migration guidance.
Spring Boot 3.5 and Spring Framework 6
The platform has been upgraded to the latest Spring framework components.
| Component | New Version |
|---|---|
| Spring Boot | 3.5.7 |
| Spring Framework | 6.2.1 |
| Spring Security | 6.4.2 |
| Spring Data | 3.4.1 |
| Spring Vault | 3.1.2 |
| Apache HttpClient | 5.4.1 |
| Apache HttpCore | 5.3.1 |
Hibernate 6
Hibernate has been upgraded to the latest supported versions.
| Component | New Version |
|---|---|
| Hibernate ORM | 6.4.10.Final |
| Hibernate Validator | 8.0.1.Final |
Elastic Stack 8.19
The Elastic Stack has been upgraded to version 8.19.6.
| Component | New Version |
|---|---|
| Elasticsearch | 8.19.6 |
| Kibana | 8.19.6 |
| Logstash | 8.19.6 |
The legacy Elasticsearch High-Level REST Client has also been replaced with the Elasticsearch Java Client 8.19.6.
Jetty 12 and Tomcat 11
The embedded and standalone web containers have been upgraded to support Jakarta EE 10 and Servlet 6.0.
| Component | New Version |
|---|---|
| Jetty | 12.0.36 |
| Apache Tomcat (RSView) | 11.0.4 |
Groovy 4
The platform now uses Groovy 4.0.14, replacing Groovy 2.5.21.
Action Tasks and gateway scripts now run on the Groovy 4 runtime.
RabbitMQ 4.2
RabbitMQ has been upgraded from 3.8.3 to 4.2.1.
This release also includes an updated Erlang/OTP runtime, which requires OpenSSL 3.x on Linux hosts. For more information, see Infrastructure Upgrade.
SDK Gateways 4.0
All bundled SDK gateways have been rebuilt using the 4.0 SDK and are fully compatible with the updated platform runtime.
Dynamic MCP Server
Version 8.1.0.0 introduces Dynamic MCP, a new feature that enables administrators to create and manage one or more Model Context Protocol (MCP) server endpoints directly within Actions Pro.
Each MCP endpoint can be configured to expose selected Runbooks as executable skills, allowing MCP-compatible AI agents, such as Claude, to discover and invoke them. This allows Runbooks to be used as AI tools while continuing to leverage Actions Pro authentication and access controls.
Unlike the standalone, containerized MCP server available in previous releases, Dynamic MCP is built directly into Actions Pro. MCP endpoints can be created, configured, and managed from within the platform, eliminating the need for a separate deployment.
Infrastructure Upgrade
Version 8.1.0.0 introduces infrastructure requirements as part of the platform modernization effort.
Java 21 Runtime Required
All Actions Pro components now target Java 21. Hosts and containers must provide a compatible Java 21 JRE. Temurin 21 is the reference runtime.
OpenSSL 3.x Required for RabbitMQ
RabbitMQ 4.2.x uses a newer Erlang/OTP runtime that requires OpenSSL 3.x.
Hosts running the embedded or bundled RabbitMQ service must have OpenSSL 3.x available. Operating systems based on RHEL 7 / CentOS 7 with OpenSSL 1.0.x or 1.1.x are no longer supported for the message broker.
Elasticsearch 8.x Upgrade Considerations
The Elastic Stack has been upgraded from 7.17 to 8.19. Before upgrading, review Elasticsearch cluster and data compatibility requirements.
The Elasticsearch 8.x release includes changes to index compatibility, security settings, and keystore defaults compared to the 7.x release.
Tomcat 11 (Servlet 6.0)
RSView now runs on Apache Tomcat 11 with Jakarta EE 10 / Servlet 6.0 support.
Any custom Tomcat configuration should be reviewed and validated for compatibility with Tomcat 11.
Update Support
The following upgrade paths are supported:
- Actions Pro versions 7.7 and later can be upgraded directly to Actions Pro 8.1.0.0.
User Security
This release has been evaluated against the OWASP Top 10 security flaws using Veracode. The detailed scan report will be available on request.
Software Composition
The following table lists the major platform components updated in Actions Pro 8.1.0.0.
| Component | Version (8.1.0.0) | Previous Version |
|---|---|---|
| Java (OpenJDK / Temurin) | 21 | 11 |
| Spring Boot | 3.5.7 | 2.7.14 |
| Spring Framework | 6.2.1 | 5.x |
| Spring Security | 6.4.2 | 5.x |
| Spring Data | 3.4.1 | 2.x |
| Spring Vault Core | 3.1.2 | 2.3.4 |
| Hibernate ORM | 6.4.10.Final | 5.4.33.Final |
| Hibernate Validator | 8.0.1.Final | 8.0.0.Alpha3 |
| Hibernate Commons Annotations | 6.0.6.Final | 5.1.2.Final |
| Jakarta EE Namespace | EE 10 (jakarta.*) | EE 8 (javax.*) |
| Jakarta Servlet API | 6.0.0 | Javax Servlet |
| Jakarta Persistence API | 3.1.0 | 2.2.3 |
| Jakarta Validation API | 3.0.2 | 2.0.2 |
| Jakarta XML Bind API | 4.0.2 | 2.3.2 |
| Apache Tomcat (Standalone RSView) | 11.0.4 | 9.0.102 |
| Jetty (Embedded) | 12.0.36 | 9.4.52 |
| Elasticsearch | 8.19.6 | 7.17.28 |
| Kibana | 8.19.6 | 7.17.28 |
| Logstash | 8.19.6 | 7.17.28 |
| Elasticsearch Java Client | 8.19.6 (co.elastic.clients) | REST High-Level Client 7.17.28 |
| RabbitMQ (Linux) | 4.2.1 | 3.8.3 |
| RabbitMQ (Container) | 4.1.6-management-alpine | 3.8-management-alpine |
| Groovy | 4.0.14 | 2.5.21 |
| Apache HttpClient | 5.4.1 | 4.x |
| Apache HttpCore | 5.3.1 | 4.x |
| Jackson | 2.18.6 | 2.18.3 |
| docx4j | 11.5.13 (core + JAXB Reference Implementation) | 3.3.2 |
| ehcache | 3.11.1 (Jakarta) | 3.10.8 |
| Axis2 / Axiom | 2.0.0 (Jakarta) | 1.8.0 / 1.3.0 |
| OWASP CSRFGuard | 4.3.0-jakarta | 3.1.0 |
| Apache Commons FileUpload | 2.x (jakarta-servlet6) | 1.5 |
| Kafka Connect API | 4.1.1 | 0.11.0.0 |
| React | 18.3.1 | 18.2.0 |
| Vue | 2.7.16 | 2.6.14 |
| SDK Gateways | 4.0 | 3.x |
Known Issues and Upgrade Notes
HashiCorp Vault Integration
Full Vault-backed secret management is not included in Actions Pro 8.1.0.0.