Release 4.0.0 link to all user stories for all new features

[Sandy-at-Tazama]

TAZAMA CONNECTION STUDIO (TCS)

TCS:

• 1.1 User Story: Define New API Endpoints #300
• 1.2 User Story: Field Mapping and Data Transformation #301
• 1.3 User Story: Dry-Run of Configuration #302
• 1.4 User Story: Submit Endpoint for Approval #303
• 1.5 User Story: Clone and Modify Existing API Endpoints #331
• 1.6 User Story: Approve Configuration Packages #332
• 1.7 User Story: Reject Configuration Packages #333
• 1.8 User Story: Deploy Configuration Package to Target Environment #334
• 1.9 User Story: Function Configuration via TCS #358

DEMS:

• 2.1 User Story: Notify DEMS on New Configuration #339
• 2.2 User Story: Load & Cache Configurations #340
• 2.3 User Story: Ingest & Validate Messages #341
• 2.4 User Story: Handle Data Transformation and Validation Failures #342

DE API:

• 3.1(a) User Story: Define File-Based Pull Jobs (via TCS UI) #335
• 3.1(b) User Story: Schedule Pull Jobs with CRON (non-UI) #336
• 3.2 User Story: Push-Based Data Enrichment via REST APIs #337
• 3.3 User Story: Approve Enrichment Endpoint Definitions #346
• 3.4 User Story: Reject Enrichment Endpoint Configuration #350
• 3.5 User Story: Publish Enrichment Endpoint Definitions #347
• 3.6 User Story: CRON Job Configuration for Pull-based Data Enrichment #359

RELAY SERVICE ENHANCEMENT

known-to-known without decoding:

• 1A: Relay from NATS to NATS (Known destination) #168
• 1B: Relay from NATS to Kafka (Known destination) #169
• 1C: Relay from NATS to RabbitMQ (Known destination) #170
• 1D: Relay from NATS to REST API (Known destination) #171

known-to-known with decoding:

• 2A: Decode Protobuf from NATS and Relay JSON to NATS (Known destination) #172
• 2B: Decode Protobuf from NATS and Relay JSON to Kafka (Known destination) #173
• 2C: Decode Protobuf from NATS and Relay JSON to RabbitMQ (Known destination) #174
• 2D: Decode Protobuf from NATS and Send JSON to REST API (Known destination) #175

known-to-unknown with decoding:

• 3A: Decode Protobuf from NATS and Relay JSON to NATS (Unknown Destination) #176
• 3B: Decode Protobuf from NATS and Relay JSON to Kafka (Unknown Destination) #177
• 3C: Decode Protobuf from NATS and Relay JSON to RabbitMQ (Unknown Destination) #178
• 3D: Decode Protobuf from NATS and Send JSON to REST API (Unknown Destination) #179

ALERT TRIAGE MODULE

• 1-A Auto-Trigger Triage Task for New Alerts #213
• 1-B Auto-Close False Positive Alert with No Transaction or AML Suspicion #214
• 1-C Auto-Close True Positive Alert #215
• 1-D Investigate Confirmed Alert with Transaction Occurrence #216
• 1-E Investigate Confirmed Alert with Money Laundering Suspicion #217
• 1-F Investigate Alert with Low Confidence Prediction #218
• 1-G Default to Manual Investigation When No Confidence Threshold is Configured #219
• 1-H Bypass Triage If Module is Disabled #220
• 1-I Split Cases for Fraud and AML Investigations #221
• 1-J Prioritize Alerts for Investigation Based on Configurable Attributes #222
• Manual Alerts Handling #281

CASE MANAGEMENT SYSTEM

Create a New Case:

• 1-A Case Creation by system-to-system transmission (ideal path) #185

• System-to-system transmission (Alert-Triage disabled) #315

• System-to-system transmission (Alert-Triage enabled investigation required) #316

• Manual Case Creation #321

  • Case Creation by a Supervisor #322
  • Case Creation by Analyst #345

Complete Case Creation:

• 2A Title: Completing a Saved Case Creation #196
• 2B Title: Case Update Failure During Completion #197
• 2C Title: Abandoning a Saved Case #198

Approve Case Creation:

• 3A Title: Supervisor Approves Case Creation #199
• 3B Title: Supervisor Rejects Case Creation #202
• 3C Title: Supervisor Approval Failure #240

Approve Case Creation:

• 3A Title: Supervisor Approves Case Creation #199
• 3B Title: Supervisor Rejects Case Creation #202
• 3C Title: Supervisor Approval Failure #240

Assign (Reassign) a Task:

