Loading
Skip to main content

Success Community

Version 6.4.0

Release Date : 11-10-2026

Features

Zoho Service Desk Integration

ReleaseOwl now supports Zoho Service Desk as an ALM (issue-tracker) integration, alongside Jira, ServiceNow, Freshservice, 4Me, and Azure DevOps. Requests and changes created in Zoho Service Desk can be imported into ReleaseOwl as user stories, and their status remains synchronized with the release pipeline.

Credential

Create a credential of type Zoho Service Desk in Credential Manager. The integration uses OAuth for authentication.

What you can do

The integration supports the following actions:

  • Select Zoho Service Desk projects and boards when configuring the project’s ALM integration, including filter-based boards.
  • Zoho requests and changes are synchronized as user stories in ReleaseOwl. Individual items can be opened using their external IDs.
  • View the current status of requests and changes and determine the next status to which a user story can move.
  • Update the status of a Zoho item from the release pipeline and add a comment.
  • Add comments from ReleaseOwl to the Zoho item as plain text or formatted text.

ReleaseOwl provides a webhook address for each project (one for requests and one for changes). When an item changes in Zoho Service Desk, Zoho calls this address and ReleaseOwl updates the user story. The address contains a secret key that is checked for every call.

License Info

The License Info screen under Administration now provides a clearer view of the tenant’s license usage and product entitlements. The SAP Cloud ALM Features usage card displays the Total, Deployed, and Remaining counts, along with the Alert Threshold. A progress bar provides a visual indication of usage and turns red when usage exceeds the licensed total.

Pipeline Reports

A new Pipeline Reports tab is available on the Reports page, alongside Deployment Reports and Task Reports. These reports provide visibility into user stories and artifacts promoted through release pipeline stages, including promotion and approval details, supporting production change audits.

Three reports are available:

  • User Story Deployment Pipeline Report: Shows user stories promoted through selected pipeline stages. Filter by date range, release pipeline, and one or more stages to define which stages to include.
  • CPI Artifacts Deployment Pipeline Report: Lists deployed CPI artifacts with their associated user story promotion and approval details.
  • API Artifacts Deployment Pipeline Report: Provides deployment pipeline details for API artifacts.

The User Story Deployment Pipeline Report includes the user story ID, external ID, summary, release package, stage, promotion details, promoter, promotion date, and approval information, including approvers and delegated approvals where applicable.

ABAP Checkout Task for RAP Applications

For RAP applications, feature-related and hotfix changes are merged directly into the target branch. The new ABAP Checkout task checks out the target branch in the software component of the target BTP ABAP Environment before validation and deployment. This ensures that validation and deployment use the intended code.

How it works

The task starts the checkout operation on the target system and monitors it until the checkout is complete. The result, whether successful or failed, is recorded against the user story for traceability.

Fields

The task includes the following fields:

  • Name / Description: Identifies the task.
  • Checkout Source: Specifies where the branch comes from. The available options are Branch/Commits from User Story and Branch from Environment. When Branch from Environment is selected, the Source Environment field is displayed.
  • Target Environment: Specifies the environment from which the branch is obtained when Checkout Source is set to Branch from Environment.
  • Notify Users: Sends a notification when the task is completed.

Improvements

Manage Users

The Settings section in Manage Users now displays Created On, Created By, Modified On, and Modified By details for each user. These details are available for records created or modified from April 2026 onward. For records from before April 2026, the corresponding fields remain blank.

RAP Application Deployment Report

A new RAP Application Deployment Report is available under Reports to track deployments of RAP applications to ABAP Cloud environments. The report provides details about deployed applications, source branches, deployment dates, and deployment status.

On the Reports page, the Deployment Reports tab now includes a RAP Application Deployment Report card alongside the User Story Deployment Report. The Task Reports tab remains unchanged.

Filters

Filter deployment records by From Date, To Date, and Environment. You can hide the filters to provide more space for the report table.

Export

Use the Export button to download the report as an Excel file for auditing and sharing.

SAC and SDS: Environment-Based Import Configuration

Import settings for SAP Analytics Cloud (SAC) and SAP Datasphere (SDS) can now be configured separately for each environment. A package no longer needs to be imported with the same settings across all environments. For example, data can be included when importing to QA and excluded when importing to production.

  • Default import settings: Configure the default import settings in the SAC and SDS deploy tasks of the pipeline.
  • Deployment audit: The import settings used for each environment are recorded in the deployment log, allowing deployments to be audited later.
  • Datasphere space mappings: Define space mappings at the tenant level and for individual environments. The configured mapping is always applied during SDS deployment to ensure that items are deployed to the intended space.

SAC and SDS: Manual Completion

SAC and SDS deployments can now be marked as completed manually. This is useful when a deployment needs to be closed after a manual fix, keeping the pipeline and deployment records consistent.

  • Deployment log: The deployment log now records whether a deployment was completed Manually or Automatically.

SAC and SDS: Add Artifacts and Individual Sync

Users can now add or remove selected SAC and SDS artifacts for a project environment and synchronize individual artifacts when only a specific item has changed. This avoids synchronizing and importing all artifacts for a small change and helps keep each project focused on the artifacts it manages.

SAC and SDS: Sync History

The Sync History for SAP Analytics Cloud and SAP Datasphere now provides detailed information about changes detected during each synchronization, instead of only recording that a sync was performed.

Administrators and developers can now see:

  • Which packages were added, updated, or removed.
  • The number of changes detected during a synchronization.
  • Which packages failed to synchronize and the reason for the failure.

This makes it easier to track what changed and when and identify why a synchronization failed.

New Roles and Permissions

The Manage Roles section now includes additional roles and permissions for SAP Analytics Cloud (SAC), SAP Datasphere (SDS), and SAP Public Cloud. These permissions provide more granular control over package and artifact management, synchronization, user-story assignment, and import configuration.

Build Pipeline: Maven and Gradle Tests for Java Applications

The build pipeline now supports running Java test cases with Maven or Gradle for Java (CAP) applications built as MTA (Java). Teams can run existing Maven or Gradle tests as part of the build pipeline and report the test results to SonarQube for code analysis.

Builder Step

The Builder step now includes a Java Build Tool field, where you can select Maven or Gradle when configuring an MTA (Java) build.

Tool Integrations

The Tool Integrations step now includes JUnit under Additional Tests. When JUnit is selected, ReleaseOwl executes the Java test cases using the Maven or Gradle build tool selected in the Builder step. The existing Karma and WDI5 test options are also available under Additional Tests. To execute WDI5 tests, provide the appropriate test script defined in your application’s package.json, select WDI5 under the Additional Tests field, and enter the corresponding script name in the Web Driver IO Scripts field.

Pipeline Execution

Based on the selected Java build tool, the generated pipeline includes either a Maven Tests or Gradle Tests stage. The tests run using a build image that matches the selected Java version. WDI5 tests can also be executed as an additional test, and their results are converted into a format that can be processed by SonarQube.