IBM Support

IBM Cloud Pak for Business Automation 23.0.x Known Limitations

General Page

This web page provides a list of known limitations in IBM Cloud Pak® for Business Automation 23.0.x. Workarounds are provided where possible.

​

IBM Cloud Pak for Business Automation 23.0.2

The following limitations pertain to IBM cloud pak for Automation 23.0.2.  They are subject to change between releases. You can find additional limitations in the product documentation at IBM Cloud Pak for Automation 23.0.2: Known Limitations.  
 

 Table of contents

 
IssueDescription
Version
The steps and links for backing up and restoring IBM Cloud Pak foundational services are not available in the IBM Cloud Pak for Business Automation documentation. The IBM Cloud Pak for Business Automation disaster recovery solution requires backing up and restoring both IBM Cloud Pak for Business Automation components and IBM Cloud Pak foundational services.Symptom: You cannot back up and restore IBM Cloud Pak foundational services by using IBM Documentation.



Cause: No further information is available.


Solution: For assistance in backing up and restoring IBM Cloud Pak foundational services, contact the IBM Cloud Pak foundational services team.
 		23.0.2

Back to top

 
IssueDescription
Version
Default self-signed certificates for CPD route will not be renewed automatically when expired
Symptom:  Customer is seeing an expired certificate when connecting via the CPD route. This is causing issues with CP4BA as well such as when some expected services are hitting the CPD Route URL and are seeing the expired certificate.

Cause:  In CP4BA, if you are using the default CPD route certificate, it will expire after 90 days. The certificate stored in the iaf-system-automationui-aui-zen-cert secret will be updated by the cert manager and will be automatically renewed. However, the route will not be updated when that secret is changed.

Solution:
If you manually edit the ZenService CR, it will trigger the route to be updated with the secret. Hence if you do two quick updates to change the secret in the ZenService as shown here:
  •  oc patch ZenService iaf-zen-cpdservice --type='json' -p='[\{"op": "add", "path": "/spec/zenCustomRoute","value":{"route_secret":"dummy-value","route_reencrypt":true}}]' -n ${CP4BA_AUTO_NAMESPACE}
  •   oc patch ZenService iaf-zen-cpdservice --type='json' -p='[\{"op": "add", "path": "/spec/zenCustomRoute","value":{"route_secret":"iaf-system-automationui-aui-zen-cert","route_reencrypt":true}}]' -n ${CP4BA_AUTO_NAMESPACE}
then the CPD route certificate will be updated.
23.0.2

Back to top

 
LimitationDescription
Version
The user cannot use the Test button during the table data annotation in Automation Document Processing (ADP) Designer.Symptom: In the ADP Designer, the user annotates the table data and clicks the Test button. A blank page is displayed instead of the table (rows and columns) that is based on the new annotations.

Cause: A required parameter was missed in the spbackend pod that causes the Test button to not work.


Solution: Upgrade to the upcoming fixpack 23.0.2 IF001.		23.0.2

Back to top

LimitationDescription
Version
The user must manually install IER plug-in.
Symptom: When trying to download and load the IER plug-in into IBM Content Navigator, you will be unable to do so.  

Solution: You must manually place the plugin in a location visible to IBM Content Navigator by following the steps mentioned in the technote here.
23.0.2

Back to top

​IBM Business Automation Navigator

LimitationDescription
Version
None reported
 
23.0.2

Back to top

 

IBM Business Automation Workflow 

LimitationDescription
Version
If you use the case feature of Business Automation Workflow, BAW and CPE "replica" sizes must be set to 1.
 
Symptom:
There is a potential risk of a database deadlock on the Content Platform Engine side, and this deadlock causes the Business Automation Workflow and Content Platform Engine integration code to fail.
 
Solution:
Do not set the value for the BAW and CPE "replica" size to more than 1 in the CP4BA custom resource (CR) file. The issue is fixed in CP4BA 24.0.0.IF007.
23.0.2
Case business objects are not supported as search criteria for related case searchesSymptom: Even though case business objects are defined in the Case Search view, the case business objects are not listed as search properties for related case searches.

Solution: The use of case business objects in related case searches is currently unsupported.		23.0.2

Back to top

LimitationDescription
Version

Under certain conditions, when deploying in Starter mode, Operational Decision Manager's dbserver pod might show two pods, instead of just one, and crash.

Solution:
Force the usage of a block storage class in your custom resource by editing the following value:
odm_configuration:
  internalDatabase:
    persistence:
      storageClassName: <name of your block storage class>
 
23.0.2

Back to top

LimitationDescription
Version
None reported
 
23.0.2

Back to top

 

IBM Automation Workstream Services

LimitationDescription
Version
No new limitations reported
 
23.0.2

Back to top

 

IBM Automation Decision Services

LimitationDescription
Version
Incorrect download path for engine-compact-runtime-3.1.9.jar 

Symptom: The engine-compact-runtime-3.1.9.jar file is currently unavailable for downloading due to a typographical error in its download path.

