1. Overview

Signals are custom identifiers that can be returned as part of a response when specific rules are triggered. Unlike standard recommendations such as "Block" or "Review," signals provide additional context or actions for the user. They act as flags for specific detected conditions and can trigger follow-up actions within the system or user system.

2. Purpose of Signals

Signals enhance the flexibility of the rule framework(s) by allowing the system to react to complex scenarios that require additional actions beyond approving or blocking a request. Examples include:

• Requesting additional documentation for a transaction.

• Flagging an entity for enhanced due diligence.

• Triggering the collection of a digital KYC form link.

• Initiating electronic identification.

3. Signal Configuration

Each signal is uniquely identified and associated with triggered rules. Users can configure signals based on specific business needs and regulatory requirements.

Signal Properties

A signal consists of the following attributes:

• ID: A unique identifier for the signal.

• Name: A descriptive label that uniquely identifies the signal.

• Active Status: Determines whether the signal is currently active and can be assigned to new requests.

• CreatedAt: The timestamp when the signal was created.

• UpdatedAt: The timestamp when the signal was last updated.

4. Managing Signals

Retrieving a List of Signals

Users can retrieve all stored signals in the system. Query parameters allow filtering and sorting:

• Sorting Options: Users can sort by id or createdAt.

• Order: Sort results in ascending (ASC) or descending (DESC) order.

• Active Filter: Retrieve only active signals.

• Pagination: Specify _start and _end values to retrieve a specific range of results.

5. Creating a Signal

To create a new signal, users must provide:

• Name: A unique identifier for the signal.

• Active Status: Determines if the signal is available for use.

6. Updating a Signal

Existing signals can be modified by specifying:

• ID: The unique identifier of the signal.

• Updated Name: If the signal needs renaming.

• Active Status Change: Signals can be activated or deactivated as needed.

7. Using Signals in Rule Execution

When a rule is triggered, the system evaluates whether a corresponding signal should be included in the response. Signals do not replace the main recommendation (such as "Block", "Review" or "Proceed") but supplement it, providing additional guidance.

For example:

• If an entity has been flagged for suspicious activity, a "Trigger_Enhanced_Due_Diligence" signal could be issued.

• If additional KYC information is needed, a "Trigger_Digital_KYC_Form" signal might be generated.

• If electronic identification is required, a "Initiate_Electronic_Identification" signal could be sent.

8. Summary

Signals serve as an additional layer of insight and action in the rule framework. By leveraging signals, organizations can implement more nuanced and dynamic risk management strategies while maintaining compliance and operational efficiency.