IBM Support

Readme for Cloud Pak for Business Automation 21.0.3 IF020

Fix Readme


Abstract

The following document is for IBM Cloud Pak for Business Automation 21.0.3 IF020. 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: 21.0.3
Update Name: 21.0.3 IF020
Fix ID: 21.0.3-WS-CP4BA-IF020
Publication Date: 26 April 2023

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: 
    oc get icp4acluster -o yaml
oc get AutomationUIConfig -o yaml 
oc get Cartridge -o yaml 
oc get AutomationBase -o yaml 
oc get CartridgeRequirements -o yaml
  3. Required when you are using Business Automation Insights
    If Business Automation Insights is deployed, prune the Business Automation Insights deployment, and jobs,  before you apply the updated custom resource YAML file.
    $ oc delete Deployment,Job -l \
> 'app.kubernetes.io/name=ibm-business-automation-insights'
    Tip: For Flink event processing to resume from its previous state, make sure that savepoints are created before the upgrade and specified in the updated CR. For more information see Restarting from a checkpoint or savepoint

Installing the interim fix

Important: If you used any individual image tag settings in your CP4BA CR, it could prevent the operator from updating the images to the appropriate version. Ensure you remove any of these settings for a production installation when you upgrade.
Breaking change(s):
  1.  Starting with 21.0.3-IF012 interim fix, the URLs for Content Management Interoperability Services (CMIS) have changed (i.e., "cmis" context root was introduced): 
    • The previous CPD route for CMIS has changed
      • from:  https://cpd-<cp4ba-namespace>.xxxx.xxxx.xxxx/openfncmis_wlp 
      • to:  https://cpd-<cp4ba-namespace>.xxxx.xxxx.xxxx/cmis/openfncmis_wlp
    • The previous Openshift route for CMIS has changed
      • from:  https://cmis-<cp4ba-namespace>.xxxx.xxxx.xxxx/openfncmis_wlp 
      • to:  https://cmis-<cp4ba-namespace>.xxxx.xxxx.xxxx/cmis/openfncmis_wlp
The CASE package associated with this interim fix is ibm-cp-automation-3.2.20.tgz.  Download the CASE package to wherever you are planning to perform the online installation or upgrade of this interim fix (for example, the infrastructure node of your OCP cluster) and extract the CASE package into a directory. For offline/Airgap installation or upgrade follow below mentioned Scenario 5.
Cloud Pak for Business Automation 21.0.3 interim fixes are released to the v21.3 operator channel. Once the operator is upgraded, it triggers rolling updates for all the pods it manages to ensure they are updated to the appropriate version to match the operator.
If your environment has access to IBM entitled registry and has an automatic v21.3 channel subscription then production installations are upgraded automatically. This upgrade generally occurs when the interim fix is released or when images are mirrored for air gap setup.
Starting with 21.0.3-IF007 interim fix, we "pin" the version of Cloud Pak for Business Automation along with all its dependencies including IBM Automation Foundation and IBM Cloud Pak Foundational Services.  In other words, the automatic updates will be turned off and you will need to perform the steps listed to upgrade your environments in the future. 
This interim fix contains the following version of Cloud Pak for Business Automation, Automation Foundation, and Cloud Pak Foundational Services:
  • Cloud Pak for Business Automation – 21.0.3-IF020
  • Automation Foundation – 1.3.13
  • Cloud Pak Foundational Services – 3.19.10
Note:  If you have other Cloud Paks installed on the same OCP cluster, be sure to check the compatibility of the Automation Foundation  and Cloud Pak Foundational Services versions, listed above, with other Cloud Paks.
Depending on the current setup and state of your existing environment, there are various upgrade actions that need to be taken. The following scenarios cover what actions might be needed for a particular setup.

Installing IBM Cloud Pak foundational services in multiple namespaces is now possible starting with 21.0.3 iFix019.

If the cp4a-clusteradmin-setup.sh script is used, a namespace-scoped instance of foundational services is installed in the same namespace as the CP4BA deployment. If you do not want this configuration, you must use the OpenShift Container Platform (OCP) console to install Cloud Pak for Business Automation. A CP4BA deployment installed from the OCP console uses a cluster-scoped instance of foundational services in the ibm-common-services namespace.

Restriction: You cannot have a cluster-scoped instance of foundational services and a namespace-scoped instance on the same cluster.
Configuration of foundational services in multiple namespaces:

Important: By default, a dedicated instance of foundational services is installed with CP4BA, which is the recommended use case. If you do not want to use dedicated foundational services for your deployment and want to use a shared instance instead, you must use the OCP console. A deployment of CP4BA with a shared foundational services instance can be done by applying the CP4BA catalog sources and then selecting the CP4BA catalog tile to create a subscription.
Using the OCP console

To create dedicated foundational services for your CP4BA deployment in the OCP console, you must add a configMap (common-service-maps) to your cluster that describes the namespace mapping of the foundational services. The following example shows a configMap with two mapped instances:

apiVersion: v1

kind: ConfigMap

metadata:

  name: common-service-maps

  namespace: kube-public

data: 

  common-service-maps.yaml: |

    controlNamespace: cs-control

    namespaceMapping:

    - requested-from-namespace:

      - cp4ba1

      map-to-common-service-namespace: cp4ba1

    - requested-from-namespace:

      - cp4ba2

      map-to-common-service-namespace: cp4ba2

Where the CP4BA deployment in the cp4ba1 namespace uses dedicated foundational services that are also installed in cp4ba1, and the CP4BA deployment in cp4ba2 uses dedicated foundational services in cp4ba2.

After you created a configMap, you can then follow the steps to install a CP4BA starter or production deployment. For more information, see Installing on Red Hat OpenShift.

When the deployment is complete, the CP4BA deployment uses the foundational services that are defined in the configMap namespace mapping.

Using the deployment scripts

If you use the cluster admin script (cp4a-clusteradmin-setup.sh), the script checks for an existing common-service-maps configMap to see whether the instances of foundational services already in the cluster are dedicated to a Cloud Pak. If the common-service-maps configMap does not exist, the script creates a configMap so that the operator can deploy a dedicated instance. When the script is complete, the CP4BA deployment uses the foundational services that are defined in the configMap namespace mapping.

For more information, see Installing IBM Cloud Pak foundational services in multiple namespaces.

  • Scenario 1: You are using a starter installation.
    Actions: Starter environments do not support upgrades. Although you can use the interim fix content, install a new starter environment and use the CASE package from this interim fix.
  • Scenario 2: Your installation is version 21.0.2-IF012
    Note:  You can only upgrade to 21.0.3-IF00x from the latest 21.0.2-IF012
    Actions:      To upgrade your environment, follow the Upgrading automation containers instructions.
    • When you perform the upgrade, you can substitute the CASE package from this interim fix for the 21.0.3 CASE package while you follow the instructions. For air gap, you can use the case save command in step 1 of scenario 4.
    • Note: If you are using versions before 21.0.2, then you must incrementally upgrade and follow the instructions for each version between your source version and 21.0.3
  • Scenario 3:  Your installation is version 21.0.3-IFxxx and you're using pinned catalog (note that pinned catalog was available with 21.0.3-IF007 or later)
    Actions:  Apply the updated catalog sources below (Note: you are not require to execute the "update_subscription.sh" script to change the subscription).
    1. Apply the catalog sources to pin to the specified versions for IBM Automation Foundation, IBM Foundational Services with Cloud Pak for Business Automation.
      You can apply the catalog sources below from a command line by creating a YAML file (for example, cp4ba_catalog_sources.yaml) with the catalog sources below and performing "oc apply -f cp4ba_catalog_sources.yaml", or you can apply the catalog sources using the OCP console
      Note, you can apply only one catalog source at a time using the OCP console. 
      Note:  The DB2, IBM Business Team Service, and Postgres catalog sources are dependent components of Cloud Pak for Business Automation. 
      # CP4BA 21.0.3-IF020 catalog
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: ibm-cp4a-operator-catalog
  namespace: openshift-marketplace
spec:
  displayName: ibm-cp4a-operator
  publisher: IBM
  sourceType: grpc
  image: icr.io/cpopen/ibm-cp-automation-catalog@sha256:a70c961cae542caf134128ad7f0bdc8d6bb4d3deb746f54ed2f4ecb66ade7402
  updateStrategy:
    registryPoll:
      interval: 45m
---
# IBM Automation Foundation Base 1.3.13
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: ibm-cp-automation-foundation-catalog
  namespace: openshift-marketplace
