Legal case queries

Resolve a claim id for a legal case, resolve preferred employee names, and retrieve financial transactions by invoice number.

Field	Value
Operation ID	OP-SD-18
Trigger	Legal case processing workflow.
Inputs	Case number(s), invoice number
Outputs	Claim id, name, payment
Primary components	LegalQueryProvider
Entry point	Data/SAIF.Data/Queries/Legal/LegalQueryProvider.cs

Steps

1. GetClaimIdForCase: try the CC API first, then fall back to the WCB, BRB, DCBS, OALJ and OWCP numbers, in order (SD-BR-060, SQL-152, SQL-153, SQL-154, SQL-155, SQL-156, SQL-157). Delegates: CCClaimApiService. Data: LegalCase (LEGAL_CASE).
2. GetAdpEmployeeName: use the preferred name when present, otherwise the legal name (SD-BR-061).
3. GetFinancialTransaction: get the payment by invoice number.

   Origin: This step delegates to FinancialDataApiClient.GetPaymentsByInvoiceNumber, implemented in SAIF.Data.Guidewire, which issues a cached GET of payments?invoiceNumber={invoiceNumber} and optionally includes zero-pay payments.

Process flow

The following diagram visualizes this operation's control flow.

flowchart TD
    Start([Legal case processing workflow.]) --> S1["`LegalQueryProvider`"]
    S1 --> S2{"Rules satisfied?"}
    S2 -->|Yes| EndOk([Result returned])
    S2 -->|No| EndErr([Exception / empty result])

Failure and edge-case behavior

• No case number resolves to a claim: GetClaimIdForCase falls through all five sources and returns none found*.

Related documentation

• Operations and processes
• Business rules
• SQL catalog
• Database tables

Sources

• Data/SAIF.Data/Queries/Legal/LegalQueryProvider.cs
• Data/SAIF.Data/Queries/Legal/LegalQueryProvider.cs:35
• Data/SAIF.Data/Queries/Legal/LegalQueryProvider.cs:40
• Data/SAIF.Data/Queries/Legal/LegalQueryProvider.cs:55