IBM Support

Readme for Cloud Pak for Business Automation 23.0.2 IF002

Fix Readme


Abstract

The following document is for IBM Cloud Pak for Business Automation 23.0.2 IF002. 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: 23.0.2
Update Name: 23.0.2 IF002
Fix ID: 23.0.2-WS-CP4BA-IF002
Publication Date: 29 February 2024

Before installation
  1. Ensure you take regular backups of any databases associated with the environment.
  2. 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:
  3. oc get icp4acluster -o yaml 
oc get content -o yaml
oc get Foundation -o yaml
  4. 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 23.0.2-IF002
  • Cloud Pak Foundational Services 4.4
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 (the same catalog sources are also in the referenced CASE package).  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.
Important interim fix details:
Cloud Pak for Business Automation 23.0.2 interim fixes are released to the v23.2 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.
 
Step 1: Setup the CASE package
  1. Download the CASE package provided with this interim fix to a Linux based machine (RHEL or macOS).
  2. Use the tar command to extract the cert-kubernetes directory.
tar -xvzf ibm-cp-automation-5.1.2.tgz
cd ibm-cp-automation/inventory/cp4aOperatorSdk/files/deploy/crs
tar -xvf cert-k8s-23.0.2.tar
cd cert-kubernetes
Step 2:  Perform an online or 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.
  • 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 Production deployment of CP4BA is only supported when deploying into a new namespace without CPFS.
    Actions: Starter deployments do not support upgrades. Although 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 CASE package from this interim fix.
  • 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: You can use this interim fix content to perform a Production deployment.  To deploy an online Production deployment using the content of this interim fix, please follow steps from Question 5 in install a new online Production environment and use the CASE package from this interim fix.
  • 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 . It is recommended to use "oc mirror" for mirroring images process as the alternate option "oc-image-mirror" will be deprecated in the future. 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, download the CASE package mirror file cp4ba-case-to-be-mirrored-23.0.2-IF002.txt for this interim fix. You must rename the file to cp4ba-case-to-be-mirrored-23.0.2-IF002.yaml. 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-23.0.2-IF002.yaml
      The absolute path to file needs to be a path starting from "/". For example, "/opt" .
      Follow the instructions in Downloading the CASE files .
    2. You will need to mirror the images associated with the new CASE package.  
      export CASE_NAME=ibm-cp-automation
export CASE_VERSION=5.1.2
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, run the generated catalog-sources.yaml based on the catalog namespace.
      Note: If the IBMPAK_HOME environment variable is set, the downloaded CASE is located in $IBMPAK_HOME/.ibm-pak/data/mirror/$CASE_NAME/$CASE_VERSION/catalog-sources.yaml. If you want to change the namespace from the global catalog namespace (GCN) to your target CP4BA namespace (cp4ba-project), replace “openshift-marketplace” with the “<cp4ba_namespace_name>” in the generated catalog-sources.yaml file for all catalogs, except “ibm-cert-manager-catalog” and “ibm-licensing-catalog”.
      • Option 1: For Global catalog namespace.
        Run the below command. 
        cat $IBMPAK_HOME/.ibm-pak/data/mirror/$CASE_NAME/$CASE_VERSION/catalog-sources.yaml | sed 's/opencloud-operators/opencloud-operators-v4-4/g' | oc apply -f -
      • Option 2: For Target CP4BA namespace (private catalog).
        1. Run the following commands to update the catalog sources to be installed in the target namespace ( i.e the namespace value of the variable $NAMESPACE ) 
          sed -i "s/openshift-marketplace/$NAMESPACE/g" $IBMPAK_HOME/.ibm-pak/data/mirror/$CASE_NAME/$CASE_VERSION/catalog-sources.yaml
