Skip to content

Manage hearing locations

Maintain hearing-location reference data (create, retrieve, update, delete) and validate state codes, guarding delete when active schedule rows exist.

Field Value
Operation ID OP-CLL-014
Trigger Reference-data maintenance user adds, edits, or deletes a hearing location
Inputs Business-object criteria properties set by the caller (see linked SQL parameter tables)
Outputs Persisted/retrieved clsHearingLocationInfo state
Primary components clsHearingLocationInfo, clsHearingLocation
Entry point SAIF.Business.Claim.Legal\LegalNet\clsHearingLocationInfo.vb, TableMaint\clsHearingLocation.vb

Steps

  1. Validate the request against applicable business rules: BR-CLM-LGL-012, BR-CLM-LGL-013
  2. On failure: validation errors are collected and returned to the caller; the operation does not proceed.
  3. Execute the underlying data access for clsHearingLocationInfo against: DB-CLL-032, DB-CLL-062, DB-CLL-063, DB-CLL-065-104
  4. Tables affected: HEARING_LOCATION, SCHEDULE, ALL_STATES
  5. Return the resulting object graph (or success/failure status) to the caller.

Process flow

flowchart TD
    Start([Reference-data maintenance user adds, edits, or deletes a hearing location]) --> Validate[Validate business rules]
    Validate --> Decision{Valid?}
    Decision -->|No| EndErr([Return validation errors])
    Decision -->|Yes| Exec[Execute data access for clsHearingLocationInfo]
    Exec --> EndOk([Return result])

Failure and edge-case behavior

  • Validation failure: the operation returns collected errors without persisting any change.
  • ValidateState on this path is non-parameterized (raw string concatenation) — see business-rules.md for the flagged SQL-injection risk.

Sources

  • SAIF.Business.Claim.Legal\ (clsHearingLocationInfo, clsHearingLocation)