Skip to main content

Success Community

Support

Version 6.3.0

Version 6.3.0

Release Date : 09-08-2026

Features

1. MTAR Application

ReleaseOwl now offers comprehensive DevOps support for SAP BTP MTAR applications, extending Release Pipelines to automate the complete application delivery lifecycle. This release brings end-to-end automation for MTAR application development, validation, and deployment — streamlining Git operations, standardizing release processes, and reducing manual effort across SAP BTP landscapes.

What’s New MTAR Application Registration

ReleaseOwl introduces a new MTAR Application configuration that enables administrators to register SAP BTP MTAR applications for deployment management.

The configuration includes:

  • Application information
  • Source code repository configuration
  • Source Control Management (SCM) credentials
  • Branching model selection
  • Build Pipeline configuration

ReleaseOwl supports the following development models:

  • Feature Branch Model: Each User Story is associated with a dedicated feature branch. All development, build, and deployment activities for the User Story are performed using that branch.
  • Cherry Pick Model: Specific commits are selected from the development branch for a User Story. Only the selected commits are included in the build and promoted through the Release Pipeline.

Landscape Configuration

Administrators can configure multiple SAP BTP environments for each MTAR application.

Each environment supports:

  • Branch mapping
  • Build Pipeline association
  • Environment-specific .mtaext file configuration
  • Development branch configuration for Cherry Pick projects

This configuration provides centralized management of environment-specific deployment settings.

Artifact Source in Release Pipelines

Release Pipelines now include a new Artifact Source option, providing greater flexibility in artifact selection.

The supported artifact sources are:

  • Build Pipeline – Uses artifacts generated by a configured Build Pipeline.
  • User Story – Processes artifacts for any registered MTAR application associated with a User Story.

This enhancement provides greater flexibility in pipeline configuration and artifact management.

MTAR Application Support in User Stories

User Stories now support one or more MTAR applications.

The following capabilities are available:

  • Associate multiple MTAR applications with a single User Story.
  • Manage Feature Branches directly from the User Story.
  • Select commits for Cherry Pick–based projects.
  • Create Feature Branches and Hot Fix Branches.
  • Promote multiple MTAR applications through a single Release Pipeline.

Change Type

A new Change Type field has been introduced for MTAR project User Stories.

The supported values are:

  • Normal
  • Hot Fix

The selected change type determines the branch creation and promotion process throughout the release lifecycle.

2. New Release Pipeline Workflow Tasks

ReleaseOwl introduces dedicated workflow tasks to automate MTAR application deployments as part of the Release Pipeline workflow. These tasks streamline the deployment process, reduce manual effort, and ensure consistent promotion of MTAR applications across SAP BTP environments.

MTAR Pull Request Task

ReleaseOwl introduces a new MTAR Pull Request workflow task that automates the creation of pull requests between configured source and target branches during Release Pipeline execution.

Key capabilities include:

  • Support for Feature Branch, Hot Fix, and Environment branches.
  • Automatic branch resolution based on User Stories or Landscape Configuration.
  • Human approval workflow through My Tasks.
  • Assignment of approval tasks to users, roles, or custom components.
  • Automatic continuation of the Release Pipeline after approval.

MTAR Application Merge Task

A new MTAR Application Merge workflow task automates Git merge operations as part of the Release Pipeline.

Key capabilities include:

  • Merge from User Story branches.
  • Merge from environment branches.
  • Temporary staging branch support.
  • Support for Release Packages.
  • Conditional execution for User Stories and Release Packages.
  • Email notifications upon successful merge completion.

MTAR Application Build Task

ReleaseOwl introduces a new MTAR Application Build task that automates the build process using configured Build Pipelines.

Key capabilities include:

  • Build from User Story branches.
  • Build from environment branches.
  • Build from staging branches.
  • Separate build configuration for Release Packages.
  • Support for multiple MTAR applications within a single User Story.
  • Automatic generation of deployment-ready MTAR artifacts.

MTAR Validation Task

A new MTAR Validation task enables automated quality verification before deployment.

Key capabilities include:

  • Validation of artifacts generated by selected Build Tasks.
  • Generation of validation reports.
  • Dependency analysis.
  • Impact analysis.
  • Integration with quality validation tools such as SonarQube, ESLint, and OPA5 (where configured).
  • Configurable pipeline behavior using the Continue on Failure option.

Automated Deployment Support

The deployment stage has been enhanced to support the deployment of multiple MTAR applications within a single Release Pipeline execution.

Deployments automatically use:

  • Configured environment mappings.
  • Associated Build Pipelines.
  • Environment-specific .mtaext files.
  • Generated MTAR deployment artifacts.

These enhancements provide a streamlined, automated deployment workflow for SAP BTP MTAR applications while ensuring consistent promotion across environments.

3. CPI- B2B Scenarios

ReleaseOwl introduces Trading Partner Management (TPM) support for SAP Integration Suite, enabling organizations to synchronize, manage, version, and deploy TPM artifacts across environments.