• 4A Title: Assigning a Task to a User (Supervisor) #200
• 4B Title: Reassigning a Task to Another User #201
• 4C Title: Task Assignment Failure #241
• 4D Title: Task Assignment to Invalid User #242
• View work queue #317

Unassign a Task:

• 5-A Unassigning a Task #244
• 5-B Unassign Task Failure #245

Suspend a Case:

• 6-A Suspending a Case #248
• 6-B Case Suspension Failure #249

Resume a Case:

• 7-A Resume a Suspended Case #251
• 7-B Resume Case Failure #252

Close a Case:

• 8-A Closing a Case #254
• 8-B Case Closure Failure #256

Approve Case Closure:

• 9-A Supervisor Approves Case Closure #258
• 9-B Supervisor Rejects Case Closure #259
• 9-C Case Closure Approval Failure #260

Reopen a Case:

• 10-A Reopening a Case #262
• 10-B Case Reopening Failure #263

Approve Case Reopening:

• 11-A Supervisor Approves Case Reopening #265
• 11-B Supervisor Rejects Case Reopening #266

Reporting:

• 12-A Generate Reports #268

Case Queue and Work Queue Management:

• 13-A Creating Work Queues #270
• 13-B Assigning Users to Work Queues #271
• 13-C Reassigning Tasks Between Work Queues #272
• 13-D Monitoring Task Progress in Work Queues #273
• 13-E Case Queue and Work Queue Management #274
• 13-F System Notifications for Task Assignments #275

AI Task:

• AI Task (ATM module) - API integration #329

INVESTIGATIONS & VISUALIZATIONS

Investigations

Epic 1: Evidence Collection

• 1.1 User Story – Collect and Analyze Evidence #381
• 1.2 User Story – Attach Sanctions Screening Result #382
• 1.3 User Story – Attach Adverse Media Screening Result #383
• 1.4 User Story – Attach SAR/STR Filing Evidence #384
• 1.5 User Story – Store Evidence in Tamper-Protected Repository #385
• 1.6 User Story – View Evidence in Reports Module #386
• 1.7 User Story - Attach KYC and EDD report #398

Epic 2: Fraud & AML:

• 2.1 User Story – Compile Fraud Report #388
• 2.2 User Story – Profile Transactions (30–90 Days) #389

Common Features across System:

• 3.1 User Story – Integrate CMS with DLH for Transaction Data #393

Visualizations

• 1. User Story: Alert Navigator #410
• 2. User Story: Transaction Detail View #411
• 3. User Story: Transaction History Analysis #412
• 4. User Story: Benford’s Law Distribution Analysis #413
• 5. User Story: Network Navigator #414
• 6. User Story: Transaction Network Analysis #415
• 7. User Story: Account Network Analysis #416
• 8. User Story: Counterparty Network Analysis #417
• 9. User Story: Alert History View #418
• 10. User Story: Conditions View #419
• 11. User Story: Integration of CIMS with JupyterHub for Visualization Fetching #420

BIAR (Business Intelligence and Reporting)

BIAR

• CIMS-1. Store and retrieve unstructured artifacts (CouchDB) #375
• TIKA-1. Extract text and metadata from unstructured artifacts #377
• SOLR-1. Index extracted metadata into Apache Solr #379
• BIAR-1. Ingest the extracted metadata to Raw Layer #378
• DLH-1 Land immutable raw data in Apache Ozone using Apache Nifi #365
• PIPE-1. Apache Spark processing with checkpoints #366
• DLH-2. Create Bronze Apache Hudi (Copy-On-Write) tables with Apache Spark #367
• DLH-3. Silver enrichment & schema evolution (Apache Hudi) #368
• DLH-4. Curated Gold marts for BI/ML #369
• PIPE-2a. Stream ingest (real-time) #370
• PIPE-2b. Trickle ingest (small deltas) #371
• PIPE-2c. Batch ingest (bulk backfill) #372
• PIPE-3. ETL contract tests #373
• PIPE-4. Operational monitoring & alerting #374
• BI-1. JupyterHub multi-user access to Gold #380

AI

• AICAL-1 Calibration #396
• AIANOM -1 Anomaly Detection #397

Dashboard

• User Story - 1 METRICES #448
• User Story: Executive Overview Dashboard #449
• User Story: TMS Performance Dashboard #450
• User Story: Fraud Trend Analysis Dashboard #451
• User Story: Fraud Typology Effectiveness Dashboard #452
• User Story: Case Management Trend Dashboard #453
• User Story: Case Tracking Analysis Dashboard #573

MODEL MANAGEMENT

Rule Builder

