IBM Support

Readme for Cloud Pak for Business Automation 22.0.2 IF006

Fix Readme


Abstract

The following document is for IBM Cloud Pak for Business Automation 22.0.2 IF006. 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: 22.0.2
Update Name: 22.0.2 IF006
Fix ID: 22.0.2-WS-CP4BA-IF006
Publication Date: 29 June 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 content -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.
  4. Ensure no custom route or ingress is configured using port 9080 from service endpoints
    Starting with 22.0.2-IF006, due to security concerns, unsecured port 9080 was removed from Kubernetes service for the capabilities and components listed below. Note that the default routes and ingresses created by the operator already using secured port 9443 of the services so they are unaffected by this change. However, if you created custom routes or ingresses using unsecured port 9080, make sure replace it with secured 9443 port before upgrading.
    The capabilities and components that were changed:
    • FileNet Content Manager
    • Automation Document Processing
    • Business Automation Navigator
    • IBM Enterprise Records
    • IBM Content Collector for SAP
  5. Cloud Pak Foundational Services (CPFS) Channel upgrade
    If your CPFS subscriptions associated with the Cloud Pak are not at the expected channel for this iFix, then you must upgrade that first. For more details on cluster-scoped and namespace-scoped CPFS instances, see System requirements.
    1. Log in to the cluster as an administrator by using the oc login command.
    2. Download the upgrade_common_services.sh script to your local machine.
    3. Execute the upgrade_common_services script to change the related subscriptions to the needed channel.
      • If you want to upgrade all CPFS instances in the cluster then execute this command where -c v3.23 provides the needed channel: 
        ./upgrade_common_services.sh -a -c v3.23
        Note: If you are using cluster-scoped CPFS, then you must upgrade all CPFS instances. This can impact other Cloud Pak installations in the cluster and you should ensure they support the same version.
      • If you want to only upgrade specific namespace-scoped CPFS instances, then you will need to make use of the various command arguments to meet your needs.
        • Use -cloudpaksNS to list all Cloud Pak namespaces you want to upgrade.
          Note: If multiple Cloud Pak instances are sharing a CPFS instance, they all must be upgraded at the same time.
        • Use -controlNS to specific the location of the control namespace.
          Note: The control namespace version needs to be equal to the highest version of CPFS in the cluster.
        • Use -csNS to list all CPFS namespaces you want to upgrade.
          Note: This list can overlap with the cloudpak list.
        For example, if you want to upgrade a namespace-scoped CPFS instance with the Cloud Pak and CPFS sharing the cp4ba namespace and the control namespace set to cp4ba-c to version v3.23, run the following command: 
        ./upgrade_common_services.sh -cloudpaksNS cp4ba -csNS cp4ba -controlNS cp4ba-c -c v3.23

Installing the interim fix

This interim fix contains the following version of Cloud Pak for Business Automation,  IBM Automation Foundation (IAF), and Cloud Pak Foundational Services (CPFS):
  • Cloud Pak for Business Automation – 22.0.2-IF006
  • IBM Automation Foundation – 1.3.14
  • Cloud Pak Foundational Services – 3.23.4
Note:  This interim fix only supports the Automation Foundation and 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 Automation Foundation  and Cloud Pak Foundational Services versions, listed above, with other Cloud Paks' specifications.
Important interim fix details:
  • Case Package: ibm-cp-automation-4.1.6.tgz
  • Case Package mirror file (IBM-Pak steps): cp4ba-case-to-be-mirrored-22.0.2-IF006.txt
  • Case Save command (cloudctl steps): 
    cloudctl case save --case docker://icr.io/cpopen/ibm-cp-automation-case-cache@sha256:3956587ad09de939c9e15ed54fdc758094ccca03d725fc0c6c684eb007af6930 --outputdir ${OFFLINEDIR}
  • Cloud Pak Foundational Services channel: v3.23