sed -i 's/opencloud-operators/opencloud-operators-v4-4/g' $IBMPAK_HOME/.ibm-pak/data/mirror/$CASE_NAME/$CASE_VERSION/catalog-sources.yaml

        2. Note: IBM Cert Manager catalog and IBM Licensing catalog cannot be deployed to the same namespace as CP4BA catalog namespace when you want to deploy as private catalog. This is due to the operator functionality perspective, IBM Licensing and IBM Cert Manager are cluster singleton services, although they are in a namespace, they watch and manage the resources for the entire cluster. This is quite different from a CP4BA instance in one namespace. Each CP4BA instance has it's own tenant scope(one or several namespaces), and there would be multiple CP4BA instances per cluster.

          Manually edit $IBMPAK_HOME/.ibm-pak/data/mirror/$CASE_NAME/$CASE_VERSION/catalog-sources.yaml to update namespace value -
                1. Update the namespace value for ibm-cert-manager-catalog catalogsource from openshift-marketplace to ibm-cert-manager.
                2. Update the namespace value for ibm-licensing-catalog catalogsource from openshift-marketplace to ibm-licensing.
          (OR) The following commands can also be executed to edit to the catalogsource.yaml for namespace value 
          sed -i '/name: ibm-licensing-catalog/{N;s/namespace: .*/namespace: ibm-licensing/}' $IBMPAK_HOME/.ibm-pak/data/mirror/$CASE_NAME/$CASE_VERSION/catalog-sources.yaml
sed -i '/name: ibm-cert-manager-catalog/{N;s/namespace: .*/namespace: ibm-cert-manager/}' $IBMPAK_HOME/.ibm-pak/data/mirror/$CASE_NAME/$CASE_VERSION/catalog-sources.yaml
        3. Create namespaces ibm-licensing and ibm-cert-manager where ibm-licensing-catalog and ibm-cert-manager-catalog will be installed. 
          oc new-project ibm-licensing
oc new-project ibm-cert-manager
        4. Run the following command to apply the modified catalog source. 
          oc apply -f $IBMPAK_HOME/.ibm-pak/data/mirror/$CASE_NAME/$CASE_VERSION/catalog-sources.yaml
    5. Go to the CPFS installer folder from the downloaded cert-kubernetes folder. 
      cd cert-kubernetes/scripts/cpfs/installer_scripts/cp3pt0-deployment
    6. Run the following command based on the catalog namespace.
      • Option 1: For global catalog namespace . 
        ./setup_singleton.sh --license-accept --enable-licensing -v 1 -c v4.2
      • Option 2: For Target CP4BA namespace (private catalog) . 
        ./setup_singleton.sh --enable-licensing --enable-private-catalog --license-accept -v 1 -c v4.2
    7. Run the following steps based on the catalog namespace
      • Option 1: For global catalog namespace .
        Install the CloudPak Operator in your namespace . 
        oc ibm-pak launch $CASE_NAME \
