Readme for IBM Cloud Pak for Business Automation 25.0.0 IF003

Fix Readme

Abstract

The following document is for IBM Cloud Pak for Business Automation 25.0.0 IF003. It includes the CASE package download, installation information, and the list of APARs/Known Issues that are resolved in this interim fix.

Content

Readme file for:	IBM Cloud Pak® for Business Automation
Product Release:	25.0.0
Update Name:	25.0.0 IF003
Fix ID:	25.0.0-WS-CP4BA-IF003
Publication Date:	29 October 2025

Prerequisites and supersedes
Components impacted
Before installation
Installing the interim fix
Performing the necessary tasks after installation
Uninstalling
List of fixes
Known Limitations
Document change history

Prerequisites and supersedes

Supersedes all prior interim fixes for Cloud Pak for Business Automation 25.0.0.

Components impacted

General
Cloud Pak for Business Automation Operator
Automation Document Processing
Automation Decision Services
Business Automation Application
Business Automation Insights
Business Automation Navigator
Business Automation Studio
Business Automation Workflow including Automation Workstream Services
Enterprise Records
FileNet Content Manager
Operational Decision Manager
User Management Service
Workflow Process Service

Before installation

Ensure you take regular backups of any databases associated with the environment.
Ensure your operators are in a healthy state, before upgrading.
If one or more operators are failing, then it can prevent the system from completing an upgrade.
It is recommended to check a few of the important CR statuses to ensure there are not failures and the statuses appear ready for the various installed components. Check the status of the following CRs when they exist:

oc get icp4acluster -o yaml 
oc get content -o yaml
oc get Foundation -o yaml

Remove any image settings in CRs
If you used any individual image tag settings in your CRs, it could prevent the operator from updating the images to the appropriate version. Ensure you remove any of these settings when you upgrade. This doesn't apply to starter installation as it requires a new install.

Installing the interim fix

This interim fix contains the following version of Cloud Pak for Business Automation and Cloud Pak Foundational Services (CPFS):

Cloud Pak for Business Automation 25.0.0-IF003
Cloud Pak Foundational Services 4.16

Note: This interim fix only supports the Cloud Pak Foundational Services listed above. It is important that you deploy or upgrade Cloud Pak for Business Automation using the catalog sources in this readme document. If you have other Cloud Paks installed on the same OCP cluster, be sure to check the compatibility of the Cloud Pak Foundational Services versions listed above with other Cloud Paks' specifications.

Cloud Pak for Business Automation (CP4BA) 25.0.0 interim fixes are released to the v25.0 operator channel. Once the operators are upgraded, it triggers rolling updates for all the pods it manages to ensure they are updated to the appropriate version to match the operator.

NOTES :

Automation Document Processing is not supported for a CP4BA Starter Deployment with this interim fix.
Starting with this interim fix, Java 17 or a version newer is required and must be installed on the bastion host where the deployment scripts are executed before running either a fresh installation or an upgrade to this iFix. Users can specify a custom Java installation directory using the flag --java-path while executing the cp4a-deployment.sh script or cp4a-prerequisites.sh script.

Step 1: Download the installation and upgrade scripts

Download the 25.0.0-IF003 branch by using the following git clone command.
```
git clone -b 25.0.0-IF003 https://github.com/icp4a/cert-kubernetes.git
```

Step 2: Perform an online/offline fresh installation or an upgrade on an existing online/offline deployment.

Depending on the current setup and state of your existing environment, there are various actions that need to be taken. The following scenarios cover what actions might be needed for a particular setup.

For an upgrade scenario, these are the Cloud Pak foundational services migration modes supported -

Migration Mode	Support
Cluster-scoped to Namespace-scoped	Supported (This is the recommended approach if your current deployment is using cluster-scoped CPFs)
Namespace-scoped to Namespace-scoped	Supported (If your CPFs deployment is already namespace-scoped, then continue to remain at namespace-scoped)
Cluster-scoped to Cluster-scoped	Not Supported (Please follow the recommended upgrade from Cluster-scoped to Namespace-scoped for CPFs)
Cluster-scoped ("All namespaces") to Cluster-scoped ("All namespaces")	Supported ( There is no migration path from Cluster-scoped ("All namespaces") to Namespace-scoped )

