Skip to main content
Version: Release SaaS

September 2026

Version: 27.1.0-907.1100

AI Features​

AI Assistant​

important

Ask Release is now called AI Assistant. The feature and the way you use it are unchanged.

AI Assistant now routes each conversation to an agent tuned for a specific kind of question. You select the agent when you start a chat, and the conversation stays with it for its life. To ask a different kind of question, start a new chat and select another agent. The following agents are available:

  • Generic Agent: the default agent for general questions about your Release data, such as release status, tasks, templates, folders, variables, and configurations.
  • Reporting Agent: answers data questions with charts and tables, and can add results to a custom dashboard.
  • Knowledge Base Agent: answers how-to questions about working with Release and its integrations.
note

The Reporting Agent is a Tech Preview feature. It is available for evaluation and is subject to continuous improvement.

AI Assistant also includes Task Troubleshooting, which explains why a task failed. You launch it from the failed task's Explain error button in the task drawer rather than from the agent selector.

The agents you see depend on your permissions. Every agent respects your Release permissions, and results include only data you are authorized to view.

For more information, see:

Demo Templates​

The Digital.ai demo folder now contains six demo templates, grouped into the Agentic Automation, Enterprise Delivery Orchestration, and Mobile Banking Delivery subfolders.

Five templates are new in this release. They cover MCP-powered insights, agentic release automation, a conversational AI task, end-to-end delivery orchestration, and auto-triggered cross-team epic delivery.

The existing mobile banking template is now named Mobile Banking Release Orchestration, and it adds MCP and AI tasks alongside Slack notifications.

For more information, see Release SaaS - Demo Templates.

Deployment Visibility and Versioning​

Live Deployments​

Live Deployment Cards​

Live Deployments page usability has been improved so each deployment card shows the most essential information, cards are shorter and easier to scan, and additional details are shown on hover.

For more information, see Live Deployments in Release.

Folder-Level Applications and Environments​

The View Live deployments and Edit Live deployments folder permissions now also apply to the Applications and Environments pages in a folder. No new permissions were added.

For more information, see Folder Teams and Permissions.

Connections and Variables​

Connections​

Connection Deletion​

Completed and aborted releases no longer prevent a referenced connection from being deleted. A connection can be deleted as long as it is not referenced by an active release, trigger, or other active configuration.

For more information, see When a Connection Cannot Be Deleted.

Connection Title Check​

When creating or editing a connection, Release now warns if another connection of the same type already uses that title. This makes connections easier to tell apart when selecting one in a task. The warning is informational, and the connection can still be saved. Global connections are checked against other global connections. Folder-level connections are checked across the folder hierarchy, including parent folders and subfolders.

For more information, see Duplicate Connection Title Check.

Variable Enhancements​

Variable List Improvements​

The variable search now indicates when a filter is applied, and a variable counter reflects the filtered results. The list header stays fixed while you scroll, which helps with long variable lists.

On a release variable list, the release and folder variable toggle displays total variable counts. These totals do not change when a filter is applied.

For more information, see Searching Release Variables.

Working with Releases​

UI and Functional Enhancements​

My Tasks Tile​

The Home page now includes a My tasks tile that lists the tasks assigned to you, such as tasks in the In progress, Pending, or Failed status. Tasks are sorted by due date, so the ones due soonest appear first. Each row shows the task name, the release and phase the task belongs to, the task status, and the due date.

For more information, see My Tasks Tile.

Run As Password Variables Preserved in Child Releases​

When the Password release property references a password variable, a Create Release task now passes the variable reference to the child release instead of the password value. The child release resolves the variable when its tasks run.

The variable must be in scope for the child release. Global password variables and secret manager references are always in scope. A folder password variable is in scope only when the destination folder defines it or inherits it from a parent folder. A release password variable is never in scope. If the variable is not in scope, the task fails before it runs and the error names the variable.

For more information, see Passing the Run As Password to Child Releases.

Plugins and Integrations​

Agent Orchestration Container Plugin​

  • The Release LLM Integration Container plugin has been renamed to Agent Orchestration Container plugin.
  • The MCP Server connection and the Digital.ai LLM AI Model connection now support OAuth2 as an authentication method, alongside the existing options. Both support a Client Credentials or Password grant type, using the same set of fields: Access token URL, Username, Password, Client secret, and Scope. MCP Server connections also gained two optional Secret Header fields, for sending sensitive header values without exposing them in the plain Headers table.
  • The AI Model: Digital.ai LLM connection now supports model aliases. The Model field is renamed Model or Alias, and it accepts either a provider model ID or a system model alias, such as dai-chat-general. A platform administrator maps the alias to a list of provider models in priority order, and the Digital.ai LLM Service resolves it to a concrete model, so the connection keeps working when the underlying models change. System alias names start with dai-.
  • The MCP: Call Tool task now renders a Tool input form generated from the selected tool's JSON Schema, instead of a raw JSON textarea. Required fields are marked as required, and fields with a schema default value are pre-filled automatically. Complex or unsupported schema types, such as nested objects or oneOf/anyOf compositions, fall back to a JSON textarea for that field. If the tool's schema cannot be loaded, the raw JSON textarea is shown for the entire Input property as before.

For more information, see Agent Orchestration Container Plugin.

Argo CD Container Plugin​

Added a Cluster Name field to the Create Application (Container), Update Application (Container), and Check if ArgoCD Application Already Exists (Container) tasks. Use it to identify the destination Kubernetes cluster by name instead of by URL. Provide either Cluster URL or Cluster Name, not both.

For more information, see Argo CD Container Plugin.

Conjur Plugin​

The Conjur Plugin now supports OAuth 2.0 authentication for server connections, enabling token-based (JWT) authentication for CyberArk Conjur Cloud (SaaS) connections.

For more information, see Conjur Plugin.

Deploy Plugin​

  • Deploy tasks now support Unicode characters, such as emoji, in deployment output.
  • Deployment errors from Deploy are now shown in the corresponding Release task output, making it easier to identify the cause of a deployment failure.
  • The plugin now uses the JDK truststore instead of the Python certificate bundle for API requests to Deploy, adding support for user-configured custom certificates.

For more information, see Deploy Plugin.

Jira Plugin​

The Create Issue Json task now converts rich text fields, such as description and environment, to Atlassian Document Format when a cloud connection is used.

For more information, see Jira Plugin.

Remote Completion Plugin​

Remote Completion now accepts replies in which an email watermarking gateway has replaced the spaces after ACTION:, TASK_ID:, and SIGNATURE: with non-ASCII characters.

For more information, see Use Remote Completion Task.

ServiceNow Plugin​

  • The Wait for Status task now processes structured response data returned while polling.
  • The Find Records by Query task now returns records that have empty field values, including on Oracle databases.

For more information, see ServiceNow Plugin.

Administration​

Permission Updates​

Admin Roles Hidden from Users Without the Admin Permission​

Users who have the Edit security permission but not the Admin permission no longer see roles that include the Admin permission. Such a role is not listed in the Roles column on the Permissions page and does not appear in the dropdown when you type a role name, so these users cannot assign permissions to it or remove permissions from it.

For more information, see The Permissions Page.

Runner Updates​

Runner Capability Name Validation​

Release now validates capability names when you add them to a runner. A capability name can contain letters, numbers, and hyphens (-), such as prod, k8s, or remote-script. Release removes surrounding spaces when you add a capability, and rejects a name that contains any other character.

For more information, see Runner Capabilities.