--version $CASE_VERSION \
--inventory $CASE_INVENTORY_SETUP \
--action install-operator \
--namespace $NAMESPACE
      • Option 2: For Target CP4BA namespace (private catalog) .

        Create a CP4BA subscription in the target namespace from the OperatorHub using the Openshift console UI by following the below steps

        • Navigate to the OperatorHub in the Openshift Console
        • Select the private catalog namespace (i.e value of $NAMESPACE ) in projects dropdown
        • Navigate to business automation in the side bar menu
        • Select the IBM Cloud Pak for Business Automation (CP4BA) multi-pattern tile 
          1.  In the Create Operator Subscription wizard, select the channel (v23.2 for 23.0.2).If you set any subscriptions to manual, then you must approve any pending operator updates. It is not recommended to set subscriptions to manual because it can make the installation error prone when some of the dependency operators are not approved. By default, all subscriptions are set to automatic.
          2. Choose A specific namespace on the cluster under Installation Mode and select the $NAMESPACE from the dropdown and click install.
          3. In the Installed Operators view, verify the status of the IBM Cloud Pak for Business Automation installation.
    8. 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 23.0.1 IF00x.
    Warning: You can only upgrade existing environments if they were using a single namespace scoped foundational services(CPFS) instance. Which mean the CPFS instance is installed in the same namespace as the cloud pak and isn't shared with any other Cloud Pak instances. Otherwise you would need to rebuild to upgrade.
    Note: Direct upgrade from version prior to 23.0.1 is not supported. If you are upgrading from a prior version then you would need to perform incremental upgrading using the instructions from each prior version.
    Actions:  
    For online upgrade , follow the upgrade instructions listed in Upgrading CP4BA multi-pattern clusters from 23.0.1 in online environment and for offline upgrade , follow the upgrade instructions listed in Upgrading CP4BA multi-pattern clusters from 23.0.1 in offline environment .
  • Scenario 5:  Your installed Production deployment is 23.0.2 GA or 23.0.2 IF001 and is online.
    Actions: 
    Perform the following steps and then the upgrade of operators and deployments will start.
    1. Upgrade the CP4BA operators using one of two methods. 
      • Option 1: For Global catalog namespace.
        Running the operator upgrade script from the CASE package for Global Catalog namespace. 
        ./scripts/cp4a-deployment.sh -m upgradeOperator -n <CP4BA Namespace>
      • Option 2: For Target CP4BA namespace (private catalog).
        Running the operator upgrade script from the CASE package to switch from Global Catalog namespace to Private Catalog namespace or to upgrade the existing Private Catalogs in the CP4BA Namespace. 
        ./scripts/cp4a-deployment.sh -m upgradeOperator -n <CP4BA Namespace> --enable-private-catalog
        Warning: The script in [upgradeOperator] mode will scale the CP4BA deployments down to zero. You must execute the script in [upgradeDeploymentStatus] mode to scale them back in. 
    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.
      1. Run the script in [upgradeOperatorStatus] mode to check that the upgrade of the CP4BA operator and its dependencies is successful. 
        ./scripts/cp4a-deployment.sh -m upgradeOperatorStatus -n <CP4BA Namespace>
        Warning: The script will scale the CP4BA deployments down to zero. You must execute the upgradeDeploymentStatus command to scale them back up.
      2. Run the script in [upgradeDeploymentStatus] mode to check that the upgrade of the CP4BA deployment is successful. 
        ./scripts/cp4a-deployment.sh -m upgradeDeploymentStatus -n <CP4BA Namespace>
  • Scenario 6:  Your installed Production deployment is 23.0.2 GA or 23.0.2 IF001 and using airgap/offline.
    Note:     It is recommended to use "oc mirror" for mirroring images process as the alternate option "oc-image-mirror" will be deprecated in the future. 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: 
    Perform the following steps and then the upgrade of operators and deployments will start.
    1. Download the CASE package mirror file, cp4ba-case-to-be-mirrored-23.0.2-IF002.txt, for this interim fix and you must rename the file to cp4ba-case-to-be-mirrored-23.0.2-IF002.yaml. Then execute this command to download the CASE files: 
      oc ibm-pak get -c file://(absolute path to file)/cp4ba-case-to-be-mirrored-23.0.2-IF002.yaml
      The (absolute path to file) needs to be a path starting from "/". For example, "/opt"
      For more information, see Downloading the CASE files.
    2. You will need to mirror the images associated with the new CASE package. Follow the instructions for either mirroring option in Mirroring images to the private registry using the new version values associated with this fix. 
      export CASE_NAME=ibm-cp-automation
export CASE_VERSION=5.1.2
    3.  Option 1: For Global catalog namespace.
      Run the below command. 
      cat $IBMPAK_HOME/.ibm-pak/data/mirror/$CASE_NAME/$CASE_VERSION/catalog-sources.yaml | sed 's/opencloud-operators/opencloud-operators-v4-4/g' | oc apply -f -
      Option 2: For Target CP4BA namespace (private catalog).
      Run the following commands to update the catalog sources to be upgraded in the target namespace ( i.e the namespace value of the variable $NAMESPACE )
      sed -i "s/openshift-marketplace/$NAMESPACE/g" $IBMPAK_HOME/.ibm-pak/data/mirror/$CASE_NAME/$CASE_VERSION/catalog-sources.yaml
sed -i 's/opencloud-operators/opencloud-operators-v4-4/g' $IBMPAK_HOME/.ibm-pak/data/mirror/$CASE_NAME/$CASE_VERSION/catalog-sources.yaml

      Note: IBM Cert Manager catalog and IBM Licensing catalog cannot be deployed to the same namespace as CP4BA catalog namespace when you want to deploy as private catalog. This is due to the operator functionality perspective, IBM Licensing and IBM Cert Manager are cluster singleton services, although they are in a namespace, they watch and manage the resources for the entire cluster. This is quite different from a CP4BA instance in one namespace. Each CP4BA instance has it's own tenant scope(one or several namespaces), and there would be multiple CP4BA instances per cluster.

      Manually edit $IBMPAK_HOME/.ibm-pak/data/mirror/$CASE_NAME/$CASE_VERSION/catalog-sources.yaml to update namespace value -
            1. Update the namespace value for ibm-cert-manager-catalog catalogsource from openshift-marketplace to ibm-cert-manager.
            2. Update the namespace value for ibm-licensing-catalog catalogsource from openshift-marketplace to ibm-licensing.
      (OR) The following commands can also be executed to edit to the catalogsource.yaml for namespace value 
      sed -i '/name: ibm-licensing-catalog/{N;s/namespace: .*/namespace: ibm-licensing/}' $IBMPAK_HOME/.ibm-pak/data/mirror/$CASE_NAME/$CASE_VERSION/catalog-sources.yaml
