ReleaseOwl Releases

ReleaseOwl follows a continuous deployment approach to deliver updates to its SaaS platform. New software versions—including feature enhancements, security patches, and bug fixes—are rolled out regularly to ensure seamless improvements. This process is designed to minimize downtime, maintain business continuity, and provide users with an uninterrupted experience.

Key Aspects of ReleaseOwl Releases:

Continuous Improvement: Each release incorporates enhancements based on customer feedback, industry trends, and technical advancements.
Reliability and Stability: Releases undergo thorough testing, validation, and quality assurance (QA) before deployment.
Security and Compliance: Security patches and compliance updates are integrated into releases to safeguard data and ensure adherence to industry standards.
Version Control: Every release follows a structured versioning format (e.g., YYYY.Major.Minor), where YYYY represents the year, Major denotes the major release, and Minor represents minor updates.

Release Notes

Release Notes provide a summary of changes included in a particular release. They serve as a reference for customers and users to understand what’s new, improved, or fixed.

Each release note typically contains:

Version Information: The release number and date.
New Features: Introduction of new functionalities.
Enhancements: Improvements to existing features.
Bug Fixes: Resolution of reported issues.

Release Calendar

1. Release Process & Cadence

The Release Process is a structured workflow followed to deploy new updates. It includes both the Normal Release Process and the Hotfix Process, governed by a clear release cadence to ensure efficient feature rollouts and system stability.

1.1 Release Cadence

Type	Purpose	Frequency
Major Releases	New features, enhancements, significant changes.	Quarterly
Minor Updates	Bug fixes, performance improvements, security patches.	Monthly
Hotfixes	Critical bug fixes & urgent security patches.	As needed

1.2 Normal Release Process

Schedule

Releases occur monthly, typically on Sundays (IST) to minimize business disruptions.

Some releases may be minor patches.
Others introduce significant features and improvements.

Communication

Communication Stage	Details
Pre-Release Notification	Email sent to all existing customers one week before the scheduled release with info about upcoming changes and potential downtime.
Post-Release Update	Email sent after successful deployment with release notes detailing changes, enhancements, and known issues.

Data Migration

Performed automatically during deployment.
If manual intervention is needed, affected customers will be notified with detailed steps.

Downtime

2 to 5 hours, depending on update complexity.
Efforts are made to minimize downtime while ensuring successful rollout.

1.3 Hotfix Process

Schedule

Hotfixes are deployed the same day or next day to minimize customer impact.

Downtime

30 minutes to 1 hour, depending on complexity.

Communication

Communication Stage	Details
Pre-Deployment Notification	Sent 4 hours before deployment to affected customers.
Post-Deployment Update	Sent after successful hotfix deployment.

1.4 Incident & Downtime Management

Incident Classification & Response Time

Incident Type	Impact	Response Time	Resolution Target
Critical (P1)	Complete system failure, affecting all users.	Immediate	Resolution within hours
High (P2)	Key functionality unavailable, workaround exists.	Within 1 hour	Resolved within 24 hours
Medium (P3)	Non-critical issues with limited impact.	Within 24 hours	Fixed in next Monthly Release
Low (P4)	Cosmetic or minor functional issues.	Within 48 hours	Scheduled in the roadmap

Downtime Handling & Communication

Action	Details
Real-time Monitoring	Proactive monitoring to detect issues before they impact users.
Pre-Downtime Notification	Customers notified in advance of scheduled maintenance/downtime.
Incident Status Updates	Continuous communication via email and a status page.
Post-Incident RCA	Root Cause Analysis with preventive measures shared with affected customers.

ReleaseOwl Releases

Key Aspects of ReleaseOwl Releases:

Continuous Improvement: Each release incorporates enhancements based on customer feedback, industry trends, and technical advancements.
Reliability and Stability: Releases undergo thorough testing, validation, and quality assurance (QA) before deployment.
Security and Compliance: Security patches and compliance updates are integrated into releases to safeguard data and ensure adherence to industry standards.
Version Control: Every release follows a structured versioning format (e.g., YYYY.Major.Minor), where YYYY represents the year, Major denotes the major release, and Minor represents minor updates.

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

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.

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.

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.

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.

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.

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.

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.