spec:
  displayName: IBM Automation Foundation Operators
  publisher: IBM
  sourceType: grpc
  image: icr.io/cpopen/ibm-cp-automation-foundation-catalog@sha256:1753b1cabf6cdc6d295d8da096ce3f769b6487fdbef5802de63dccbfa7d9a43b
  updateStrategy:
    registryPoll:
      interval: 45m
---
# IBM Automation Foundation Core 1.3.13
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: ibm-automation-foundation-core-catalog
  namespace: openshift-marketplace
spec:
  displayName: IBM Automation Foundation Core Operators
  publisher: IBM
  sourceType: grpc
  image: icr.io/cpopen/ibm-automation-foundation-core-catalog@sha256:8bd0b52526de4a2adf6b299237f3d295a710e7d0ff538a319226c614ceae618b
  updateStrategy:
    registryPoll:
      interval: 45m
---
# IBM Cloud Foundational Services 3.19.10
 apiVersion: operators.coreos.com/v1alpha1
 kind: CatalogSource
 metadata:
  name: opencloud-operators
  namespace: openshift-marketplace
  annotations:
    bedrock_catalogsource_priority: '1'
 spec:
  displayName: IBMCS Operators
  publisher: IBM
  sourceType: grpc
  image: icr.io/cpopen/ibm-common-service-catalog@sha256:a8446e8b4d489147d6e2551ac983d2be0cbfd83d32daab0cee15fd56ec5a3a78
  updateStrategy:
    registryPoll:
      interval: 45m
  priority: 100 
---
# DB2 Operator Case version 5.1.3
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: ibm-db2uoperator-catalog
  namespace: openshift-marketplace
spec:
  displayName: IBM Db2U Catalog
  #5.1.1
  #image: icr.io/cpopen/ibm-db2uoperator-catalog@sha256:3727845846f2fe9be0b712abd3c9d0b89c243b603ca0b129553f6733df548b36
  image: icr.io/cpopen/ibm-db2uoperator-catalog@sha256:269b92119828b09069df70f61f0032262eee7bae413e08935b2d0d68f65062d1
  imagePullPolicy: Always
  publisher: IBM
  sourceType: grpc
  updateStrategy:
    registryPoll:
      interval: 45m
---
# IBM Business Teams Service version 3.24.0
 apiVersion: operators.coreos.com/v1alpha1
 kind: CatalogSource
 metadata:
  name: bts-operator
  namespace: openshift-marketplace
  annotations:
    bedrock_catalogsource_priority: '1'
 spec:
  displayName: BTS Operator
  publisher: IBM
  sourceType: grpc
  image: icr.io/cpopen/ibm-bts-operator-catalog@sha256:aa49b78da11e3f072537b05b84494db55b2e2b1558fac59217ff8e651b57120e
  updateStrategy:
    registryPoll:
      interval: 45m
---
# Cloud Native PostgresSQL 4.11.0
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  annotations:
    bedrock_catalogsource_priority: '1'
  name: cloud-native-postgresql-catalog
  namespace: openshift-marketplace