Note: The recommended migration mode for an instance with cluster scoped Cloud Pak foundational services is to namespace scoped Cloud Pak foundational services.

Scenario 1: You are installing a Starter deployment online or have an existing online Starter deployment
Warning: If you have an existing Cloud Pak Foundation Services instance installed at the cluster scoped level or in the namespace where CP4BA is being installed, then it is not supported. The Starter deployment of CP4BA is only supported when deploying into a new namespace without CPFs.
Actions: Starter deployments do not support upgrades; however, you can use this interim fix content to perform a Starter deployment. To deploy a Starter deployment using the content of this interim fix, please see install a new Starter environment and use the installation scripts from the branch that you cloned above.
Scenario 2: You are installing online Production deployment
Warning: If you have an existing Cloud Pak Foundation Services instance installed at the cluster scoped level or in the namespace where CP4BA is being installed, then it is not supported. The Production deployment of CP4BA is only supported when deploying into a new namespace without CPFs.
Actions: To deploy an online Production deployment without using a local registry, please follow steps in install a new online Production environment and use the installation scripts from the branch that you cloned above.
Scenario 3: You are installing offline/airgap Production deployment
Warning: If you have an existing Cloud Pak Foundation Services instance installed at the cluster scoped level or in the namespace where CP4BA is being installed, then it is not supported. The Production deployment of CP4BA is only supported when deploying into a new namespace without CPFs.
Note: As prerequisites for this scenario, you must follow steps here to set up the bastion host to mirror images to the registry and further to set up the private registry. The mirroring of images can be completed using "oc mirror" for the mirroring images process. If you are looking to install only a set of capabilities then you can make use of filters listed in Table 1 so that you can only download the specific set of images that you require.
Actions:
1. To deploy an airgap/offline Production deployment, find mirror file cp4ba-case-to-be-mirrored-25.0.0-IF003.txt for this interim fix from the branch that you cloned above under the scripts/airgap directory. Execute this command from your bastion host to download the CASE files.
```
oc ibm-pak get -c file://(absolute path to file)/cp4ba-case-to-be-mirrored-25.0.0-IF003.txt
```
  The absolute path to file needs to be a path starting from "/". For example, "/opt".
2. You will need to mirror the images associated with the new cp4ba-case-to-be-mirrored-25.0.0-IF003.txt mirror file.
```
export CASE_NAME=ibm-cp-automation
export CASE_VERSION=25.0.3
export CASE_INVENTORY_SETUP=cp4aOperatorSetup
export TARGET_REGISTRY=<target-registry>
export NAMESPACE=<cp4ba_namespace_name>
```
  Follow the instructions for either mirroring option in Mirroring images to the private registry using the new CASE version associated with this interim fix.