Version 6.2.3

Enhancement

Sonar Project Management Enhancement

Previously, a new Sonar project was created for every build executed through the Build Pipeline. This resulted in multiple Sonar projects being generated for the same application across different build executions.

The system has been enhanced to create a single Sonar project for an application and associate subsequent build executions with the same project using version numbers. This provides better project organization and simplifies Sonar project management. Only the user who creates a Sonar project can view and access it. Other users cannot view, search for, or access projects created by another user.

Default Workbench Client Support for Multi-Landscape Deployments

Previously, the deployment configuration supported only a single target client for transport imports. As a result:

Customizing transports were imported into the configured target client.
Workbench transports were also imported only into the same target client.
If Workbench transports needed to be deployed to additional clients or landscapes, users had to perform manual import activities.

Current Enhancement

A new field, Default Workbench Client, has been introduced in the Validation ,Deployment and Import via TOC tasks.

When the Default Workbench Client is configured:

Customizing transports continue to be imported only into the primary target client.
Workbench transports are automatically imported into:
- The primary target client configured for the deployment.
- The Default Workbench Client specified in the deployment configuration.

Example Scenario

A deployment is configured with the following settings:

Target Client: Client A
Default Workbench Client: Client B

Deployment Behavior

Transport Type

Import Destination

Customizing Transport

Client A only

Workbench Transport

Client A and Client B

As a result, Customizing transports continue to be imported only into their designated target client, while Workbench transports are automatically imported into both the primary target client and the configured Default Workbench Client.

Version 6.2

Release Date : 31-05-2026

Features

ALM Integrations – ReleaseOwl Configuration Support

Introduced ReleaseOwl Integration support within the ALM Integrations module. Users can now configure and manage ReleaseOwl integrations through a dedicated integration interface by selecting ReleaseOwl as the external system and configuring project workflow types such as Scrum or Kanban.

This enhancement also supports the configuration and management of workflow-specific Statuses and Types within the integration setup.

Statuses – Allows users to define and manage workflow statuses such as To Do, In Progress, and Completed.
Types – Allows users to define and manage work item types such as Bug, Task, and Story.

Additionally, if a project is already configured with a Scrum workflow integration, the same project cannot be added again in another integration configuration. To reconfigure the project with a different workflow setup, the existing integration must first be deleted and then recreated.

Audit APIs

To improve auditability, governance, and external reporting capabilities, ReleaseOwl now introduces a new set of Audit APIs. These APIs provide access to workflow approvals, project information, role configurations, and user assignments, enabling external systems and reporting tools to retrieve audit-related data directly from ReleaseOwl.

Workflow Approver Details API

This API retrieves approver details for a specific workflow instance, including task information, approver details, approval status, approval date, and associated role information. It provides complete visibility into the approval history of an individual workflow instance.

Workflow Approval Audit API

This API retrieves approval details for workflow instances within a specified date range for a selected project and workflow. The response includes approval information grouped by workflow instance, making it suitable for audit tracking, compliance reporting, and historical analysis.

Projects API

This API retrieves all projects available within a tenant, along with project-related information and associated users. It enables external systems to access project metadata for reporting and governance purposes.

Roles API

This API retrieves all roles configured within a tenant, including role metadata such as role name, description, and role type. It provides visibility into role definitions and access structures across the tenant.

Users API

This API retrieves users associated with a specific project and role. The response includes user details such as username, first name, last name, and unique user identifier, providing visibility into project-level role assignments and user access.

Improvements

API Management – Selective Artifact Addition

Introduced an “Add Artifacts” option in API Management that allows users to add selected artifacts directly instead of synchronizing all available artifacts. Users can now choose and add only the required artifacts, reducing unnecessary synchronization activities and simplifying artifact management within the application.

API – Action Column Enhancement

Enhanced the Sync History view in API Management by introducing a new Action column. The column displays the type of operation performed during synchronization, such as:

ADDED – Indicates newly added artifacts.
UPDATED – Indicates artifacts that were modified and updated during a subsequent synchronization.
REMOVED – Indicates artifacts that were removed from the project.

Additionally, if API Management artifacts are removed, the sync status will be displayed as COMPLETED_WITH_ERRORS when the artifact is assigned to a user story.

API Management – Artifact Search Functionality

Introduced an advanced search capability for API Management artifacts within the application. Users can now efficiently locate specific artifacts by searching with the artifact name, significantly reducing the need for manual navigation through extensive artifact inventories.

API Management – Remove Artifacts

Introduced the Remove Artifacts capability in API Management. Instead of removing artifacts individually from the project, users can now select multiple artifacts using the checkbox option and remove them simultaneously by clicking Remove Artifacts.

API Management – New Role for Package Management Operations

Introduced a new role in API Management for package management operations. Users assigned with this role can now add or remove packages from the project directly within API Management, enabling more efficient management of API artifacts and packages.

Force Deployment Support for API Management Artifacts

Introduced Force Deployment support for API Management artifacts within the Import Settings section of the API Management Artifacts dialog under the User Story Edit view. This enhancement enables users to force deploy supported API Management artifact types, including API Proxies, API Providers, Key Value Maps (KVMs), and Products.

When Force Deploy is enabled, deployments are allowed to proceed even if the target environment version is higher than the source environment version. Instead of blocking the deployment, the system displays a warning message indicating the version mismatch.

Additionally, the Deployment Logs section now displays an indicator icon to identify deployments executed using the Force Deploy option.

Example Warning Message: “The artifact ‘<Artifact Name>’ target environment version ‘1.4’ is higher than the source environment version ‘1.3’, but Force Deploy is enabled.”

API Management – Enhanced API Provider Configuration Support

Enhanced API Provider configuration in API Management to support a broader range of provider-specific connection settings. Previously, only a limited set of API Provider configuration options were available in ReleaseOwl. With this enhancement, users can now configure all supported connection parameters required by different API Provider types.

The configuration screen dynamically displays the relevant input fields based on the selected provider type, including:

Internet – Host, Port, and SSL configuration.
On-Premise – Host, Port, Location ID, Authentication, and Additional Properties.
Open Connectors – Region, Host, Port, Organization Secret, and User Secret.
Cloud Integration – Cloud Integration Management Host, Port, Authentication, Username, and Password.

This enhancement ensures that ReleaseOwl supports client-specific API Provider configurations and provides greater flexibility when managing API Management connections across QA and Production environments.

Integration Advisor – Selective Artifact Addition

Introduced an “ADD Artifacts” option in Integration Advisor that allows users to add selected artifacts directly instead of synchronizing all available artifacts. Users can now select and add only the required artifacts, reducing unnecessary synchronization activities and simplifying artifact management within the application.

Integration Advisor – Artifact Search Functionality

Introduced search functionality for MAG (Message Implementation Guideline) and MIG (Message Implementation Guide) artifacts within the application. Users can now quickly identify and access required artifacts by searching with the artifact name, eliminating the need to manually browse through large artifact collections.

Integration Advisor Sync History – Action Column Enhancement

Enhanced the Sync History view in Integration Advisor by introducing a new Action column. The column displays the type of operation performed during synchronization, such as:

ADDED – Indicates newly added artifacts.
UPDATED – Indicates artifacts that were modified and updated during a subsequent synchronization.
REMOVED – Indicates artifacts that were removed from the project.

Additionally, if Integration Advisor artifacts are removed, the sync status will be displayed as COMPLETED_WITH_ERRORS when the artifact is assigned to a user story.

Integration Advisor – Remove Artifacts

Introduced the Remove Artifacts capability in Integration Advisor. Instead of removing artifacts individually from the project, users can now select multiple artifacts using the checkbox option and remove them simultaneously by clicking Remove Artifacts.

Deployment History – Integration Advisor

Introduced the Deployment History option in Integration Advisor to display the complete history of package deployment activities. This enhancement provides detailed tracking information for each artifact deployed within a package, enabling users to monitor deployment actions, review deployment status, and maintain deployment traceability across environments.

