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.

Fields that contain white text must be on a solid black background.

Mitigation

This issue can be corrected by saving the document from the detailed document issues page.

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 more information and to resolve the issue, see Content Platform Engine uneven CBR indexing workload and indexing degradation.

• Ensure that cpe is deployed in a highly available setup, with at least two replicas.
• Monitor the cpe pod and restart if issues occur.
• On the cpe pod, consider setting the disable_fips production parameter to "true" for any environments where FIPS is not required.

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 indices 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 indices do not lead to reaching this limit.

Event formats are documented in Reference for event emission.

For Operational Decision Manager, you can configure event processing to avoid the risk of mappings explosion. See Operational Decision Manager event processing walkthrough. For 21.0.1 This walkthrough is not available.

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.

Similarly, you get version 20.0.3 of Business Performance Center.

For 21.0.1 The patch is not available.

For 21.0.1 This parameter is not available.