The engine-compact-runtime-3.1.9.jar redirects to 'engine-compact-runtime/3.1.9/engine-compact-runtime-3.1.6.jar'


Solution: Manually set the desired version for engine-compact-runtime-<version>.jar in the download path.

For example: engine-compact-runtime/3.1.9/engine-compact-runtime-3.1.9.jar

23.0.2

Back to top

​ 
 

IBM Content collector for SAP Applications

LimitationDescription
Version
Special characters in Keystore password not supported.Symptom: ICCSAP deployment fails when special characters are specified in secrets file ibm-iccsap-secret.

Cause: Special characters are not yet supported in the Keystore password.

Solution: Ensure that the keystorePassword in the ibm-iccsap-secret does not contain any special characters until this issue is fixed. This issue will be fixed in a future iFix for the release.		23.0.2

Back to top

 
 
 

​

IBM Cloud Pak for Business Automation 23.0.1

The following limitations pertain to IBM Cloud Pak for Automation 23.0.1. They are subject to change between releases. You can find additional limitations in the product documentation at IBM Cloud Pak for Automation 23.0.1: Known limitations.

 Table of contents

 
IssueDescription
Version
The steps and links for backing up and restoring IBM Cloud Pak foundational services are not available in the IBM Cloud Pak for Business Automation documentation. The IBM Cloud Pak for Business Automation disaster recovery solution requires backing up and restoring both IBM Cloud Pak for Business Automation components and IBM Cloud Pak foundational services.Symptom: You cannot back up and restore IBM Cloud Pak foundational services by using IBM Documentation.


Cause: No further information is available.


Solution: For assistance in backing up and restoring IBM Cloud Pak foundational services, contact the IBM Cloud Pak foundational services team.
 		23.0.1

Back to top

 
IssueDescription
Version

The upgrade of foundational services is not supported for 23.0.1 in the following cases:

  • You have a cluster-scoped foundational services instance and want to upgrade to a namespace-scoped instance. You probably have a cluster-scoped instance only in the following circumstances:
    • You installed Cloud Pak for Business Automation 21.0.3 GA or up to 21.0.3-IF018, and then you upgraded incrementally to 22.0.2 (21.0.3 → 22.0.1 → 22.0.2).
    • You installed Cloud Pak for Business Automation 22.0.1 GA or 22.0.1-IF001, and then you upgraded to 22.0.2.
  • You have a cluster-scoped foundational services instance and you want to continue to use a cluster-scoped foundational services instance in 23.0.1.
  • You have a namespace-scoped foundational services instance and you want to install CP4BA in a different namespace.
An upcoming release is planned to support an upgrade of a CP4BA deployment that uses a cluster-scoped foundational services instance to a namespace-scoped instance. Remember, you might have a cluster-scoped instance if you originally installed a deployment before CP4BA 21.0.3-IF019, or you installed your CP4BA 22.0.2 deployment from the OCP console without creating a common-service-maps ConfigMap. If you do have this type of deployment, it is recommended that you wait for the new upgrade support.23.0.1

The documentation Installing Rule Designer shows the wrong version Eclipse.

The documentation shows Eclipse 2020.06. It should show Eclipse 2022.06.23.0.1
The URL to get product entitlement key is incorrect when running deployment scriptsSymptom:The link will take to IBM Cloud Paks documentation instead of the instructions to generate entitlement key.