spec:
  displayName: Cloud Native Postgresql Catalog
  publisher: IBM
  sourceType: grpc
  image: icr.io/cpopen/ibm-cpd-cloud-native-postgresql-operator-catalog@sha256:642aba4b78bcadd8f1d5e1f9d05d8484e2934d914a5b6d67435f3e98082d7592
  updateStrategy:
    registryPoll:
      interval: 45m
  priority: 100
    2. If you have any subscriptions set to manual, then you need to approve any pending operator updates.
    3. If some of the many operator updates are not approved, it is not recommended to set subscriptions to manual, this makes the upgrade more error prone . By default all subscriptions are set to automatic.
  • Scenario 4:  If you are not using "pinned" catalog and your installation is version 21.0.3-IFxxxx (where xxxx is the latest iFix of 21.0.3).  Your 21.0.3 installation has the latest iFix because you are using the IBM Operator Catalog and the CP4BA Operator will automatically upgrades to the latest iFix when it is available.
    Actions: Apply the updated catalog sources above in scenario #3.  Then execute the "update_subscription.sh" script to change the subscriptions.
    1. Update the existing subscriptions of Cloud Pak for Business Automation, Automation Foundation, and Cloud Pak Foundational Services to change from IBM Operator Catalog to the individual catalogs applied above.
      1. Find the update_subscription.sh script from the extracted CASE package under "../ibm-cp-automation/inventory/cp4aOperatorSdk/files/deploy/crs/cert-kubernetes/scripts" Note, at the root of the CASE package is a nested archive that needs to be extracted as well.
      2. Log in to your OCP cluster as a cluster administrator
      3. Execute the update_subscription.sh -n <your cp4ba namespace>
        Note, at this point, the environment will be updated to use the new "pinned" catalogs. Your environment will no longer auto-update the operators when new versions are released.
    2. If you have any subscriptions set to manual, then you need to approve any pending operator updates.
      If some of the many operator updates are not approved, it is not recommended to set subscriptions to manual, this makes the upgrade more error prone . By default all subscriptions are set to automatic.
  • Scenario 5: Your installation is air gap and 21.0.3.x
    Actions:
    After the operators are upgraded, it will trigger the upgrade of the related deployments and pods. See the items mentioned in "Performing the necessary tasks after installation" for more actions that can be needed after the upgrade is completed.
    1. Set up the environment variables for CASE. 
      • export CASE_NAME=ibm-cp-automation 
      • export OFFLINEDIR=/opt/cp4ba2103-if020
      • export CASE_VERSION=3.2.20
      • export CASE_INVENTORY_SETUP=cp4aOperatorSetup 
      • export CASE_ARCHIVE=${CASE_NAME}-${CASE_VERSION}.tgz 
      • export CASE_LOCAL_PATH=${OFFLINEDIR}/${CASE_ARCHIVE}

        Note: The values are specific to the interim fix, however, you can choose a different empty directory for the OFFLINEDIR if you need to put the files somewhere else.
    2. Save this specific set of case packages
      cloudctl case save --case docker://icr.io/cpopen/ibm-cp-automation-case-cache@sha256:22902a8fda545f3c703e1d21664697ccbcdcda87c4ee5264e13833df95325476 --outputdir ${OFFLINEDIR}
      Once the command completes, all the Case archive and inventory are saved under /opt/cp4ba2103-if020.
    3. Mirror the entitled registry images to the local registry by completing the same steps used during installation. For more information about mirroring, see Mirroring images to the private registry.
      Make sure to use the CASE image OFFLINEDIR (/opt/cp4ba2103-if020) from step 1.
    4. Update the catalog with the new version by running the install-catalog action. 
      cloudctl case launch \
--case ${OFFLINEDIR}/${CASE_ARCHIVE} \
--inventory ${CASE_INVENTORY_SETUP} \
--action install-catalog \
--namespace ${NAMESPACE} \
--args "--registry ${LOCAL_REGISTRY} --inputDir ${OFFLINEDIR} --recursive"
    5. If you have any subscriptions set to manual, then you need to approve any pending operator updates.
      If some of the many operator updates are not approved, it is not recommended to set subscriptions to manual as it can make the upgrade more error prone. By default all subscriptions would be set to automatic.

Performing the necessary tasks after installation

  1. Update Kafka certificates when you are using Business Automation Insights
    If you are using Business Automation Insights and upgrading from an IBM Automation Foundation version before 1.3, the operator will fail to become ready after the upgrade, and kafka/zookeeper pods show SSL errors. To resolve the issue, follow the "To renew the leaf certificates for Kafka" instructions in Changes to CA certificate and key does not automatically rotate Kafka leaf certificates.
  2. 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.
  3. Required when you are using Workflow Process Service OCP deployment
    If you used any individual image tag settings in your WfPSRuntime CR, it could prevent the operator from updating the images to the appropriate version. Ensure you remove any of these settings when you upgrade.
  4. Required when you are using Workflow Process Service Docker Compose Edition
    1. Follow the step 2 of section "3. Running your environment" in Installing Workflow Process Service to log in to the entitled registry with your entitlement key.
    2. Back up your database backup, docker-compose.yml and folder for docker volumes “production_workflow_runtime_data” and “production_workflow_runtime_logs”.
    3. (Optional) Push the images to your docker registry. Log in to your docker registry, and push the docker images into your docker registry by using the following commands: 
      docker login <server>
docker tag cp.icr.io/cp/cp4a/workflow-ps/workflow-ps-server:<tag> \
 <server>/workflow-ps-server:<tag>
docker tag cp.icr.io/cp/cp4a/workflow-ps/workflow-ps-authoring:<tag> \
 <server>/workflow-ps-authoring:<tag>