The CASE package content is used to help facilitate installation and upgrade operation. See the various instructions for more specific details.
Cloud Pak for Business Automation 22.0.2 interim fixes are released to the v22.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.
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.
  • Scenario 1: You are using a Starter deployment
    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.
    Note: If you have existing Cloud Pak Foundational Services instances in the cluster then you should review the channel upgrade info in Before Installation.
  • Scenario 2: You are installing a Production deployment
    Actions: You can use this interim fix content to perform a Production deployment.  To deploy a Production deployment using the content of this interim fix, please see install a new Production environment and use the CASE package from this interim fix.
    Note: If you have existing Cloud Pak Foundational Services instances in the cluster then you should review the channel upgrade info in Before Installation.
  • Scenario 3: Your installation's version is prior to 22.0.2.
    Actions: Follow the upgrade instructions while using the case package details from this iFix.
    Warning: If you are using Business Automation Applications, you must upgrade from 21.0.1 ifix06 due to DT174377. Upgrading from an earlier release could result in corrupted business applications.  
    Important: When upgrading common services, be sure to upgrade to the needed channel for the iFix.
    Note: If you are upgrading from a version prior to 22.0.1, then you will need to perform incremental upgrades from each prior version.
  • Scenario 4:  You already have a Production deployment installed 22.0.2 GA or 22.0.2 + any interim fix and now you want to install another Production deployment using this interim fix on the same Openshift cluster.
    Actions: 
    Perform the following steps and then the upgrade of operators and deployments will start.
    Note: If your Cloud Pak Foundational Services instance is at an earlier release review the channel upgrade info in Before Installation.
    1. Apply the catalog sources to pin to the specified versions for IBM Automation Foundation, Cloud Pak Foundational Services and Cloud Pak for Business Automation.( Note: Make sure to follow the steps to update Cloud Pak Foundational Services in Before Installation.)
      If you download and unzip the case package mentioned above, the needed catalogSource yaml file is located here: 
      ibm-cp-automation\inventory\cp4aOperatorSdk\files\deploy\crs\cert-k8s-22.0.2\cert-kubernetes\descriptors\op-olm\catalog_source.yaml
      Execute oc apply -f catalog_source.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.

      Alternatively you can create the catalog_source.yaml file with the following text.   
      # CP4BA 22.0.2 IF006 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:63c01ab49ba53c27ab99ede7cc5db2cb687e8ae7b308a74b90c421a296395242
  updateStrategy:
    registryPoll:
      interval: 45m
---
# IBM Automation Foundation Base 1.3.14
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:c510e7b9cb3c6fdfac3a05c2f97b12e1f0187431b4466d5707d9e48b3dfd9ca1
  updateStrategy:
    registryPoll:
      interval: 45m
---
# IBM Automation Foundation Core 1.3.14
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:c3179bad29705422354c5ef656ee464c5322cca09010fff9b5bf86a9ad06aab4
  updateStrategy:
    registryPoll:
      interval: 45m
---
# IBM Cloud Foundational Services 3.23.4
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  annotations:
    bedrock_catalogsource_priority: '1'
  name: opencloud-operators
  namespace: openshift-marketplace
spec:
  displayName: IBMCS Operators
  publisher: IBM
  sourceType: grpc
  image: icr.io/cpopen/ibm-common-service-catalog@sha256:cc3491ee7b448c3c8db43242d13e9d5d13a37ad9e67d166744d9b162887ed7e7
  updateStrategy:
    registryPoll:
      interval: 45m
  priority: 100
---
# IBM Business Teams Service version 3.26.0
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  annotations:
    bedrock_catalogsource_priority: '1'
  name: bts-operator
  namespace: openshift-marketplace
spec:
  displayName: BTS Operator
  publisher: IBM
  sourceType: grpc
  image: icr.io/cpopen/ibm-bts-operator-catalog@sha256:0043ccbf6ae8a6901182fb1e45bc580b8a81be67b951897e9dc4ef6495a94f57
  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 InstallPlans.
      Note:  It is not recommended to set subscriptions to manual, this makes the upgrade more error prone.  By default all subscriptions are set to automatic.
    3. Follow the steps to perform validation of your Production deployment
  • Scenario 5:  Your installation is 22.0.2 GA or 22.0.2 + any interim fix and using IBM-Pak Plugin airgap instructions
    Actions: 
    Perform the following steps and then the upgrade of operators and deployments will start.
    Note: If your Cloud Pak Foundational Services instance is at an earlier release review the channel upgrade info in Before Installation.
    1. Get the case package mirror file, cp4ba-case-to-be-mirrored-22.0.2-IF006.txt, for interim fix and you must rename the file to cp4ba-case-to-be-mirrored-22.0.2-IF006.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-22.0.2-IF006.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. Follow the instructions for either mirroring option in Mirroring images to the private registry.
      Important: You must set export CASE_VERSION=4.1.6 that is the version for this iFix.
    3. Update the catalog with the new version by running the install-catalog action. 
      oc ibm-pak launch $CASE_NAME \