Release Pipelines- Versions

Introduced a new Versions option in Release Pipelines to display all versions for the selected Release Pipeline. This enhancement enables users to track and view generated pipeline versions associated with user story promotions. Versions are displayed only after the corresponding Release Pipeline has been promoted for a user story.

Multi-Language Support Enhancement

Introduced multi-language support in ReleaseOwl to improve accessibility and enhance the user experience for global users. Users can now switch the application language directly from the profile menu. Language support has been implemented across most labels and application screens to provide a more localized and user-friendly experience.

The following languages are currently supported:

English
German
Spanish
French
Portuguese

This enhancement enables users to interact with the application in their preferred language, improving usability and navigation across ReleaseOwl modules.

Reports Section for BTP & Multiverse

Introduced the Reports section in the Project View for both BTP and Multiverse projects, providing centralized visibility into deployment and task-related activities.

The Reports section currently supports the following report types:

Deployment Reports – Enables users to track deployment activities and deployment status of user stories by applying filters such as date range, environment, target system, and deployment status.
Task Reports – Provides visibility into task execution details across environments, including information such as release pipeline, pipeline stage, deployment status, assigned user, and related task activities.

This enhancement improves deployment monitoring, operational visibility, and reporting capabilities across BTP and Multiverse projects.

Human Tasks – Promoter cannot be the approver

Introduced the “Promoter cannot be the approver” option for Human Tasks in Release Pipelines. When this option is enabled, the promoted user cannot approve or reject the request from My Inbox. An error message will be displayed if the promoted user attempts to perform the approval action.

Release Pipelines- Prevent same approver across tasks

Introduced a new option in Release Pipelines: “Prevent same approver across tasks”. When this option is enabled, the same user cannot be assigned as the approver for multiple Human Tasks within the same pipeline. This enhancement ensures segregation of duties by preventing a single person from performing multiple approval roles, such as Peer Review, QA Approval, and UAT Testing, within the same release process. If the same user attempts to approve multiple tasks, the system will display an error message and block the action.

CPI Management – Add Artifact

Introduced the Add Artifact capability in CPI Management. Instead of synchronizing all artifacts from the package, users can now add individual artifacts by entering the Artifact ID and selecting the Artifact Type. After providing the required details, the artifacts can be added directly using the Add option, enabling selective artifact addition and management.

The Artifact ID can be obtained from SAP BTP Integration Suite. For Integration Flows (iFlows), the Artifact ID is available in the General section of the artifact. For Message Mappings, the Artifact ID can be found under the View Metadata section.

CPI Sync History – Action Column Enhancement

Enhanced the Sync History view in CPI Management by introducing a new Action column. The column displays the type of operation performed during synchronization, such as:

ADDED – Indicates newly added artifacts.
UPDATED – Indicates artifacts that were modified and updated during a subsequent synchronization.
REMOVED – Indicates artifacts that were removed from the project.

Bugs

Update IFlow XML Config Parameter Value to Target Environment

This bug involves dynamically updating the IFlow XML configuration parameter values based on the selected target environment during deployment. The fix ensures environment-specific configuration values are correctly replaced before deployment, improving deployment accuracy and reducing manual configuration efforts.

Deploy Integration Advisor Overlay MAG

This enhancement focuses on enabling deployment support for Integration Advisor Overlay MAG artifacts. Previously, Overlay MAG deployments were either unsupported or failing during execution. The fix introduces proper handling, packaging, and deployment flow for Overlay MAG artifacts, ensuring successful deployment and better compatibility with SAP Integration Advisor processes.

Version 6.1.0

Release Date : 12-04-2026

Features

1. JIRA Credential Validation & Proxy Configuration

Introduced a Validate option during JIRA credential registration for Basic Authentication, OAuth, and Bearer Token methods. This enables validation of JIRA credentials to ensure successful connectivity using any of the supported authentication types.
Enhanced existing proxy capabilities by adding support for SAP Cloud Connector. This enables secure connectivity between ReleaseOwl and on-premise JIRA instances, allowing access to JIRA systems within the client network without exposing them externally.

