Features
Data Source Configuration Management
You can add various types of data source configurations. Each configuration represents a data source SOFACLRISK can read from during subsequent checks. Supported types include:
OSS: Read configuration for OSS files. Provide access credentials, endpoint, bucket, and related information.
FTP: Read configuration for files from an FTP system. Provide FTP server access information.
DB: Read configuration for databases. Provide database access settings. It is recommended to use a standby database for checks.
Offline: Access configuration for an offline data warehouse.
Data Source Management
You can add different types of data sources, each representing a data origin that the check system can read during subsequent checks. Supported types include:
File: Specify a file that can be read via an OSS or FTP data source configuration, and configure field delimiters, decoding methods, and other properties.
DB: Specify a database table accessible via a DB data source configuration. Configure sharding, related tables, etc., or filter data directly using SQL.
Data Node Management
You can create a data node to add and manage different types of data nodes. You can complete the mapping as follows:
Map a table in an offline database to a data node. You can add a name and associate a data node with a data node to facilitate the management of data nodes.
Map the file to a check data node, and specify the fields, sorting, and hashing information in the file.
Map the database table to a check data node, and provide the fields that need to be checked in the table, such as sorting and hashing.
All files that need to be used in subsequent checks, such as DB tables and offline tables, should be created as check points.
Check Point Management
Create check points to manage data models to be checked. Add multiple nodes to a check point, and create corresponding check rules within it to maintain a complete check model. Within a check point, you can associate check scenarios, assign an owner, set the check type, and configure the deferred execution delay.
For the same data model (for example, checks from the orders table to the transactions table), all its check rules should be managed within a single check point to facilitate ongoing maintenance.
Check Rule Management
Create rules to perform checks between fund business tables. The rule owner can edit, disable, and enable rules. When a rule is enabled, the system performs periodic checks according to the rule's configured frequency. You can view the execution status for each cycle.
Check Template Management and Import
Create check templates to reuse check data models. For example, multiple businesses may involve checks between summary tables and ledger/flow tables. You can create corresponding templates and rules and import them for reuse across businesses.
Creating a check template is largely the same as creating a check point, and you can add corresponding rules under the template as well.
When creating a check point, you can import a check template for reuse. During import, replace data nodes and update rule names as needed. After import, the corresponding rules and data nodes are automatically added to the target check point.
Check Scenarios
Manually add and maintain check scenarios and specify a scenario when creating a check point, enabling categorized management of check nodes.
Check scenarios support parent-child node management to map multi-level business hierarchies.
Notification Subscription
You can subscribe to notifications about the status, exceptions, and tasks of a rule. You can specify the notification methods and objects.
Anomaly Alerts for Checks
When the system detects difference data and creates an exception event, it will notify you via SMS, email, and platform alerts.
View Difference Data
Review the detailed difference data detected during a single check run. Each run displays up to 10 sampled difference records.
Close Exceptions
Record the reason for an exception to facilitate subsequent reviews. After locating and resolving the root cause, close the exception to update its status, helping stakeholders track handling progress.
Bulk Close False-Positive Exceptions
If rule SQL is not well-designed or business spans partitions such that complete data was not checked, an exception may be a false positive. On the exception list page, select multiple exception events and click Bulk Close to mark them as false positives and add remarks.