3. Login to the cluster and go to namespace for the operator from the bastion host.
```
oc login https://<CLUSTERIP>:<port> -u <ADMINISTRATOR>
oc project ${NAMESPACE}
```
4. From your bastion host, install the catalog sources and operators using the steps listed in Install Catalog Source and Operators using cluster admin script.
5. Follow the remaining steps from Question 6 listed here to complete the installations of offline/airgap Production deployment.
Scenario 4: Your installed Production deployment version is 24.0.1 IF001 and older
Warning:
If your production deployment version is older than 24.0.1-IF001, please follow instructions in Knowledge Center to upgrade to 24.0.1-IF002 first and follow instructions to upgrade from 24.0.1-IF002 to 25.0.0-IFixes.
Actions:
Follow the supported upgrading path documented in Upgrading CP4BA to 24.0.1. After you have successfully upgraded the deployment to 24.0.1-IF002, you may proceed to follow Scenario 5 below.
Scenario 5: Your installed Production deployment version is 24.0.1 IF002 and newer
Warning:
All instructions to download the installation and upgrade scripts in the Knowledge Center links referenced below can be ignored. Instead use the installation and upgrade scripts downloaded in Step 1
Actions:
For online upgrade, follow the upgrade instructions documented in Upgrading CP4BA multi-pattern clusters from 24.0.1 in online environment.
For offline upgrade, you must first complete the prerequisites by following steps here to set up the bastion host to mirror images to the registry and further to set up the private registry. The mirroring of images can be completed using "oc mirror" for the mirroring images process manually  or using"oc mirror" for the mirroring images process by script . Once the mirroring of images is completed, follow the upgrade instructions documented in Upgrading CP4BA multi-pattern clusters from 24.0.1 in online environment.
Scenario 6: Your installed Production deployment is 25.0.0 GA or newer.
Note:
For a dedicated deployment or namespace scoped deployment, the value for < CP4BA Namespace > should be the namespace where all IBM Cloud Pak foundational services/CP4BA Operators and Services are deployed. If the CP4BA Operators and Services are deployed in different namespaces( separation of duties), the value for < CP4BA Namespace > should be the namespace where all IBM Cloud Pak foundational services/CP4BA Operators are deployed in.
Warning:
For a CP4BA Deployment with BAI ( Business Automation Insights ) selected as an optional component, it is recommended to create BAI savepoints before starting the upgrade process to this interim fix. For Flink event processing to resume from its previous state, savepoints are required to be created before the upgrade and specified in the updated CR. BAI savepoints can be created by following the below steps.
- Retrieve the name of the InsightsEngine custom resource file.
```
InsightsEngine_CR=$(kubectl get InsightsEngine --no-headers --ignore-not-found -n <CP4BA-Namespace> -o name)
```
  Retrieve and export the below details.
```
export MANAGEMENT_URL=$(kubectl get ${InsightsEngine_CR} --no-headers --ignore-not-found -n <CP4BA Namespace> -o jsonpath='{.status.components.management.endpoints[?(@.scope=="External")].uri}')
export MANAGEMENT_AUTH_SECRET=$(kubectl get ${InsightsEngine_CR} --no-headers --ignore-not-found -n <CP4BA Namespace> -o jsonpath='{.status.components.management.endpoints[?(@.scope=="External")].authentication.secret.secretName}')
export MANAGEMENT_USERNAME=$(kubectl get secret ${MANAGEMENT_AUTH_SECRET} --no-headers --ignore-not-found -n <CP4BA Namespace> -o jsonpath='{.data.username}' | base64 -d)
export MANAGEMENT_PASSWORD=$(kubectl get secret ${MANAGEMENT_AUTH_SECRET} --no-headers --ignore-not-found -n <CP4BA Namespace> -o jsonpath='{.data.password}' | base64 -d)
```
  Create BAI savepoints and store them in a temporary file called bai.json.
```
curl -X POST -k -u ${MANAGEMENT_USERNAME}:${MANAGEMENT_PASSWORD} "${MANAGEMENT_URL}/api/v1/processing/jobs/savepoints" -o ./bai.json
```
  Scale down the CP4BA and Insights Engine Operator.
  oc scale --replicas=0 deployment ibm-cp4a-operator oc scale --replicas=0 deployment ibm-insights-engine-operator
- Retrieve the recovery path locations for each BAI component for which BAI savepoints are created from ./bai.json and update the bai_configuration section of the custom resource file. For Example: If there is a BAI savepoint being created for navigator component, then the updated custom resource file should have the below configuration.
```
bai_configuration:
  navigator:
    recovery_path: /mnt/pv/savepoints/dba/bai-navigator/savepoint-fb88f4-42027046b73b
  ... 
  # Add recovery_path for all other components
```
- Once the upgrade has been completed, make sure to remove all instances of the recovery_path parameters from the updated custom resource file.
Actions:
From the branch that you cloned above navigate to the scripts directory and perform the following steps to upgrade the CP4BA operators and deployment.
1. Upgrade the CP4BA operators.
  - Warning:
    The script with the upgradeOperator option will scale the CP4BA Operators down to zero. You must execute the script with the upgradeDeploymentStatus mode to scale them back in.
  - Actions:
    Run the cp4a-deployment.sh script with the upgradeOperator option to upgrade the IBM Cloud Pak foundational services/CP4BA operators:
```
./scripts/cp4a-deployment.sh -m upgradeOperator -n <CP4BA Namespace>
```
2. Wait for the operators to complete their upgrades.
  By default all subscriptions are set to automatic, but if you have any subscriptions set to manual then you need to approve any pending InstallPlans.
  Use the below command to see the current status of the install plans.
```
oc get installPlan
```
  The upgrade will be blocked, if any of the needed InstallPlans are not approved. It is not recommended to set subscriptions to manual as this makes the upgrade more error prone.
3. You can use the following scripts to check the status of the upgrades.
  - Warning:
    The script will scale the CP4BA deployments down to zero. You must execute the cp4a-deployment.sh script with upgradeDeploymentStatus option to scale them back up.
  - Actions:
    [OPTIONAL] Run the cp4a-deployment.sh script with upgradeOperatorStatus option to check that the upgrade of the CP4BA operator and its dependencies is successful:
```
./scripts/cp4a-deployment.sh -m upgradeOperatorStatus -n <CP4BA Namespace>
```
4. Start up the upgraded CP4BA Operators.
  Run the cp4a-deployment.sh script with upgradeDeploymentStatus option to check that the upgrade of the CP4BA deployment is successful:
```
./scripts/cp4a-deployment.sh -m upgradeDeploymentStatus -n <CP4BA Namespace>
```
  Note: If you are using the P8BPMREST CPE end point, you must wait for the CPE components status to display "Done" and then execute the below command to make it accessible.
```
kubectl patch zenextension <CUSTOM_RESOURCE_FILENAME>-cpe-zen-extension -n <CP4BA NAMESPACE> --type=merge -p '{"metadata": {"annotations": {"checksum_cpe_ips": "0"}}}'
```

Scenario 7: Your installed Production deployment is 25.0.0 GA or newer and using airgap/offline.
Note:
As prerequisites for this scenario, you must follow steps here to set up the bastion host to mirror images to the registry and further to set up the private registry.
For a dedicated deployment or namespace scoped deployment, the value for < CP4BA Namespace > should be the namespace where all IBM Cloud Pak foundational services/CP4BA Operators and Services are deployed. If the CP4BA Operators and Services are deployed in different namespaces( separation of duties), the value for < CP4BA Namespace > should be the namespace where all IBM Cloud Pak foundational services/CP4BA Operators are deployed in.
Warning:
For a CP4BA Deployment with BAI ( Business Automation Insights ) selected as an optional component, it is recommended to create BAI savepoints before starting the upgrade process to this interim fix. For Flink event processing to resume from its previous state, savepoints are required to be created before the upgrade and specified in the updated CR. BAI savepoints can be created by following the below steps.
- Retrieve the name of the InsightsEngine custom resource file.
```
InsightsEngine_CR=$(kubectl get InsightsEngine --no-headers --ignore-not-found -n <CP4BA-Namespace> -o name)
```
  Retrieve and export the below details.
```
export MANAGEMENT_URL=$(kubectl get ${InsightsEngine_CR} --no-headers --ignore-not-found -n <CP4BA Namespace> -o jsonpath='{.status.components.management.endpoints[?(@.scope=="External")].uri}')
export MANAGEMENT_AUTH_SECRET=$(kubectl get ${InsightsEngine_CR} --no-headers --ignore-not-found -n <CP4BA Namespace> -o jsonpath='{.status.components.management.endpoints[?(@.scope=="External")].authentication.secret.secretName}')
export MANAGEMENT_USERNAME=$(kubectl get secret ${MANAGEMENT_AUTH_SECRET} --no-headers --ignore-not-found -n <CP4BA Namespace> -o jsonpath='{.data.username}' | base64 -d)
export MANAGEMENT_PASSWORD=$(kubectl get secret ${MANAGEMENT_AUTH_SECRET} --no-headers --ignore-not-found -n <CP4BA Namespace> -o jsonpath='{.data.password}' | base64 -d)
```
  Create BAI savepoints and store them in a temporary file called bai.json.
```
curl -X POST -k -u ${MANAGEMENT_USERNAME}:${MANAGEMENT_PASSWORD} "${MANAGEMENT_URL}/api/v1/processing/jobs/savepoints" -o ./bai.json
```
  Scale down the CP4BA and Insights Engine Operator.
  oc scale --replicas=0 deployment ibm-cp4a-operator oc scale --replicas=0 deployment ibm-insights-engine-operator