• 1.1 User Story: Secure Login for All Roles #421
• 1.2 User Story: Create New Rule Setup #422
• 1.3 User Story: Parse and Extract Variables from Sample Payload #423
• 1.4 User Story: Rule Building #424
• 1.5 User Story: Graphical Nodes Addition #425
• 1.6 User Story: Using Defined Global Variables #426
• 1.7 User Story: Graphical Nodes Configuration #427
• 1.8 User Story: Connecting Graphical Nodes #428
• 1.9 User Story: View Complete Rule before Validation #429
• 1.10 User Story: Run Validation on a Rule #430
• 1.11 User Story: Setting up RBAC for Governance #433
  
• 1.12 User Story: View Rule Library #438
• 1.13 User story: Search Rule Library #439

Test Cases Generation

• 01 - Navigate to Test Case Generator #472
• 02 - Load Base Template in Graphical Interpreter #473
• 03 - Add Predefined Function Node #474
• 04 - Add Setup Nodes (Describe / BeforeEach) #475
• 05 - Add Test Scenario Node #476
• 06 - Generate Code against Test Case Definition #482
• 07 - Validate Test Cases via Play Mode #483
• 08 - Backend for Test Cases Generation #598

Simulation Sandbox

• US-SS-01 — Navigate to Simulation Sandbox #491
• US-SS-02 — Select Simulation Scope and Depth #492
• US-SS-04 — Deploy Configuration to Staging for Simulation #494
• 04 - Add Setup Nodes (Describe / BeforeEach) #475
• US-SS-05A — Execute Rule Unit Simulation Using Test Cases #495
• US-SS-05B — Rule Execution via NATS-Utilities #496
• US-SS-05C — Execute End-to-End Simulation Across Tazama System #497
• US-SS-06 — Iterate and Refine Based on Simulation #498
• US-SS-14 — Suspending a Rule #506
• US-SS-18 - GitHub-backed Rule & Testcase Initialization #556
• US-SS-08 — Submit Configuration Package for Review #500
• US-SS-10 — Review and Approve Rule #502
• US-SS-13 — CI/CD-Driven Workflow from Staging to Production #505
• US-SS-11 — Deploy Approved Configuration to Production #503
• US-SS-12 — Revert Rule Package to Maker After Review #504
• US-SS-17 — Clone an Existing Rule #509
• US-SS-03 — Select Dataset for Simulation #493
• US-SS-19 - Role-Based Email Notifications Across Rule Lifecycle #617
• US-SS-20 - Test Rule by modifying payload fields #618

Simulation & Masking

• US-AC-001 — Modal Visibility is Restricted by Role #699
• US-TOK-001 — View the Message Tokenization Dashboard #700
• US-TOK-002 — Create a New Tokenization Configuration — Select Message Type and Version #701
• 04 - Add Setup Nodes (Describe / BeforeEach) #475
• US-INT-001 — TRS Fetches Active Message Types from TCS for Masking Configuration #718
• US-MASK-003 — View the Message Payload and Schema in the Masking Wizard #702
• US-MASK-004 — Apply Pre-Defined Field-Level Tokenization Templates #703
• US-MASK-005 — View Pre-Highlighted PII Fields and Configuration Summary Before Saving #704
• US-MASK-006 — Save and Submit Masking Configuration for Checker Approval #705
• US-MASK-007 — View Masking Configurations Pending Approval #706
• US-MASK-008 — View Full Details of a Masking Configuration #707
• US-MASK-009 — Approve a Masking Configuration #708
• US-INT-002 — Approved Tokenization Configuration is Activated in DLH Bronze Layer #719
• US-MASK-010 — Reject a Masking Configuration and Return It to the Maker #709
• US-SIM-001 — Access the Simulation Modal #710
• US-SIM-002 — View Simulation History and Revisit Past Simulation Results #711
• US-SIM-003 — Select Date and Time Range for Simulation Data #712
• US-SIM-004 — Fetch tokenized Transaction Data from DLH for Simulation #713
• US-SIM-005 — Run Simulation — Replay Messages Through DEMS #714
• US-SIM-006 — View Real-Time Evaluation Results and Logs Per Message #715
• US-SIM-007 — View Expanded Simulation Results for an Individual Message #716
• US-SIM-008 — View Overall Simulation Summary #717
• US-INT-003 — TRS Queries DLH Bronze Layer for Simulation Data via Secure Gateway #720
• US-INT-004 — DLH Bronze Layer Masks and Packages Data on Simulation Fetch Request #721
• US-INT-005 — DLH Packages, Encrypts, and Transfers Simulation Data to TRS Dev #722
• US-INT-006 — TRS Dev Feeds Messages into DEMS Dev One by One for Simulation #723
• US-INT-007 — DEMS Dev Streams Evaluation Results Back to TRS Simulation Modal in Real Time #724