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 36779972 Customer to External Entity similarity edges are not visible in graph. Approve action from Manual Decision UI does not work. NA
4 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
5 39239765 Graph Manual Decision : Reject button missing and Approve button misaligned in Pending Approval tab for approver users NA

Table 1-2 Entity Resolution

S.No Bug ID Known Issues and Limitations Workaround
5 36336726 Transliteration does not work for Chinese and Korean languages. NA

Table 1-3 ML4AML Use Case

S.No Bug ID Known Issues and Limitations Workaround
6 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.

7 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.
8 37808107 Anomaly Scoring with PCAREC Technique is failing for KM, AGNES, and DBSCAN. NA
9 37814999 Unsupervised Model - Getting an error while executing the DBSCAN deviation scoring logic with LDCOF and CBLOF technique. NA
10 38174062 SM - Annual Model Monitoring: BTL Conversion Rate plot is displayed even when there are no valid records. NA
11 38173989 SM - Annual Model Monitoring: Monthly Scenario Alert Summary is not being displayed. NA
12 38173417 SM - Monthly Model Monitoring: Margin Density Paragraph's dataframe is None. NA
13 40113502 ISSUE WITH "CREATE AMLES MODELING DATASET / JOIN AMLES TRAIN DATASET WITH TRANSACTIONAL FEATURES" PARAGRAPH  

Table 1-4 User Activity

S.No Bug ID Known Issues and Limitations Workaround
13 35953842 Data studio's dynamic forms “Drop down” gives error. Invalidate the session and execute the notebook again.
14 37008227 Schema Creation Fails - Cannot Reuse the Same Name. Create workspace with new name
15 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
16 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.
17 37387861 The user will not be able to log in to DataStudio directly if the AuthZ flag is enabled. NA
18 38345192 An undefined error is displayed when creating a new workspace and attaching a Conda environment from the Compliance Studio UI. To create the workspace:
  1. In the workspace, click Details.
  2. In the workspace schema, click Edit and attach the Conda environment.
19 38403218 The Compliance Studio UI is not displaying FCC UI contents, and a blank page is observed. NA
20 39944496 THRESHOLD SET NOT LOADED IN ATL OVERLAY NA
21 40025819 THRESHOLD CREATION AND SCENARIO EXECUTION ERROR NA
22 39160456 COMPLIANCE STUDIO 8131 - DTP CONF DEPLOYMENT FAILS WITH ERROR "VALUE TOO LARGE FOR COLUMN AAICL_SS_BATCH_URL Manually update the column length of V_URL of the AAICL_SS_BATCH_URL table if the URL exceeds more than 100 characters.
23 40146409 - CS81320 INSTALLER/LDAP - LDAP_AUTH_PASSWORD PARAM IS NOT EXPORTED AS PART OF MMG-HOME/BIN/INITIALIZE-SECRETS.SH SCRIPT NA
24 40146962 GRAPH MATCH RULE EXECUTION FAILS FOR PARALLEL_LEVEL=8 WITH ERROR "PARALLEL QUERY SERVER DIED UNEXPECTEDLY NA

Table 1-5 Scenario Conversion Utility

S.No Bug ID Known Issues and Limitations Workaround
20 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

Parent topic: Introduction