--version $CASE_VERSION \
--action install-catalog \
--inventory $CASE_INVENTORY_SETUP \
--namespace $NAMESPACE \
--args  "--registry $TARGET_REGISTRY --recursive --inputDir ~/.ibm-pak/data/cases/$CASE_NAME/$CASE_VERSION"
    4. If you have any subscriptions set to manual, then you need to approve any pending InstallPlans.
      Note: It is not recommended to set subscriptions to manual, this makes the upgrade more error prone . By default all subscriptions are set to automatic.
    5. Follow the steps to perform validation of your Production deployment
  • Scenario 6:  Your installation is 22.0.2 GA or 22.0.2 + any interim fix and using cloudctl(deprecated) airgap instructions
    Actions: 
    Perform the following steps and then the upgrade of operators and deployments will start.
    Note: If your Cloud Pak Foundational Services instance is at an earlier release review the channel upgrade info in Before Installation.
    1. Set up the environment variables for CASE 
      export CASE_NAME=ibm-cp-automation 
export OFFLINEDIR=/opt/cp4ba2202-if006
export CASE_VERSION=4.1.6
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:3956587ad09de939c9e15ed54fdc758094ccca03d725fc0c6c684eb007af6930 --outputdir ${OFFLINEDIR}
      Once the command completes, all the Case archive and inventory are saved under OFFLINEDIR.
    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/cp4ba2202-if006) 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 InstallPlans.
      Note: It is not recommended to set subscriptions to manual, this makes the upgrade more error prone . By default all subscriptions are set to automatic.
    6. Follow the steps to perform validation of your Production deployment

Performing the necessary tasks after installation

  1. 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.
  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 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, 22.0.2-IF001.
    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, 22.0.2-IF001.
    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.
  4. 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-2020-14039, CVE-2020-15586, CVE-2020-16845, CVE-2020-24553, CVE-2020-28362, CVE-2020-28366, CVE-2020-28367, CVE-2020-28975, CVE-2020-29510, CVE-2021-27918, CVE-2021-29923, CVE-2021-3114, CVE-2021-33195, CVE-2021-33196, CVE-2021-33197, CVE-2021-33198, CVE-2021-34558, CVE-2021-36221, CVE-2021-36222, CVE-2021-37750, CVE-2021-3782, CVE-2021-38297, CVE-2021-39293, CVE-2021-41771, CVE-2021-41772, CVE-2021-42740, CVE-2021-43618, CVE-2021-44716, CVE-2022-23491, CVE-2022-23772, CVE-2022-23773, CVE-2022-23806, CVE-2022-24675, CVE-2022-24921, CVE-2022-25147, CVE-2022-2795, CVE-2022-2795, CVE-2022-28327, CVE-2022-3116, CVE-2022-3204, CVE-2022-32221, CVE-2022-35737, CVE-2022-36227, CVE-2022-3627, CVE-2022-37434, CVE-2022-38784, CVE-2022-3970, CVE-2022-40897, CVE-2022-45939, CVE-2022-45939, CVE-2022-4645, CVE-2022-48303, CVE-2023-0795, CVE-2023-0796, CVE-2023-0797, CVE-2023-0798, CVE-2023-0799, CVE-2023-0800, CVE-2023-0801, CVE-2023-0802, CVE-2023-0803, CVE-2023-0804, CVE-2023-1579, CVE-2023-1972, CVE-2023-20883, CVE-2023-23919, CVE-2023-23936, CVE-2023-24807, CVE-2023-2491, CVE-2023-2491, CVE-2023-25658, CVE-2023-25659, CVE-2023-25660, CVE-2023-25662, CVE-2023-25663, CVE-2023-25664, CVE-2023-25665, CVE-2023-25666, CVE-2023-25667, CVE-2023-25668, CVE-2023-25669, CVE-2023-25670, CVE-2023-25671, CVE-2023-25672, CVE-2023-25673, CVE-2023-25674, CVE-2023-25675, CVE-2023-25676, CVE-2023-25801, CVE-2023-26920, CVE-2023-27579, CVE-2023-28617, CVE-2023-32233, CVE-2023-34104, CVE-2023-34104
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 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.
DT215399 You will see a hanging icp4adeploy-ban-job after upgrading if Business Automation Studio was removed from your deployment
DT213078 No Solution is displayed if two or more Project areas are selected in Workflow Center's Case Solutions
DT214376 Unable to expand the toolkits view when viewing application with duplicate dependencies
DT215489 Endless spinning after adding file in ''Create an external automation service''