- Retrieve the recovery path locations for each BAI component for which BAI savepoints are created from ./bai.json and update the bai_configuration section of the custom resource file. For Example: If there is a BAI savepoint being created for navigator component, then the updated custom resource file should have the below configuration.
```
bai_configuration:
  navigator:
    recovery_path: /mnt/pv/savepoints/dba/bai-navigator/savepoint-fb88f4-42027046b73b
  ... 
  # Add recovery_path for all other components
```
- Once the upgrade has been completed, make sure to remove all instances of the recovery_path parameters from the updated custom resource file.
Actions:
Perform the following steps and then the upgrade of operators and deployments will start.
1. To upgrade an airgap/offline Production deployment, find mirror file cp4ba-case-to-be-mirrored-25.0.0-IF003.txt for this interim fix from the branch that you cloned above under the scripts/airgap directory. Execute this command from your bastion host to download the CASE files:
```
oc ibm-pak get -c file://(absolute path to file)/cp4ba-case-to-be-mirrored-25.0.0-IF003.txt
```
  The (absolute path to file) needs to be a path starting from "/". For example, "/opt".
2. You will need to mirror the images associated with the new cp4ba-case-to-be-mirrored-25.0.3.txt mirror file.
```
export CASE_NAME=ibm-cp-automation
export CASE_VERSION=25.0.3
export CASE_INVENTORY_SETUP=cp4aOperatorSetup
export TARGET_REGISTRY=<target-registry>
export NAMESPACE=<cp4ba_namespace_name>
```
  Follow the instructions for either mirroring option in Mirroring images to the private registry using the new CASE version associated with this interim fix. If you are looking to install only a set of capabilities then you can make use of filters listed in Table 1 so that you can only download the specific set of images that you require.
3. From the branch that you cloned above navigate to the scripts directory and perform the following steps to upgrade the CP4BA operators.
  - Warning:
    The script with the upgradeOperator option will scale the CP4BA Operators down to zero. You must execute the script with the upgradeDeploymentStatus mode to scale them back in.
  - Actions:
    Run the cp4a-deployment.sh script with the upgradeOperator option to upgrade the IBM Cloud Pak foundational services/CP4BA operators:
```
./scripts/cp4a-deployment.sh -m upgradeOperator -n <CP4BA Namespace>
```
4. Wait for the operators to complete their upgrades.
  By default all subscriptions are set to automatic, but if you have any subscriptions set to manual then you need to approve any pending InstallPlans.
  Use the below command to see the current status of the install plans.
```
oc get installPlan
```
  The upgrade will be blocked, if any of the needed InstallPlans are not approved. It is not recommended to set subscriptions to manual as this makes the upgrade more error prone.
5. You can use the following scripts to check the status of the upgrades.
  - Warning:
    The script will scale the CP4BA deployments down to zero. You must execute the cp4a-deployment.sh script with upgradeDeploymentStatus option to scale them back up.
  - Actions:
    [OPTIONAL] Run the cp4a-deployment.sh script with upgradeOperatorStatus option to check that the upgrade of the CP4BA operator and its dependencies is successful:
    ./scripts/cp4a-deployment.sh -m upgradeOperatorStatus -n <CP4BA Namespace>
6. Start up the upgraded CP4BA Operators.
  Run the cp4a-deployment.sh script with upgradeDeploymentStatus option to check that the upgrade of the CP4BA deployment is successful:
```
./scripts/cp4a-deployment.sh -m upgradeDeploymentStatus -n <CP4BA Namespace>
```
  Note: If you are using the P8BPMREST CPE end point, you must wait for the CPE components status to display "Done" and then execute the below command to make it accessible.
```
kubectl patch zenextension <CUSTOM_RESOURCE_FILENAME>-cpe-zen-extension -n <CP4BA NAMESPACE> --type=merge -p '{"metadata": {"annotations": {"checksum_cpe_ips": "0"}}}'
```

Performing the necessary tasks after installation

a. Review the installation

It is recommended that you review the CR yaml status section and operator logs after the upgrade to ensure there are no failures preventing your pods from upgrading.

