Skip to content

Print a legal letter

Assemble print-ready letter content (attorney names, worker info, policy names) primarily via LegalApi REST calls, resolve case number via LEGAL.vw_cases, and generate a print-document sequence number.

Field Value
Operation ID OP-CLL-018
Trigger User requests a printed letter for a legal case
Inputs Business-object criteria properties set by the caller (see linked SQL parameter tables)
Outputs Persisted/retrieved clsLetterRequest state
Primary components clsLetterRequest, clsLetterRequestCollection
Entry point SAIF.Business.Claim.Legal\Print\clsLetterRequest.vb, Print\clsLetterRequestCollection.vb

Steps

  1. Validate the request against applicable business rules: BR-CLM-LGL-020, BR-CLM-LGL-021, BR-CLM-LGL-022, BR-CLM-LGL-023
  2. On failure: validation errors are collected and returned to the caller; the operation does not proceed.
  3. Execute the underlying data access for clsLetterRequest against: DB-CLL-058, DB-CLL-053
  4. Tables affected: LEGAL.vw_cases
  5. Return the resulting object graph (or success/failure status) to the caller.

Process flow

flowchart TD
    Start([User requests a printed letter for a legal case]) --> Validate[Validate business rules]
    Validate --> Decision{Valid?}
    Decision -->|No| EndErr([Return validation errors])
    Decision -->|Yes| Exec[Execute data access for clsLetterRequest]
    Exec --> EndOk([Return result])

Failure and edge-case behavior

  • Validation failure: the operation returns collected errors without persisting any change.

Sources

  • SAIF.Business.Claim.Legal\ (clsLetterRequest, clsLetterRequestCollection)