2. New Pipeline Tasks in Release Pipelines

Introduced new pipeline tasks to enhance governance, validation, and control during the release process.

Newly Added Tasks:

Checklist Task
- Introduced Checklist Task in release pipelines to enable execution of structured pre-release validation and compliance checks.
- Allows teams to define and verify mandatory steps, approvals, and conditions that must be completed prior to deployment.
- Ensures adherence to organizational standards and release governance by enforcing checklist-driven validations.
- Reduces the risk of missed steps and improves overall release quality by confirming readiness before progressing further in the pipeline.
Once a Checklist Task is added to a User Story and promoted, the assigned user can access it from the My Tasks section via the Approve / Reject action.
Within the task, all checklist items are displayed, including mandatory items marked with a star (★). Users can upload required files, mark items as done, and provide comments as needed.

After performing Approve or Reject, the executed checklist details can be viewed in the Pipeline Activity section.

Branch Merge Task

Introduced a Branch Merge Task as part of the release pipeline workflow to enable merging of changes from one branch to another using supported source control systems such as Git.

This task allows users to select the repository and branches, and perform merge operations directly within the pipeline.

In case of merge conflicts, the conflicts are surfaced at the User Story level, allowing users to review and resolve them as part of the workflow.

User Story Field Task

Introduced a new pipeline task User Story Field Task to enable dynamic synchronization of user story fields with integrated ALM systems such as JIRA.
As part of the ALM integration, user story metadata (fields) are automatically fetched from the external system and made available within ReleaseOwl. This task ensures that these fields are programmatically updated and aligned during pipeline execution.
The task operates by:
- Retrieving configured user story fields from the integrated ALM system
- Mapping and updating those fields within the ReleaseOwl user story context
Enables better traceability and data integrity by ensuring that critical fields (such as status, metadata, or custom fields) remain up to date throughout the release lifecycle.
Improves overall pipeline automation by incorporating field-level updates as a controlled task, ensuring that user story data is accurate before progressing to subsequent stages.

3. SAP CPI Environment – Mock Prefix Configuration

Introduced Mock Artifacts Prefix in SAP CPI Environment configuration, which becomes available when Test Automation is enabled.
Allows users to define a custom prefix value that is used to dynamically bind mock endpoints during test execution.
When a Mock Prefix is specified:
- Relevant endpoints are automatically mapped to their corresponding mock services
- Ensures that test cases are executed against mocked integrations instead of actual backend services

4. Origin Key – SAP Passport & SAP Cloud Identity Services

Introduced Origin Key support for both SAP Passport and SAP Cloud Identity Services (Identity Authentication) to enhance authentication handling and request traceability.
For SAP Cloud Identity Services (OIDC-based Web Authentication), users can retrieve the generated Origin Key from the Trust Configuration and configure it in ReleaseOwl after saving the credential.
For SAP Passport, the default Identity Provider Origin Key available in SAP BTP Trust Configuration can be used.
This ensures consistent and secure integration with authentication providers across different credential types.

Improvements

1. Integration Advisor – Tab-wise Segregation of Integration Advisor Artifacts

Introduced separate tabs (MAG and MIG) for Integration Advisor artifacts.
Enables users to sync individual artifact versions more efficiently.
Enhances usability by providing a structured and organized view of artifact.

2. API Management – Sync & Configuration Improvements

In this release, we have introduced several enhancements to improve the usability and flexibility of API Management synchronization and configuration in ReleaseOwl.

Key Updates:

Added support for API Provider and API Product as part of the API Management synchronization and configuration process.
Introduced separate tabs for different API artifacts to clearly distinguish each component, enabling users to easily identify, navigate, and manage specific artifacts.
Enabled individual synchronization of API artifacts, allowing users to sync specific components and fetch the latest versions from the registered SAP API Management environment.

In this release, we have enhanced the navigation experience in the My Tasks section within release pipeline tasks by introducing clickable Reference IDs.