Back to top

Business Automation Workflow including Automation Workstream Services
Known Issue Title Sec. Cont. B.I.
DT216018 SECURITY - CVE-2023-35024 - Case Builder is vulnerable to a cross site scripting vulnerability when editing document properties X
DT189179 Running Process Portal on Chrome version 109 and later shows an error on the browser console
DT214551 TASK NARRATIVE SECTION IN EMAIL NOTIFICATION IS EMPTY IN PROCESS PORTAL
DT214966

Uploading large documents through ECM intergation using BAW in CP4BA fails due to java.net.SocketTimeoutException: read timed out
DT215160 REST API /OPS/STD/BPM/SAVED_SEARCH_ACCELERATION/OPTIMIZE FAILS TO LOAD DATA INTO SAVED SEARCH ACCELERATION TOOLS TABLE
DT220253 TASK NARRATIVE SECTION IN EMAIL NOTIFICATION IS NOT POPULATED FOR ALL TASKS IN PROCESS PORTAL

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.
DT180451 XML SERIALIZATION ISSUE WHEN USING @XMLROOTELEMENT ANNOTATION IN A JAVA XOM
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
DT209907 CONTENTION WHEN EXECUTING MULTIPLE NEW RULESETS IN PARALLEL
DT211231 DEADLOCK WHEN J2SE CONNECTION POOL PURGE IS ENABLED
DT212881 RULESET PROPERTIES DISAPPEAR WHEN EDITING A DEPLOYMENT CONFIGURATION IN BUSINESS CONSOLE
DT213909 BOM VERBALISATION UNAVAILABLE WHEN AUTHORING SEMANTIC QUERIES IN BUSINESS CONSOLE
DT214728 DECISION CENTER DEPLOYMENT MAY THROW UNEXPECTED BUILD ERROR
DT214763 MERGE FROM BUSINESS CONSOLE THROWS AN EXCEPTION WHEN DEPENDENCIES FOR BOTH BRANCHES DO NOT MATCH
DT215406 UNABLE TO ENFORCE SECURITY OF DECISION SERVICES WITH SHARED PROJECTS
DT215895 WHEN COMPLETING A CHANGE ACTIVITY, CHANGES ARE NOT ALWAYS APPLIED TO RELEASE

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.
DT214551 TASK NARRATIVE SECTION IN EMAIL NOTIFICATION IS EMPTY IN PROCESS PORTAL
DT215160 REST API /OPS/STD/BPM/SAVED_SEARCH_ACCELERATION/OPTIMIZE FAILS TO LOAD DATA INTO SAVED SEARCH ACCELERATION TOOLS TABLE
DT220253 TASK NARRATIVE SECTION IN EMAIL NOTIFICATION IS NOT POPULATED FOR ALL TASKS IN PROCESS PORTAL

Back to top

Known Limitations

Document change history

  • 28 June 2023: Initial publish.

    • [{"Type":"MASTER","Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"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":"22.0.2"}]

    Document Information

    Modified date:
    07 November 2023

    UID

    ibm17001049

    Page Feedback