sed -i '/name: ibm-cert-manager-catalog/{N;s/namespace: .*/namespace: ibm-cert-manager/}' $IBMPAK_HOME/.ibm-pak/data/mirror/$CASE_NAME/$CASE_VERSION/catalog-sources.yaml
      Run the following command to apply the modified catalog source.
      oc apply -f $IBMPAK_HOME/.ibm-pak/data/mirror/$CASE_NAME/$CASE_VERSION/catalog-sources.yaml
    4. Update the cert manager and license service channels to the appropriate level with this script:
      Option 1: For Global catalog namespace. 
      ./scripts/cpfs/installer_scripts/cp3pt0-deployment/setup_singleton.sh --enable-licensing --cert-manager-source ibm-cert-manager-catalog --licensing-source ibm-licensing-catalog --license-accept -v 1 -c v4.2
      Option2: For Target CP4BA namespace (private catalog). 
      ./scripts/cpfs/installer_scripts/cp3pt0-deployment/setup_singleton.sh --enable-licensing --enable-private-catalog --license-accept -v 1 -c v4.2
    5. Update the channels to the appropriate levels for the rest of the CPFS subscriptions.
      Option 1: For Global catalog namespace
      ./scripts/cpfs/installer_scripts/cp3pt0-deployment/setup_tenant.sh --operator-namespace <CP4BA Namespace> -s opencloud-operators-v4-4 -c v4.4 --license-accept -v 1
      Option 2: For Target CP4BA namespace (private catalog).
      ./scripts/cpfs/installer_scripts/cp3pt0-deployment/setup_tenant.sh --operator-namespace <CP4BA Namespace> --enable-private-catalog -s opencloud-operators-v4-4 -c v4.4 --license-accept -v 1
      Note: Be sure to replace the namespace with the appropriate CP4BA namespace.
    6. 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 can make the upgrade more error prone.

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 -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.
b. Required when you are using Operational Decision Manager
     You must update your Rule Designer:
  • Open Eclipse 
  • Open menu Help > Check for Updates
  • Select IBM Operational Decision Manager for Developers v8.12.x - Rule Designer
  • Proceed with installation.
c. Required If you are importing Business Automation Workflow project that includes Case features. 
If you import projects with Case features, you might encounter the following errors.
com.ibm.bpm.pal.PALException: Workflow Project Import failed : Workflow Project Import failed during REST call to url: https://icp4adeploy-bastudio-service.production.svc:443/bas/CaseManager/CASEREST/v1/solution/import Response Message :{"UserMessage":{"UserResponse":"See the associated messages and the application server trace logs for more information.","UniqueId":"FNRPA0084E","Explanation":"The response information contains additional details provided by the exception.","Severity":"ERROR","Text":"An internal server error occurred while running a Case REST API method."},"UnderlyingDetails":{"Causes":["CREATE_HALFMAP failed.  26 items processed: 26 succeeded, 0 failed.\n\nNot supported: http:\/\/javax.xml.XMLConstants\/property\/accessExternalDTD"]}} 
Modify the CR as follows to make the import work. Be aware that doing this workaround might expose you to  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1844 , if your Workflow authoring tools are open to non-trusted users. 
workflow_authoring_configuration:
    jvm_customize_options: -Dcom.filenet.fdm.ignoreXXEProtectionFailures=true

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
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-4559, CVE-2017-1000487, CVE-2020-14422, CVE-2020-1734, CVE-2020-1737, CVE-2021-3583, CVE-2022-1705, CVE-2022-1962, CVE-2022-27664, CVE-2022-28131, CVE-2022-2879, CVE-2022-2880, CVE-2022-28948, CVE-2022-29162, CVE-2022-29804, CVE-2022-30580, CVE-2022-30629, CVE-2022-30630, CVE-2022-30631, CVE-2022-30632, CVE-2022-30633, CVE-2022-30634, CVE-2022-30635, CVE-2022-32148, CVE-2022-32189, CVE-2022-3697, CVE-2022-41715, CVE-2022-41716, CVE-2022-41717, CVE-2022-41720, CVE-2022-4244, CVE-2022-4245, CVE-2023-25809, CVE-2023-27561, CVE-2023-28642, CVE-2023-32681, CVE-2023-3635, CVE-2023-47108, CVE-2023-4806, CVE-2023-50298, CVE-2023-50386, CVE-2023-51074, CVE-2023-5115, CVE-2023-6246, CVE-2023-6267, CVE-2023-6780, CVE-2024-23897, CVE-2024-23898, GHSA-r68h-jhhj-9jvm, PRISMA-2022-0227
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.