docker push <server>/workflow-ps-server:<tag>
docker push <server>/workflow-ps-authoring:<tag>
      Where <server> is the host of the docker image registry that you want to use to pull the images. For example, myregistry.local:5000 or localhost:8080 for a self-hosted registry. Also, replace <tag> with the corresponding tag matching this interim fix's tag in the form of <release>-IFxxx, for example, 21.0.3-IF020.
    4. Run docker-compose down command to stop the Workflow Process Server container.
    5. Update the image url's tags in docker-compose.yml. 
      <server>/workflow-ps-server:<tag>
<server>/workflow-ps-authoring:<tag>
      Where <tag> is the corresponding tag matching this interim fix's tag in the form of <release>-IFxxx, for example, 21.0.3-IF020.
    6. Run docker-compose up command to start the Workflow Process Server container
    For more detail on Workflow Process Service, refer to Installing Workflow Process Service .
    Troubleshooting: If you are using a Docker Desktop version 4.3.0 or greater, you might get an out of memory error when you start the server. For more details and possible resolution to this issue, and other troubleshooting guidance, refer to Troubleshooting Workflow Process Service on Podman or Troubleshooting Workflow Process Service on Docker.
  5. 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.11.x - Rule Designer
    • Proceed with installation.

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-2023-25690, CVE-2022-31690, CVE-2022-31692, CVE-2022-25881, CVE-2023-0767, CVE-2023-29017, RHSA-2023:1405, CVE-2022-4378, CVE-2023-0266, CVE-2023-0386, CVE-2022-4269, CVE-2023-29017, CVE-2022-31692 
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.
N/A N/A

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
Known Issue Title Sec. Cont. B.I.
N/A N/A

Back to top

Business Automation Studio
Known Issue Title Sec. Cont. B.I.
DT197974 SECURITY VULNERABILITY IN COMMONS-FILEUPLOAD AFFECTS IBM BUSINESS AUTOMATION WORKFLOW AND CLOUD PAK FOR BUSINESS AUTOMATION X
DT195793 POSSIBLY SENSITIVE INFORMATION IN URL PARAMETERS
DT201338 SNAPSHOT TAB UNDER BRANCH PAGE OF PROCESS APP FAILS TO SHOW LIST OF SNAPSHOTS IN WORKFLOW CENTER CONSOLE
DT211542 ZEN HOME PAGE NOT SHOWING BUSINESS AUTOMATION IN THE TILE - IBM Cloud Pak for Business Automation

Back to top

