What's new and changed in Orchestration Pipelines

Orchestration Pipelines updates can include new features and fixes. Releases are listed in reverse chronological order so that the latest release is at the beginning of the topic.

You can see a list of the new features for the platform and all of the services at What's new in IBM Software Hub.

Installing or upgrading Orchestration Pipelines

Ready to install or upgrade Orchestration Pipelines?

  • To install Orchestration Pipelines along with the other IBM® Software Hub services, see Installing IBM Software Hub.
  • To upgrade Orchestration Pipelines along with the other IBM Software Hub services, see Upgrading IBM Software Hub.
  • To install or upgrade Orchestration Pipelines independently, see Orchestration Pipelines.
    Remember: All of the IBM Software Hub components associated with an instance of IBM Software Hub must be installed at the same version.

IBM Software Hub Version 5.4.0

A new version of Orchestration Pipelines was released in June 2026 with IBM Software Hub 5.4.0.

Operand version: 5.4.0

This release includes the following changes:

New features
This release of Orchestration Pipelines includes the following features:
Manage and standardize configuration by using tenant-level settings

You can now configure Orchestration Pipeline settings at the tenant level, in addition to pipeline and project levels. This lets you manage and standardize configuration across pipelines using cpdctl, making it easier to enforce consistent behavior in multi‑tenant environments.

Simplify pipeline runs by using inline mode for standard runtime

You can now run pipelines in inline mode using the standard runtime. By using inline mode, you can avoid creating separate jobs for nested pipelines and DataStage runs, simplifying job execution and pipeline management.

Standardize pipeline job names across your tenant

You can now apply consistent job names to pipeline runs by using a single configuration setting. Set the job naming behavior once at the tenant level by using cpdctl to apply consistent naming across all pipelines without requiring updates in individual projects.

Analyze pipeline runs more easily by viewing separate logs for nested jobs

You can now review pipeline execution more easily by using separate logs for nested jobs. When you run pipelines, logs from subordinate jobs are now stored separately instead of being included in the pipeline runner log. This separation makes it easier for you to find, view, and analyze the log details for each job.

Grant operational pipeline access without edit permissions

You can now manage pipeline operations by using the new job operator role. Job operator users can run pipeline jobs and reset the job run cache without modifying pipeline configurations. This new role gives you a way to grant operational access without also granting permission to edit pipelines.

Run StreamSets job component

You can now run StreamSets jobs directly within pipelines by using the Run StreamSets job component. This allows you to integrate StreamSets job execution into pipeline workflows.

New features from 5.3.1 patches
This release of Orchestration Pipelines includes the following features that were introduced in IBM Software Hub Version 5.3.1 patches:
Shape node icons that are preserved for migrated flows
Migrated flows that use Shape Node icons now retain the same node shapes after migration, preserving visual consistency between original and migrated pipelines.
Full navigation of pipeline job logs
You can now navigate logs across the complete Pipeline job hierarchy, making it easier to trace execution through parent and nested jobs.
Consolidated Logs Tearsheet for nested jobs
By opening the Consolidated Logs Tearsheet, you can navigate and view logs for each Pipeline job in the parent job dependency tree without opening nested jobs or assets in a new tab.
Nested job log links for non‑inline pipeline runs
For non‑inline pipeline runs, the main pipeline log now includes links to DataStage and Orchestration Pipelines nested job logs instead of embedding them. You can preview logs or open the full job log for detailed run information. This feature is enabled by default on IBM Cloud Pak for Data and can be enabled on IBM Cloud Pa for Data as a Service by setting ENABLE_NESTED_JOB_LINKS=true.
Hotlinks for job log navigation
For standard pipelines running in inline mode, job logs now include hotlinks that let you directly access the pipeline or DataStage job that initiated them. This improves traceability and simplifies debugging when jobs are triggered by multiple upstream jobs.
Improved validation for ws‑pipelines custom resources
The ws‑pipelines custom resource is now aligned with its CRD, allowing only supported properties and preventing the use of undefined configuration values during deployment.
PodDisruptionBudget enforcement for workloads
A new policy enforces the presence of a matching, preexisting PodDisruptionBudget for all Deployments and StatefulSets, helping maintain minimum workload availability during voluntary disruptions when the policy is run in enforce mode.
Updates
This release includes a number of additional updates. With this release, you can:

  • Reset the job run cache from the Job Details page.

  • Scroll the consolidated logs table for pipeline job run events, allowing you to view all log entries.

  • Navigate settings using a left‑hand side panel, making it easier for you to access and switch between different sections.

  • View accurate data in the Node inspector, as it displays information only for the currently selected node.

  • Rely on accurate status recognition for Completed with warnings and Completed with errors in pipeline runs.

  • No longer paste non‑Pipelines objects into the Pipeline canvas, preventing unsupported content from being added.

  • See consistent labeling, as Run ID is updated to Job run ID across the interface.

  • Configure the Run jobs independently setting at the project level, allowing you to control how inline pipeline jobs are executed across all pipelines in the project.

  • Identify Run Stream sets more easily with a new icon for the Run Stream sets job node.

  • Restore default PROJDEF values for String‑type parameters by setting the value to PROJDEF.

  • See loop references in the Expression Builder using node names only.

  • See the loop iteration for each event from Loop nodes, making it clear which iteration the event belongs to.

  • View the full tooltip for the first parameter in the Edit local parameters tearsheet when overriding parameters for a nested job node.

  • Open the Consolidated Logs Tearsheet directly from nested job run events in loop nodes using a hyperlink.

  • Identify invalid expressions more easily, with error indicators shown on nodes and detailed error messages displayed in the expression field.

  • Open a pipeline without triggering an automatic save.

  • View job run history tables without overlapping cells.

  • Reset the pipeline job run cache directly from the Job Details page.

  • See toast notifications for cache reset actions, indicating when the reset starts, succeeds, or fails.

  • Configure cache usage for pipeline job runs in Optimized Runner using the checkbox.

  • View corrected text in the Condition response section for link conditions.

Customer-reported issues fixed in this release
For a list of customer-reported issues that were fixed in this release, see the Fix List for IBM Cloud Pak for Data on the IBM Support website.
Security issues fixed in this release
The following security issues were fixed in this release:
  • CVE-2026-27135, CVE-2026-32280, CVE-2026-32281, CVE-2026-32283, CVE-2026-32288, CVE-2026-32289, CVE-2026-33810, CVE-2026-3497, CVE-2026-34986, CVE-2026-39883, CVE-2026-4424, CVE-2026-44664, CVE-2026-44665, CVE-2026-4800, CVE-2026-5121