1.4 Known Issues and Limitations

The following tables lists the Known Issues and Limitations in this release.

Table 1-1 Graph

S.No Bug ID Known Issues and Limitations Workaround
1 35564509 ECM Graph - When a graph pipeline task fails and user "restarts" the run, the failed tasks throw "invalid table name" error. User needs to schedule a new batch with all the failed tasks and re-execute
2 36381673 Event Pipeline fails when the same EVENT_CD comes from different DATA_ORIGIN. NA
3 35953859 Unable to fetch Match Rule and Refresh Graph runtime parameters in schedule configurations UI. NA
4 36993405 Job Monitor UI shows the Match rule job as failure even though the batch is in progress in the backend. NA
5 36779972 Customer to External Entity similarity edges are not visible in graph. Approve action from Manual Decision UI does not work. NA
6 36977898 Unable to create edges between widgets inside Graph Definition UI. Drag and drop the widget towards the right hand side of the UI and then create the edge
7 36997965 Refresh Graph fails when Quantifind is enabled with a fresh installation.

To avoid this error, follow these steps:

  1. Navigate to <COMPLIANCE_STUDIO_IN STALLATION_PATH>/bin directory.
  2. Open config.sh file and update NO_PROXY value as "\"*.$(hostname - d)|localhost|$(hostname - i)|127.0.0.1|0.0.0.0\""
  3. Restart Compliance Studio

Note:

It is Beta functionality with Matching Mechanism as Oracle Text (OT).

Table 1-2 Entity Resolution

S.No Bug ID Known Issues and Limitations Workaround
8 33429546 Name and address transliteration is not happening for both source and target while matching. NA
9 36376217 ER Job 1 fails with deadlock error Intermittently when the Delta Computed is set to False. Re-run the Entity Resolution Job 1
10 36336726 Transliteration does not work for Chinese and Korean languages. NA

Table 1-3 Notebook Server and Interpreters

S.No Bug ID Known Issues and Limitations Workaround
11 36376426 The "Data Studio Options" menu is not visible for a particular user if the "IDENTITY ADMIN" and "IDENTITY AUTH" groups are not assigned. Add "IDENTITY ADMIN" and "IDENTITY AUTH" groups for the user, which should show Data Studio options.

Table 1-4 ML4AML Use Case

S.No Bug ID Known Issues and Limitations Workaround
12 35872579 Scenario execution fails because the default python environment is attached to the notebook. To avoid this issue, follow these steps:
  1. User has to navigate to the newly imported AML scenario notebook.
  2. Attach the proper Python Runtime environment with the session. The recommended value for the Python Runtime environment is default_<version>.

    For more information, see Trigger Scenario Execution section in the OFS Compliance Studio Use Case Guide.

13 36373103 Failure in model fit for a model when parameters "feature_include", and "feature_must_include" are not None and control parameter "find_linear_combos =True". To work, set parameter "find_linear_combos" = False.
14 37808107 Anomaly Scoring with PCAREC Technique is failing for KM, AGNES, and DBSCAN. NA
15 37814999 Unsupervised Model - Getting an error while executing the DBSCAN deviation scoring logic with LDCOF and CBLOF technique. NA
16 38174062 SM - Annual Model Monitoring: BTL Conversion Rate plot is displayed even when there are no valid records. NA
17 38173989 SM - Annual Model Monitoring: Monthly Scenario Alert Summary is not being displayed. NA
18 38173417 SM - Monthly Model Monitoring: Margin Density Paragraph's dataframe is None. NA

Table 1-5 User Activity

S.No Bug ID Known Issues and Limitations Workaround
19 35953842 Data studio's dynamic forms “Drop down” gives error Invalidate the session and execute the notebook again.
20 36975766 User Login - support of user id that contains space and comma. In IDCS configuration, SSO Attribute "username" should be the "lastname"
21 37008227 Schema Creation Fails - Cannot Reuse the Same Name. Create workspace with new name
22 36997284 Meta Service is failing after restarting the Compliance Studio.
To resolve this issue, follow these steps:
  1. Navigate to <OFS_COMPLIANCE_STUDI O_INSTALLATION_PATH>/ deployed/ficdb/ Utilities/ LiquibaseCleanup directory.
  2. In Studio Schema, execute the metaservice_databasec hangelog_cleanup.sql script.
  3. Restart Compliance Studio
23 38171370 The authZType parameter is not being replaced in the application.yml file, and direct login to Data Studio is also not working. To resolve this issue, follow these steps:
  1. Navigate to the <COMPLIANCE_STUDIO_INSTALLATION_PATH>/deployed/mmg-home/mmg-studio/conf directory.
  2. Open the application.yml file.
  3. Under the saml configuration section, add the following line.

    authZType: "<SAML/AAI>"

    Note:
    • If Data Studio retrieve mapped groups from AAI, set authZType to AAI.
    • If Data Studio retrieve mapped groups from IDCS, set authZType to SAML.
  4. Navigate to the <COMPLIANCE_STUDIO_INSTALLATION_PATH>/mmg-home/mmg-studio/conf directory
  5. Open the application.yml file and repeat the same change made in the Step 3.

Table 1-6 Investigation Toolkit

S.No Bug ID Known Issues and Limitations Workaround
24 37876400 The case merge utility does not update the metadata tables during a "concat" operation. NA

Table 1-7 Scenario Conversion Utility

S.No Bug ID Known Issues and Limitations Workaround
25 35943957 Scenario Conversion Utility - The Events are not getting generated for these(ML/AC) Networks of Accounts, Entities, and Customers, (ML/AC) Escalation in Inactive Account scenarios. NA