The new B2B Scenarios capability provides centralized management of the following TPM artifacts:

  • Agreements: Exported Agreements from the SAP Integration Suite B2B Scenarios application can be imported into ReleaseOwl for management and deployment. Users can view Agreement details, download the exported artifacts, and track their deployment history across environments.
  • Partner Directory: Partner Directory data can be synchronized from SAP Integration Suite to ReleaseOwl. Users can search and view Partner Directory entries along with their parameter details, including Parameter ID, Value, Type, and Content Type. Both String and Binary parameter types are supported, with the option to download associated Binary content.
  • Partner Directory Configuration: A ReleaseOwl-specific artifact that allows selected Partner Directory attributes to be grouped and managed as a single unit. This simplifies deployment by allowing multiple attributes to be versioned and deployed together instead of individually.

Partner Directory Configurations can be created, updated, and versioned, with specific versions assigned to User Stories for deployment. Users can also view the deployment history of each configuration, providing better traceability throughout the release lifecycle.

4. ESLint & OPA5(Karma) Test Integration

ReleaseOwl now supports ESLint and OPA5 testing through Karma in Build Pipelines, enabling automated code quality and test validation as part of the build process.

What’s New:

  • OPA5 Test Integration: Run OPA5 test suites automatically using Karma during the Build Pipeline execution.
  • ESLint Integration: Perform ESLint static analysis alongside SonarQube to identify code quality issues.
  • Consolidated Tool Integrations: Configure Karma, ESLint, SonarQube, Malware Scanning, and SAP CVE checks from a single Tool Integrations step.
  • OPA5 Test Results: View OPA5 test counts in the SonarQube report.
  • Per-Stage Build Visibility: View individual build stages, including status, duration, timestamps, and logs, for easier troubleshooting.

5. Users & Roles Reports

Two new administrative reports are available under Reports, giving security and compliance teams a direct export of the tenant’s access model:

  • User Roles Report — lists users and their assigned roles. A Project filter lets you scope the report to a single project’s access picture.
  • Role Permission Report — lists roles and their associated permissions (role actions), showing what each role allows.

Both reports can be viewed on screen or downloaded as Excel (e.g., UserRolesReport-<date>.xlsx) — ready to attach to access reviews and audit evidence without manual screenshotting of the Role Actions screens.

Improvements

  1. Complete Environment Details in Project Settings

Project Settings now displays complete environment details, including the Host URL, System Type, and Users with Deployment Access. This provides better visibility into the configured environments and their deployment access within the project.

  1. Pagination for SAC and SDS

Pagination has been added to SAP Analytics Cloud (SAC) and SAP Datasphere (SDS) artifact listings for improved navigation and performance when managing large sets of artifacts.

  1. Import Settings- SAC and SAP Datasphere

Import Settings are now available for SAP Analytics Cloud and SAP Datasphere within the User Story edit view under the SAC/ SAP Datasphere Artifacts section. The settings include a Force Deploy option:

  • When Force Deploy is enabled, version validation checks do not block the deployment. If the target environment version is higher than the source environment version, the deployment proceeds and a warning message is displayed instead of an error.

  • Deployments performed with Force Deploy are marked with an icon in the Deployment Logs section, providing a permanent, visible record that version validation was overridden for that deployment.

  1. User Story Actions Enhancements

The Release Package Details option is now available directly in the User Story toolbar as well as within the Actions menu.

  • Export: Allows users to export User Story details from the Actions menu.
  • Release Package Details: Provides quick access to the release package information associated with the User Story from either the toolbar or Actions menu.
  1. Release Audit Report for user stories and release packages

A Release Audit Report can now be generated and downloaded at two levels:

  • User story level — the full delivery trail of a single story: what was changed, validated, approved, and deployed, by whom and when.
  • Release package level — the consolidated audit trail across all user stories carried in the package.
  1. SAP Cloud ALM Monitoring

Advanced Monitoring Settings: ReleaseOwl now provides enhanced monitoring integration with SAP Cloud ALM, allowing teams to send ReleaseOwl execution messages to SAP Cloud ALM for centralized monitoring and visibility.

Under Advanced Settings, users can enable Push Monitoring Messages and configure the types of messages to be sent to SAP Cloud ALM. The following message types are supported:

  • Deployment Messages – Provides visibility into deployment activities and their status.
  • Build Messages – Captures build-related activities and results.
  • Validation Messages – Provides information about validation activities and outcomes.

Multiple message types can be selected together, allowing teams to configure monitoring based on their requirements. This enhancement helps centralize ReleaseOwl pipeline activity in SAP Cloud ALM and improves visibility into build, validation, and deployment processes.

  1. External ID in ROALM

The Link External IDs option is now available when configuring the RO ALM integration. When enabled, an External ID column is displayed in the User Stories list, allowing users to view the external ID associated with each User Story.

Bugs

When a deployment fails and the user makes changes to the User Story or Release Package, retrying the deployment displays error messages.