Known limitations and issues

When you create an application in Business Automation Studio, an application configurator displays where you enter configuration parameters for the application.

However, after the application is created you cannot access the same configurator. As a result, you cannot change the configuration settings the same way.

Workaround

In the Batch Document Processing template, use the view configurator for the Verify Data page.

In the Document Processing template, use the view configurator for the VerifyPage.

At processing time, circumstances can occur where the Content Analyzer can return multiple KeyClass entries with the same name in the KVP Table of the extracted JSON. For example:

• A defined field exists on a page or across multiple pages.
• A field has multiple aliases that match multiple values on a page.

Mitigation

When you have multiple field values that are encountered during finalization, the value from the last field is set and any additional entries are ignored.

Mitigation

Use the mouse to select elements.

Mitigation

For the training documents only. (Not for the production runtime documents): Update the key class name, delete the training documents, reupload, reannotate, and then retrain the model.

If you define a new required field after you used samples to teach the model, and then run the sample again to train the model, the model does not account for the missing value of the required field. You must add a new sample to refresh the data.

The Datatype Mismatch validator and the Required Value validator from the pre-trained extraction model are intended to return an error if the conditions are not met. However, the two validators return an informational severity instead of an error.

You can fix this issue by updating the severity settings for any field that uses the validator. When you edit the validator, you can override the severity setting and specify an error or warning instead of informational. You need to make this update for every field that uses the validator. You do not need to retrain the model after this update, but you must redeploy the project after this update.

In each sample document, make sure that the Undefined data tab does not contain any fields with an empty captured field.

The composite data is persisted as a JSON format in a string property. Currently, the keyclass field names are stored without any values in Content Platform Engine. For example:

{"CustName":"","InvoiceNumber":"","InvoiceDate":""}

To find the value of the composite data, check the content.json file that is persisted as an annotation object along with the document.

• Decision rules
• Case management
• Content analyzer
• Process management

To correct the issue, you must configure the service so that it uses the UMS instance of Digital Worker and uses the REST API skill.

1. Undeploy the task.
2. In your skills list, select Edit skill and take note of the skills configuration and name.
3. Remove the skills from the task.
4. Add the skills again with the latest version, and use the same configuration and name as before.

• You scale down the StatefulSet runtime
• This particular runtime Pod crashes

Before you scale down, make sure that no tasks are running. Be prepared to restart a task after a runtime Pod crash.

For example, if you are deploying a task and get an error, this can be because another user added some incomplete instructions in the meantime, which prevents any deployment at this moment.

To avoid this issue, do not use a client_ID in several applications.

If you deployed Business Automation Studio with the Business Automation Workflow server on container instances in the same custom resource YAML file, but you don't see process applications from Business Automation Workflow server on container instances in Business Automation Studio, restart the Business Automation Workflow server on the container instance pod.

If you use the kubectl get podscommand to check the pods when a pod is in the CrashLoopBackOff state, you get the following error message:

Warning Failed 3m kubelet, 172.16.191.220 Error: failed to start container: Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "process_linux.go:402: container init caused \"rootfs_linux.go:58: mounting \\\"/var/lib/kubelet/pods/69e99228-b890-11e9-81c0-00163e01b43c/volume-subpaths/key-trust-store/ibm-dba-ums/2\\\" to rootfs \\\"/var/lib/docker/overlay2/0f50004756b6e39e6da16f57d7fdb9f72898bc8a5748681218a7b1b20eb0612b/merged\\\" at \\\"/var/lib/docker/overlay2/0f50004756b6e39e6da16f57d7fdb9f72898bc8a5748681218a7b1b20eb0612b/merged/opt/ibm/wlp/usr/shared/resources/security/keystore/jks/server.jks\\\" caused \\\"no such file or directory\\\"\"": unknown

To recover a pod, delete it in the OpenShift console and create a new pod.

To use IBM Business Automation Application Engine (Application Engine) with Db2® for High Availability and Disaster Recovery (HADR), you must have an alternative server available when Application Engine starts.

IBM Resource Registry can get out of sync.