oc get icp4acluster icp4adeploy -o yaml > CP4BAconfig.yaml
oc logs deployment/ibm-cp4a-operator -c operator > operator.log

If you are interested in verifying the expected image digest for a particular image, then you can review the ibm-cp-automation\inventory\cp4aOperatorSdk\resources.yaml file in the CASE package. This file has a listing of the images managed by the CP4BA operator and their expected digest for this particular interim fix level.

Uninstalling

There is no procedure to uninstall the interim fix.

List of Fixes

APARs/Known Issues fixed by this interim fix are listed in the following tables.

The columns are defined as follows:

Column title	Column description
APAR/Known Issue	The defect number
Title	A short description of the defect
Sec.	A mark indicates a defect related to security
Cont.	A mark indicates a defect specific to the Cloud Pak integration of the component
B.I.	A mark indicates the fix has a business impact. Details are found in the title column or the APAR/Known Issue document

General
Cloud Pak for Business Automation Operator
Automation Document Processing
Automation Decision Services
Business Automation Application
Business Automation Insights
Business Automation Navigator
Business Automation Studio
Business Automation Workflow including Automation Workstream Services
Enterprise Records
FileNet Content Manager
Operational Decision Manager
User Management Service
Workflow Process Service

General

Known Issue	Title	Sec.	Cont.	B.I.
N/A	Cloud Pak for Business Automation delivers container images that include operating system level and other open source libraries. Vulnerabilities (CVEs) for these libraries are published regularly. This interim fix includes fixes for these libraries to address: CVE-2007-5686,CVE-2010-4756,CVE-2011-3374,CVE-2011-3389,CVE-2011-4116,CVE-2011-4969,CVE-2012-2663,CVE-2012-6708,CVE-2013-4392,CVE-2014-6071,CVE-2015-3276,CVE-2015-9251,CVE-2016-2781,CVE-2017-14159,CVE-2017-17740,CVE-2017-18018,CVE-2018-20796,CVE-2018-5709,CVE-2018-6829,CVE-2019-1010022,CVE-2019-1010023,CVE-2019-1010024,CVE-2019-1010025,CVE-2019-11358,CVE-2019-9192,CVE-2020-11022,CVE-2020-11023,CVE-2020-15138,CVE-2020-15719,CVE-2020-19625,CVE-2020-7656,CVE-2021-24112,CVE-2021-45346,CVE-2022-0563,CVE-2022-30241,CVE-2023-2953,CVE-2023-31437,CVE-2023-31438,CVE-2023-31439,CVE-2023-31486,CVE-2023-36807,CVE-2023-36810,CVE-2023-4016,CVE-2023-45853,CVE-2023-46250,CVE-2023-52355,CVE-2023-52356,CVE-2023-52426,CVE-2024-10041,CVE-2024-1013,CVE-2024-10977,CVE-2024-21208,CVE-2024-21210,CVE-2024-21217,CVE-2024-21235,CVE-2024-2236,CVE-2024-22365,CVE-2024-25621,CVE-2024-26458,CVE-2024-26461,CVE-2024-28757,CVE-2024-28863,CVE-2024-35195,CVE-2024-3651,CVE-2024-37891,CVE-2024-39689,CVE-2024-40635,CVE-2024-45336,CVE-2024-45341,CVE-2024-47081,CVE-2024-47554,CVE-2024-55459,CVE-2024-56433,CVE-2024-57699,CVE-2024-58251,CVE-2025-0913,CVE-2025-11226,CVE-2025-11579,CVE-2025-12058,CVE-2025-12060,CVE-2025-12084,CVE-2025-12817,CVE-2025-1352,CVE-2025-1365,CVE-2025-13699,CVE-2025-1372,CVE-2025-1550,CVE-2025-22866,CVE-2025-22868,CVE-2025-22869,CVE-2025-22870,CVE-2025-22871,CVE-2025-22872,CVE-2025-27587,CVE-2025-29088,CVE-2025-29481,CVE-2025-32988,CVE-2025-32989,CVE-2025-32990,CVE-2025-40777,CVE-2025-40778,CVE-2025-40780,CVE-2025-46394,CVE-2025-4673,CVE-2025-47906,CVE-2025-47907,CVE-2025-48976,CVE-2025-52881,CVE-2025-53864,CVE-2025-53905,CVE-2025-53906,CVE-2025-54410,CVE-2025-55197,CVE-2025-56200,CVE-2025-6020,CVE-2025-6141,CVE-2025-62707,CVE-2025-62708,CVE-2025-6297,CVE-2025-6395,CVE-2025-64329,CVE-2025-6965,CVE-2025-7709,CVE-2025-8176,CVE-2025-8194,CVE-2025-8677,CVE-2025-8732,CVE-2025-8747,CVE-2025-9820,CVE-2025-9900,CVE-2025-9906,RHSA-2025:16116,RHSA-2025:20559,RHSA-2025:20801,RHSA-2025:20936,RHSA-2025:20945,RHSA-2025:20956,RHSA-2025:21110,RHSA-2025:21111 Previous interim fixes have included fixes which are also addressed with this interim fix. Consult the Related links section for readmes of previous interim fixes, at the bottom of this document.