Business Automation Workflow including Automation Workstream Services
Known Issue Title Sec. Cont. B.I.
DT208579 SECURITY - CVE-2022-1471 - CASE HISTORY EMITTER IS AFFECTED BY SNAKEYAML VULNERABILITY X
DT208782 SECURITY APAR - CVE-2022-1471 REPORTED FOR SNAKEYAML IN BPMEVENTEMITTER X
DT209212 SECURITY APAR - CVE-2023-20861 IN BPM/LOMBARDI/LIB/SPRING-EXPRESSIONS.JAR X
DT198745 Workplace cannot search for task or workflow names that contain Chinese characters
DT208139 IBM Process Federation Server indexers not reprocessing tasks and instances updates after a communication exception with Elasticsearch
DT210959 Entries with TASK_ID=NULL are never removed from the PFS_BPD_CHANGE_LOG TABLE if process instance indexing is not enabled for the federated system
JR64002 YOU CAN'T DELETE SNAPSHOTS
JR64395 YOU CANNOT ENABLE AND CONFIGURE EMAIL NOTIFICATION
JR64892 SERVICE TASKS OR NON-USER TASKS ARE VISIBLE IN IBM PROCESS PORTAL THOUGH USER CAN NOT TAKE ACTION ON THAT
JR64986 UNABLE TO DEPLOY CASE SOLUTION ON CP4BA ENTERPRISE PATTERN ENVIRONMENT USING SWAGGER UI

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.
DT196511 MAVEN BUILD ISSUE USING SWITCH ON AN ENUM (PRESENCE OF A SYNTHETIC METHOD)
DT208408 EXECUTION ORDER IS DIFFERENT WHEN USING CRE VS DE WITH NO MAIN RULEFLOW
DT209035 CANNOT DELETE A DECISION SERVICE WHICH DEPENDS ON A PROJECT/BRANCH WHICH IS NOT AVAILABLE ANYMORE
DT209333 DECISION CENTER GENERATES RULESETS FOR ALL RULE PACKAGES INCLUDING EMPTY RULE PACKAGES, GREATLY IMPACTING ENGINE PERFORMANCE
DT209334 RULE DESIGNER GENERATES RULESETS FOR ALL RULE PACKAGES, INCLUDING EMPTY RULE PACKAGES GREATLY IMPACTING ENGINE PERFORMANCE
DT197323 THE OBSERVED COLLECTION IN THE TEST SUITE REPORT DETAILS DISPLAYS MORE ATTRIBUTES THAN EXPECTED
DT197613 SLOW DISPLAY OF A CHANGE ACTIVITY IN THE BUSINESS CONSOLE
DT197938 DESCRIPTION LOST AFTER MOVING ARTIFACT TO ANOTHER FOLDER
RS03882 DECISION MODEL: COPY PASTE IN DECISION TABLE LEADS TO ADDITIONAL ROWS BEING CREATED
RS03953 IF THERE IS A VALUE IN EXPECTED VALUE THE ACTUAL VALUE CANNOT BE NULL
RS03943 UNRESPONSIVE BUSINESS CONSOLE AFTER IMPORTING FROM EXCEL AND SAVING

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.
DT208782 SECURITY APAR - CVE-2022-1471 REPORTED FOR SNAKEYAML IN BPMEVENTEMITTER X
DT209212 SECURITY APAR - CVE-2023-20861 IN BPM/LOMBARDI/LIB/SPRING-EXPRESSIONS.JAR X
JR64002 YOU CAN'T DELETE SNAPSHOTS
JR64395 YOU CANNOT ENABLE AND CONFIGURE EMAIL NOTIFICATION
JR64892 SERVICE TASKS OR NON-USER TASKS ARE VISIBLE IN IBM PROCESS PORTAL THOUGH USER CAN NOT TAKE ACTION ON THAT

Back to top

Known Limitations

Document change history

  • 26 April 2023: Initial publish.

    • Related Information

    [Supersedes 21.0.3-IF019] Readme for Cloud Pak for Business Automation 21.0.3 I…

    [Supersedes 21.0.3-IF018] Readme for Cloud Pak for Business Automation 21.0.3 I…

    [Supersedes 21.0.3-IF017] Readme for Cloud Pak for Business Automation 21.0.3 I…

    [Supersedes 21.0.3-IF016] Readme for Cloud Pak for Business Automation 21.0.3 I…

    [Supersedes 21.0.3-IF015] Readme for Cloud Pak for Business Automation 21.0.3 I…

    [Supersedes 21.0.3-IF014] Readme for Cloud Pak for Business Automation 21.0.3 I…

    [Supersedes 21.0.3-IF0013] Readme for Cloud Pak for Business Automation 21.0.3 …

    [Supersedes 21.0.3-IF012] Readme for Cloud Pak for Business Automation 21.0.3 I…

    [Supersedes 21.0.3-IF011] Readme for Cloud Pak for Business Automation 21.0.3 I…

    [Supersedes 21.0.3-IF010] Readme for Cloud Pak for Business Automation 21.0.3 I…

    [Supersedes 21.0.3-IF009] Readme for Cloud Pak for Business Automation 21.0.3 I…

    [Supersedes 21.0.3-IF008] Readme for Cloud Pak for Business Automation 21.0.3 I…

    [Supersedes 21.0.3-IF007] Readme for Cloud Pak for Business Automation 21.0.3 I…

    [Supersedes 21.0.3-IF006] Readme for Cloud Pak for Business Automation 21.0.3 I…

    [Supersedes 21.0.3-IF005] Readme for Cloud Pak for Business Automation 21.0.3 I…

    [Supersedes 21.0.3-IF004] Readme for Cloud Pak for Business Automation 21.0.3 I…

    [Supersedes 21.0.3-IF003] Readme for Cloud Pak for Business Automation 21.0.3 I…

    [Supersedes 21.0.3-IF002] Readme for Cloud Pak for Business Automation 21.0.3 I…

    Cloud Pak for Business Automation Fix list

    Cloud Pak for Business Automation Interim fix download

    [{"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"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]

    Document Information

    Modified date:
    01 April 2024

    UID

    ibm16984189

    Page Feedback