After you create the Resource Registry, you must keep the replica size.

• If you update the Resource Registry admin secret to change the username or password, first delete the instance_name-dba-rr-random_value pods to cause Resource Registry to enable the updates. Alternatively, you can enable the update manually with etcd commands.
• If you update the Resource Registry configurations in the icp4acluster custom resource instance, the update might not affect the Resource Registry pod directly. It affects the newly created pods when you increase the number of replicas.

After you deploy Business Automation Studio or Application Engine, you can't change the Business Automation Studio or Application Engine admin user.

Because of a Node.js server limitation, Application Engine trusts only root CA.

• The certificate can be self-signed, or signed by a well-known root CA.
• If you are using a depth zero self-signed certificate, it must be listed as a trusted certificate.
• If you are using a certificate that is signed by a self-signed root CA, the self-signed CA must be in the trusted list. Using a leaf certificate in the trusted list is not supported.
• If you are adding the root CA of two or more external services to the Application Engine trust list, you can't use the same common name for those root CAs.

Business Automation Studio and Application Engine support only the IBM Db2 database.

The Java™ Message Service (JMS) statefulset doesn't support scale.

For information about manually creating additional data source definitions to include in the configDropins/overrides for the FileNet® Content Manager and Business Automation Navigator containers, see Tuning IBM WebSphere® Liberty for FileNet Content Manager components.

(Fixed in 20.0.2.1) In the 20.0.2.1 version, a new parameter called dc_os_label is added that lets you specify a label per object store definition in the CR YAML. You use that same label in the ibm-fncm-secret that you create to specify separate data source login credentials for each object store data source. For more information, see Creating secrets to protect sensitive configuration data.

For more information and to resolve the issue, see Content Platform Engine uneven CBR indexing workload and indexing degradation.

1. Log in to the Navigator admin desktop.
2. Click Settings, change Navigator Mode to Platform and Content, and click Save.
3. Refresh the browser to make the change effective.
4. Reopen the Settings tab to confirm that the Upload File Path on Server setting is available.
5. (Optional) Change the Navigator Mode setting back to Platform, if needed. The upload path is still valid even if the setting cannot be shown.

Start the configuration again. This error usually displays only one time, and you can complete the configuration if you start it again.

When you configure emitters with Event Streams in Business Automation Workflow on containers, enable either the Business Automation Workflow Process Emitter or Case Emitter, not both.

•  For 20.0.1  Salted Challenge Response Authentication Mechanism (SCRAM) is not supported. Plain SSL, SSL with username and password, SSL with Kerberos authentication, and Kerberos authentication are supported.
•  New in 20.0.2  Salted Challenge Response Authentication Mechanism (SCRAM) is supported only in its SCRAM-SHA-512 variant. Plain SSL, SSL with username and password, SSL with Kerberos authentication, and Kerberos authentication are supported.
•  New in 20.0.3  Kafka Kerberos configuration is not supported.

Defining a high number of fields in an Elasticsearch index might lead to a so-called mappings explosion which might cause out-of-memory errors and difficult situations to recover from. The maximum number of fields in Elasticsearch indexes created by IBM Business Automation Insights is set to 1000. Field and object mappings, and field aliases, count towards this limit. Ensure that the various documents that are stored in Elasticsearch indexes do not lead to reaching this limit.

For more information, see BPMN summary event formats, Case and activity summary event formats, and the Settings to prevent mappings explosion page of the Elasticsearch documentation.

If some older Elasticsearch or HDFS data is pushed by the older Case event emitter, follow the replay procedure to clear the old data. Use the new Case event emitter that is released with IBM Business Automation Workflow 18.0.0.2 interim fix 8.6.10018002-WS-BPM-IFPJ45625, or IBM Business Automation Workflow 19.0.0.1 or higher fix pack to push the events.

For more information about the replay procedure, see Replaying Case events.

To avoid this issue, edit the filter in the User tasks currently waiting to be processed search. Set the state filter to accept one of the following values: TASK_CREATED, TASK_STARTED, TASK_CLAIM_CANCELLED, TASK_CLAIMED.