1.2 New Features in This Release

The following new features are incorporated in this release CS 8.1.2.9.0.

Patch Installer

In the CS 8.1.2.9.0 Maintenance Level (ML) release, users can follow Patch installer approach instead of a full installer. This method helps to save time by only transferring and applying the necessary changes, avoiding the need to install the entire software package.

Ensure the following before applying CS 8.1.2.9.0:
  • Install CS 8.1.2.8.0.

    (OR)

  • If you have applied any intermediate patches on top of CS 8.1.2.8.0, ensure that you apply all patches up to the latest 8.1.2.8.x version.

    For more information about how to apply this patch, see the OFS Compliance Studio Installation Guide.

Entity Resolution
  • The new ER pipeline (CSA_8129) has been introduced.
  • Users should populate the stg_party_type_master table with the FIC_MIS_DATE before executing any ER jobs.
  • The execution status of the ER_Run_Data_Survival_Engine.sh job has been improved. If the ER job is already triggered and is currently running, users can do the following:
    • Wait for the job to complete.

      (OR)

    • If you suspect the job is stuck due to reasons such as environment issues, database problems, etc., you should terminate the running instance and trigger a new run with RUN_TYPE set to “RERUN”.
  • Log files for the ER_Create_And_Load_Data_Into_Index.sh job have been improved when processing high-volume data for ER batches and loading data into Elastic search/OpenSearch.
Graph
  • Compliance Studio 8.1.2.9.0 includes required changes to support the new Investigation Flow notebook in Investigation Toolkit 8.1.2.9.0.
  • Compliance Studio supports connection pooling configuration from any external schema.
  • Compliance Studio allows Quantifind integration with the Investigation Toolkit.

Common for Both Entity Resolution and Graph

The OpenSearch version has been upgraded from 2.3.0 to 2.18.0.

Interpreter
  • Users can configure R (ore) interpreter in the Compliance Studio. For configuration, see the OFS Compliance Studio Administration and Configuration Guide.
  • The FCC interpreters (fcc-python, fcc-python-ml4aml, and fcc-python-sane) are deprecated. Users with custom notebooks created using these FCC interpreters should migrate to the corresponding eligible Python interpreter to ensure continued functionality.

Custom Scenario is available in Compliance Studio

The Custom Scenario feature allows you to develop and deploy tailored models or scenarios to monitor transactions for suspicious activity. It provides a rich set of pre-engineered features to support the development of such custom scenarios. Events generated by these models can be easily ingested into downstream case management systems for review.

ML4AML
  • Auto Close and Escalate using Machine Learning Customer Screening
    • The Customer Screening solution (Zipper Alerts Management UI) has been integrated with Machine Learning (ML), allowing financial institutions to streamline their compliance workflows, improve productivity, and maintain robust defenses against financial crimes. The ML models aid the compliance users in adjudication of matches, reducing false positives, and enabling more efficient identification of potential risks.
  • Bulk Threshold Uploads in Automated Scenario Calibration
    • Using the Bulk Upload feature, users can create a Threshold Set for the respective scenario, which will be used to execute scenarios in the Scenario Execution Notebook for analysis.
  • Enhancements in Behavioral Model
    • Additional Red Flag features and Base features will allow users to create a wider set of ML models for Transaction Monitoring.