8.2.7 About the Scoring Widget

The Scoring widget enables you to see Transaction Filtering's pre-configured matching rules set.

With respect to the matching rule a score is generated. If the value exceeds the frequency score (the default value is 60) a Alert/Case is generated. If the score is less than the frequency score then the transaction is considered as clean.

TFCS Rule Set

The TFCS Rule Set screen is used to configure scoring rules.

Each Rule Set defines:

• When a rule matches (based on conditions), and
• What score should be produced (either a fixed value or derived from another entity/attribute).

Multiple rule sets can exist on the same page, and an overall Scoring Type determines how scores from matched rule sets are combined.

1. Scoring Type (Top-Level)
   Scoring Type controls how scores from multiple matching rule sets are aggregated:

   • Sum: Add scores from all matched rule sets.
   • Max: Use the highest score among matched rule sets.
   • Average: Use the average score of all matched rule sets.

   This setting applies across the rule sets evaluated within this configuration context.
2. Create New Rule Set
   The “Create New Rule Set” (+) option lets an administrator add a new rule set definition. Each created rule set appears as a separate section with:

   • Rule Set Name
   • Score configuration
   • Condition rows
   • Action buttons (add/edit/delete)
3. Rule Set Header Fields (Per Rule Set)
   1. Rule Set Name

      A descriptive name for the rule set, typically indicating the business purpose (e.g., “Risk vs Amount Threshold”, “Watchlist Screening”, etc.).

      This is used for identification, governance, and maintenance.

   2. Score Type
      Defines how the score is assigned when the rule set matches:

      • value: A fixed numeric score is assigned (e.g., 20, 25).
      • entity: The score is sourced dynamically from a referenced entity/attribute (e.g., read a score field from a joined/related entity).
   3. Score (numeric)

      Shown when Score Type = value.

      This is the fixed score applied if the rule set conditions evaluate to true.

   4. Score Entity / Score Attribute

      Shown when Score Type = entity.

      These fields specify where the score should be retrieved from, typically:

      • Score Entity: The data object/table/view holding the score value.
      • Score Attribute: The column/field that contains the score.
4. Condition Grid (Rule Logic Definition)

   Each rule set contains one or more condition rows. Collectively, these rows define the matching logic for the rule set.

   Column meanings (generic)

   • LHS Entity: The left-hand-side data source (entity/table/view) for the condition.
   • LHS Attribute: The field/column from the LHS entity used in the comparison.
   • Condition Type:
     • value: Compare the LHS attribute to a literal value (number/text/list).
     • entity: Compare the LHS attribute to a field on another entity (RHS).
   • Condition: The operator used for comparison, such as:
     • `==` (equals) - `>=` (greater than or equal)
     • `in` (membership in a list)
     • (other operators may exist depending on the product configuration)
   • Value: The literal value(s) used when Condition Type = value (e.g., a threshold amount, a currency code, a list of message types).
   • RHS Entity / RHS Attribute: The right-hand-side data source and field used when Condition Type = entity (enables attribute-to-attribute comparisons/joins).

   Interpretation: A rule set “matches” when its configured conditions are satisfied based on the runtime data being evaluated.

5. Actions / Icons (Per Rule Set and Per Condition Row)
   You typically see action icons to manage configuration:

   • (+) Add: Add a new condition row (or add configuration element, depending on placement).
   • Edit (pencil): Modify the rule set header or an individual condition row.
   • Delete (trash/bin): Remove the rule set or condition row.
6. What the Screen Enables (Functional Summary)
   This screen enables a rules author to:

   1. Define multiple rule sets with clear business naming.
   2. Configure whether the score is fixed (value) or derived (entity).
   3. Build logical conditions using attributes from one or more entities.
   4. Choose how multiple matched scores are aggregated (Sum/Max/Average).
   5. Maintain rules through add/edit/delete actions.