Back to top

Cloud Pak for Business Automation Operator
Known Issue Title Sec. Cont. B.I.
N/A N/A

Back to top

Automation Document Processing
Known Issue Title Sec. Cont. B.I.
DT269835 PostgreSQL scripts missing from case package X X

Back to top

Automation Decision Services
Known Issue Title Sec. Cont. B.I.
N/A N/A

Back to top

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

Back to top

Business Automation Insights
Known Issue Title Sec. Cont. B.I.
N/A N/A

Back to top

Business Automation Navigator
Business Automation Studio
Known Issue Title Sec. Cont. B.I.
DT259434 Unable to create a snapshot in web Process Designer
DT260872 TWX import fails in Workflow Center V23.0.2
DT261303 Incorrect validation errors of data mapping in V23.0.2
DT261480 Creating a new branch in IBM Business Automation Studio fails for projects imported from IBM Business Automation Workflow

Back to top

Business Automation Workflow including Automation Workstream Services
Known Issue Title Sec. Cont. B.I.
DT258606 SECURITY DT258606 - CVE-2023-51074 IN BAW FLINK JOBS X
DT257050 Case Client icon missing when using non-default theme
DT259291 WHEN YOU USE THE USER SYNCHRONIZATION IN THE PROCESS ADMIN CONSOLE, THE USER STATE IS NOT UPDATED IN THE WORKFLOW DATABASE
DT259591 YOU MIGHT ENCOUNTER A CONNECTION FAILURE ERROR WHEN YOU CLICK THE 'TEST CONNECTION' BUTTON TO TEST AN ENTERPRISE CONTENT MANAGEMENT SERVER CONNECTION IN THE PROCESS ADMIN CONSOLE
DT260228 SnapShot installation fails with java.lang.NullPointerException
DT260320 Can not edit properties when editing heritage human services in IBM Process Designer
DT260800 Some of the action buttons in the Case Details page toolbar are not visible if the browser window is too small

Back to top

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

Back to top

FileNet Content Manager
Operational Decision Management
Known Issue Title Sec. Cont. B.I.
DT225086 MOUSE SCROLL WHEEL BEHAVES INCORRECTLY WITH RULEFLOW VERTICAL SCROLLBAR
DT245998 CLASSCASTEXCEPTION DURING EXECUTION WITH DECISION ENGINE AND RETEPLUS ALGORITHM
DT248043 RULE DESIGNER DOES NOT REFRESH ARTIFACTS AFTER SYNCHRONIZATION
DT255199 CANNOT SELECT MULTIPLE STRING LITTERAL DOMAINS WITH NEW DECISION TABLE EDITOR IN JAPANESE
DT257383 MERGING 2 DIFFERENT DECISION SERVICES MAY FAIL WITH AN UNEXPECTED ERROR MESSAGE
DT257645 AN UNEXPECTED ERROR HAS OCCURRED WHEN CREATING A BRANCH

Back to top

User Management Service
Known Issue Title Sec. Cont. B.I.
N/A N/A

Back to top

Workflow Process Service
Known Issue Title Sec. Cont. B.I.
DT258606 SECURITY DT258606 - CVE-2023-51074 IN BAW FLINK JOBS X
DT259291 WHEN YOU USE THE USER SYNCHRONIZATION IN THE PROCESS ADMIN CONSOLE, THE USER STATE IS NOT UPDATED IN THE WORKFLOW DATABASE
DT259591 YOU MIGHT ENCOUNTER A CONNECTION FAILURE ERROR WHEN YOU CLICK THE 'TEST CONNECTION' BUTTON TO TEST AN ENTERPRISE CONTENT MANAGEMENT SERVER CONNECTION IN THE PROCESS ADMIN CONSOLE
DT260228 SnapShot installation fails with java.lang.NullPointerException

Back to top

Known Limitations

Document change history

  • 29 February 2024: Initial publish.

    • [{"Type":"MASTER","Line of Business":{"code":"LOB10","label":"Data and AI"},"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":"23.0.2"}]

    Document Information

    Modified date:
    25 September 2024

    UID

    ibm17114493

    Page Feedback