Tasks originating from User Story, Release Package, and Transport Management (with default pipeline configuration) are now traceable.
Clicking the Reference ID redirects users to the respective source screens (User Story Edit / Release Package Edit / Transport Edit).
Improves navigation, traceability, and overall user experience.

Enhanced CPI Alerts with actionable operations available directly from the alert details panel for alerts in Open/Failed status.
Introduced Raise Defect action:
- Allows users to create a defect directly from the alert context
- Integrates with SAP Cloud ALM for defect registration
- Enables seamless transition from monitoring to defect tracking without manual navigation
Introduced Code Change option:
- Provides access to analyze changes related to the impacted artifact
- Helps in identifying differences between versions contributing to the failure
- Supports faster root cause analysis by linking alerts with recent changes

5. Role-Based Access for Import Settings

Updated access control for Import Settings in Integration Advisor artifacts.
Previously, Import Settings were available at the Administration level. This has now been enhanced to follow a role-based access control mechanism.
Access to Import Settings is now governed through User Management → Roles configuration:
- Administrators must assign appropriate roles to users in the Manage Users section
- Within the assigned role, the Import Settings permission must be explicitly enabled under Role Actions
Only users with the required role permissions will be able to view and access the Import Settings option for the artifacts.
Additionally, Import Settings can now be enabled and accessed during the In-Progress stage, allowing users to perform import operations earlier in the lifecycle.

6. Sync History & Validation Report – Integration Advisor

Enhanced Sync History in both API Management and Integration Advisor to include additional artifact-level details.
Added new columns:
- Artifact Name
- Artifact Type
When a single artifact is synchronized, the Sync History displays the corresponding artifact name and type, providing clear visibility into the synced item.
When synchronization is performed based on artifact type (bulk/type-based sync), the system represents the entry with a generic indicator (e.g., ‘*’) instead of a specific artifact name.
Improves traceability and auditability by clearly distinguishing between individual artifact sync operations and type-based sync actions
Introduced Validation Report for Integration Advisor, providing detailed insights into the outcome of synchronization operations.
- Enables users to review validation results and identify issues at the artifact level
- Improves visibility into sync execution and artifact consistency

Version 6.0

Release Date : 08-03-2026

Features

1. Release Pipelines – Mandatory Comment Controls for Approval and Manual Tasks

To strengthen governance and audit traceability, new mandatory comment validations have been introduced for Approval and Manual stages within Release Pipelines.

Approval Stages: When Approval Comment Required is enabled at the task level, approvers must enter a comment while performing Approve or Reject actions from the My Tasks section. The action cannot be completed without a comment.

Manual Stages: When Complete Message Required is enabled, users must provide a completion message before marking the manual task as Complete from the My Tasks section.

2. CPI Monitoring – Configuration, Real-Time Monitoring, and Check Messages

ReleaseOwl now supports Integration Suite Monitoring, enabling users to monitor integration artifacts such as iFlows, APIs, and messages from the SAP CPI tenant. This feature provides visibility into message processing, failures, and performance, helping teams quickly identify and troubleshoot integration issues.

Users can enable monitoring from the CPI Environment under Advanced Settings and configure how monitoring data is retrieved through the CPI Monitoring Configuration. The configuration allows users to define message statuses, message count limits, and the initial time period for fetching monitoring data.

Additionally, users can enable Real Time Monitor to automatically fetch monitoring data from the CPI tenant at defined schedule intervals. If real-time monitoring is disabled, users can manually retrieve the latest monitoring records using the Check Messages option, which fetches data from the last execution time to the current time.

3. CPI Monitoring – Failure Alert Enhancement

A new alert monitoring capability has been introduced as part of the CPI Monitoring feature for SAP CPI environments.

When CPI Monitoring is enabled under Advanced Settings:

Automated failure alerts are triggered when an integration package execution fails.
Email notifications are sent to configured recipients for immediate visibility.
Enables proactive monitoring and faster resolution of integration issues.
Additionally, AI Coach Failure Analysis is now integrated with CPI Monitoring. When a failure occurs, AI Coach analyzes execution logs and provides potential root cause insights along with recommended corrective actions to accelerate troubleshooting and resolution.