Cloud Pak for Business Automation Operator

Known Issue	Title	Sec.	Cont.	B.I.
DT455329	Honour Purge Policy Liberty Setting from the Custom Resource file.
DT456607	Syntax update for retrieving subscription details while executing the upgrade scripts for CP4BA

Automation Document Processing

Known Issue	Title	Sec.	Cont.	B.I.
DT459550	Spbackend pods unable to connect to DB when using PostgreSQL client authentication		X	X
DT459075	Gitgateway pod cannot connect to database		X	X

Automation Decision Services

Known Issue	Title	Sec.	Cont.	B.I.
DT458732	Error 500 opening or deploying decision service
DT456609	Decision Model reference list is not sorted
DT456062	UI Regression: Colour Formatting Missing in Column Output After Upgrade to ADS 24.0.0
DT458145	Missing Pod Disruption Budgets management in ADS components
DT45 3399	Add button in data model editor displays triplicate lines

Business Automation Application

Known Issue	Title	Sec.	Cont.	B.I.
DT456476	BatchUpdateExceptions are seen when indexing tasks which have been created by Business Automation Workflow 19.0.0.1 or older are not updated

Business Automation Insights

Known Issue	Title	Sec.	Cont.	B.I.
N/A	N/A

Business Automation Navigator

Known Issue	Title	Sec.	Cont.	B.I.
	Please see Business Automation Navigator Fix List APARs for Cloud Pak for Business Automation technote

Business Automation Studio

Known Issue	Title	Sec.
DT446922	CVE-2025-48976 - DoS vulnerability in commons-fileupload affects IBM Business Automation Workflow	X
DT447031	CVE-2025-36172 Cross-Site Scripting vulnerability in Case Client	X
DT451598	Security vulnerability in axios javascript Library affects IBM Process Designer, IBM Workflow center and IBM Business Automation Studio	X
DT457061	Server side Request Forgery affects IBM Business Automation Workflow and Cloud Pak for Business Automation	X
DT456476	BatchUpdateExceptions are seen when indexing tasks which have been created by Business Automation Workflow 19.0.0.1 or older are not updated

Business Automation Workflow including Automation Workstream Services

Known Issue	Title	Sec.
DT446922	CVE-2025-48976 - DoS vulnerability in commons-fileupload affects IBM Business Automation Workflow	X
DT447031	CVE-2025-36172 Cross-Site Scripting vulnerability in Case Client	X
DT457061	Server side Request Forgery affects IBM Business Automation Workflow and Cloud Pak for Business Automation	X
DT419413	[DOC] The Content Object created for a re-use case property has a broken reference to the associated choice list in IBM Web Process Designer
DT436090	- CWLLG2156W: The database connection pool size (200) of the Workflow Server data source might be too small tuning queue capacity and cm_max_pool_size (CP4BA)
DT445873	- Load on IM pods spike when Process Admin Console user and group search is performed
DT450088	After upgrading from ICM 5.3.3 to CP4BA , error message FNRCE0066E: E_UNEXPECTED_EXCEPTION: Failed to update case properties into PFS. : jms/TWClientConnectionFactory is seen
DT451052	Process Instances cannot be deleted due to incorrect CAN_DELETE_INSTANCE value
DT453431	Snapshot status not getting updated in Process Admin console
DT454846	When updating an existing document to newer version(s) of the document having a different mime type, the mime type of the document always reflects the mime type of the first version
DT455683	When clicking on a ToDo task in the IBM Business Automation Workflow Case Client, the message Loading... appears but Task is not opened. Error in console: Uncaught TypeError: can't access property set, casePropController is undefined.
DT456476	BatchUpdateExceptions are seen when indexing tasks which have been created by Business Automation Workflow 19.0.0.1 or older are not updated
DT457050	Process Inspector failure due to Jackson 20 MB String limit in execution tree
DT457084	db-init-job failing due to permissions when attempting to migrate process instances on 24.0.1