Cause:The presented URL (https://www.ibm.com/docs/en/cloud-paks/cp-biz-automation/23.0.1/com.ibm.dba.install/op_topics/tsk_images_enterp_entitled.html) is incorrect


Solution:Deployment scripts will be updated in the upcoming iFix.Here is the correct URL for instructions to generate product entitlement key. https://www.ibm.com/docs/en/cloud-paks/cp-biz-automation/23.0.1?topic=deployment-getting-access-images-from-public-entitled-registry
 		23.0.1

Back to top

 
LimitationDescription
Version
The transition from TensorFlow V1 to TensorFlow v2 Object Detection API result in an increase in training time for Data-extraction training . This limitation manifests as a noticeable slowdown in the training processSymptom:
1. Slower training speed: After the migration from Tensorflow V1 to Tensorflow  V2, Users  experience a significant increase in training time.
2. Decreased throughput: The training process take longer to converge, resulting in reduced throughput and slower model development.

Cause:
1. Changes in the architecture and implementation: TensorFlow v2 introduced significant architectural changes and improvements compared to v1. These changes required modifications in the training pipeline which  impacted the overall training time.
2. Optimizations and feature updates: TensorFlow v2 incorporates various optimizations and feature updates that  improve the overall performance and functionality of the framework. However, these changes require additional computational resources, leading to increased training time.

Solution:
Additional computational resources can help in reducing the training time.		23.0.1
Submitting low-quality documents (skewed, rotated, blurry, and so on) might cause the OCR engine 2 runtime pod to exceed the allotted memory allocation and restart. When that occurs, the status of the document that is being processed is marked as ‘Error’. After the pod restarts, the OCR engine 2 runtime pod takes a few minutes or so to initialize.
Symptom:
1.  Documents fail to process, returning a status of Error.
2.  The wdu-runtime pod restarts.
 
Cause:
Repeated memory requests lead to a situation where there is not sufficient memory to process the document.  This condition triggers a restart of the wdu-runtime pod.  Any document currently processing with the wdu-runtime pod at the time of failure causes the document to fail.
 
Solution:
Wait for the wdu-runtime pod to return to a running and ready state, then resubmit the documents.  Remove low-quality documents that repeatedly cause this problem.
 
If the failure happens frequently enough, increasing the wdu-runtime pod memory limit alleviates the failure.
ca_configuration:
  wduruntime:
    resources:
      limits:
        memory: "12Gi"
 
 

Back to top


Cause:
CPFS team is investigating root of issue.

Solution:
  1. User may instead use the Automatic Provision option
  2. For more details about regarding 'Provisioning on Demand', see the following topic. 
LimitationDescription
Version
You cannot connect to the IBM Enterprise Records desktop.
Symptom:
When trying to access the IBM Enterprise Records desktop, an error message says that you cannot connect to the web client.
The log also shows that an exception was thrown "java.lang.NoClassDefFoundError: org.apache.xerces.xni.parser.XMLEntityResolver".

Cause:
After moving to Java 11, IERApplicationPlugin.jar is unable to resolve the path to XercesImpl.jar in the ICN container.

Solution:
  1. Download the ier-library.xml file from https://github.com/ibm-ecm/ier-samples.
  2. Copy the ier-jars.xml file to the ICN container shared configuration folder /opt/ibm/wlp/usr/servers/defaultServer/configDropins/overrides.
  3. In the shared configuration folder, create a folder named ier-jars. Then, copy the xercesImpl.jar file from <ier_on-prem_installation>\API\JARM to the ier-jars folder.
  4. Restart the ICN pod and access the Enterprise Records desktop.
23.0.1
User might be unable to 'Provision on Demand' when using Azure AD 

Symptom:
When trying to 'Provision on Demand' with a newly installed environment, user may get error in Group Membership, reporting Membership Update Status is Skipped, with SkipReason: RedundantExport. 

Cause: 
CPFS team is still investigating root of issue. 
 

Solution:
  1. User may instead use the Automation Provision option. 
  2. For more details regarding Provisioning on Demand, can reference the following topic. 


 

 
Task Manager is not supported in 23.0.1.x release with Azure AD

Symptom:
Task Manager is unable to authorize users when using Azure AD.

Cause: 
Task Manager developer team is still investigating root issue.
 

Solution:

This issue will continue to be investigated, and resolved in future iFixes.

 
Not able to upload documents larger than 375mb through Administrative Console for Content Platform Engine (ACCE)

Symptom:
Not able to upload files larger than 375mb or larger through ACCE.
 

Solution:

Please refer to this topic.

 
 

Back to top

​IBM Business Automation Navigator

LimitationDescription
Version
None reported 23.0.1

Back to top

 

IBM Business Automation Workflow

LimitationDescription
Version
In a container production runtime environment, the Workplace task list does not refresh automatically after modifying a task.

Symptom: After you modify a task in Workplace, for example, by changing its date or priority, and save the changes, the task list does not refresh automatically to reflect your changes.

Solution: Refresh the task list manually to see the latest changes.

23.0.1
(fixed in 23.0.2)

Back to top

LimitationDescription
Version

Browsing ruleapps in the RES Console may break with an unexpected 500 error "Client-id is duplicated in the faces tree".

Symptom:
Browsing ruleapps in Rule Execution Server console result in broken pages and 500 error pages

Solution:
User will logout and log back in to restore the Rule Execution Server console.		23.0.1

Back to top

LimitationDescription
Version
None reported 23.0.1

Back to top

 

IBM Automation Workstream Services

LimitationDescription
Version
No new limitations reported 23.0.1

Back to top

 

IBM Automation Decision Services

LimitationDescription
Version
Business Automation Insights is not supported in Automation Decision Services 23.0.1.
Automation Decision Services cannot send events to Business Automation Insights.
23.0.1

Back to top

 

IBM Content collector for SAP Applications

LimitationDescription
Version
 
Special characters in Keystore password not supported. 
Symptom: ICCSAP deployment fails when special characters are specified in secrets file ibm-iccsap-secret.

Cause: Special characters are not yet supported in the Keystore password.

Solution: Ensure that the keystorePassword in the ibm-iccsap-secret does not contain any special characters until this issue is fixed. This issue will be fixed in a future iFix for the release.		23.0.1

Back to top

 

[{"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":"a8m0z0000001iUCAAY","label":"Operate-\u003EUMS Install\\Upgrade\\Setup"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"23.0.1;23.0.2"}]

Document Information

Modified date:
03 November 2025

UID

ibm16980739

Page Feedback