Enterprise Records

Known Issue	Title	Sec.	Cont.	B.I.
N/A	N/A

FileNet Content Manager

APAR	Title	Sec.	Cont.	B.I.
	See FileNet Content Manager Release Fix List APARs for IBM Cloud Pak for Business Automation technote

Operational Decision Manager (based on ODM-9.5.0.0-IF011)

Known Issue	Title	Sec.	Cont.	B.I.
DT454896	UNABLE TO SELECT A DATE IN THE DECISION TABLE EDITOR IN RULE DESIGNER
DT452944	CLASSCASTEXCEPTION WHEN USING XSD:TIME IN XOM MAPPED TO ILRTIME IN BOM
DT425576	DECISION SERVICE PROJECT HEADLESS BUILD FAILS WITH NPE
DT454134	CODE INJECTION IN THE SIMULATION FIELDS
DT454103	NON-ADMIN USERS UNABLE TO LOGIN DECISION CENTER
DT454242	CODE INJECTION IN REPORT FORMATS KPI EDITOR
DT455504	COMPARE VERSIONS PAGE DOES NOT LOAD RESULTS
DT453050	DECISION CENTER SIMULATION PRINT FEATURE IS NOT WORKING
DT453379	UNABLE TO VIEW DEPLOYMENT REPORT AFTER CLEANUP
DT451968	THE DIAGNOSTIC LAST VALUE IN PARENT BRANCH TAKES FOREVER
DT456707	RTSUSER CANNOT EXPORT SNAPSHOT FROM REST-API
DT457400	RTSUSERS ARE UNABLE TO LOGIN DECISION CENTER
DT456480	DECISION SERVICE WITH INTERCEPTOR ENABLED LEAKS MANAGEMENT SESSION

User Management Service

Known Issue	Title	Sec.	Cont.	B.I.
N/A	N/A

Workflow Process Service

Known Issue	Title	Sec.	Cont.	B.I.
DT451052	Process Instances cannot be deleted due to incorrect CAN_DELETE_INSTANCE value
DT453431	Snapshot status not getting updated in Process Admin console
DT456413	The Workflow Process Service datasave PVC should allow for RWX PV to be used, not just RWO
DT456476	BatchUpdateExceptions are seen when indexing tasks which have been created by Business Automation Workflow 19.0.0.1 or older are not updated
DT457050	Process Inspector failure due to Jackson 20 MB String limit in execution tree

Known Limitations

Cloud Pak for Business Automation 25.0.x Known Issues

Known issues in IBM Cloud Pak foundational services

Document change history

18 December 2025: Initial publish.

Related Information

[Supersedes 25.0.0-IF002] Readme for IBM Cloud Pak for Business Automation 25.0…

[Supersedes 25.0.0-IF001] Readme for IBM Cloud Pak for Business Automation 25.0…

Fix list for Cloud Pak for Business Automation 25.0.0

Cloud Pak for Business Automation Interim fix download

Cloud Pak for Business Automation Fix list

[{"Type":"MASTER","Line of Business":{"code":"LOB76","label":"Data Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSBYVB","label":"IBM Cloud Pak for Business Automation"},"ARM Category":[{"code":"a8m0z0000001gWWAAY","label":"Other-\u003ECloudPak4Automation Platform"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"25.0.0"}]

Tips