Delete hearing location¶
This operation removes a hearing location code after delegating an in-use check to the business tier, blocking the deletion when the location is currently referenced.
| Field | Value |
|---|---|
| Operation ID | OP-LGL-012 |
| Trigger | clsHearingLocationManager.DeleteLocation() invoked |
| Inputs | Location code |
| Outputs | Location removed, or blocked with an error message |
| Primary components | clsHearingLocationManager.DeleteLocation |
| Entry point | SAIF.Application.Claim.Legal\clsHearingLocationManager.vb |
Steps¶
DeleteLocation()is invoked for a target location code. The available location codes are populated from the cached HEARING_LOCATION_CODE lookup (SQL-011).- Delegate the "in-use" check to
clsHearingLocation.CanDeleteLocation.
Origin: delegates to
SAIF.Business.Claim.Legal(see operations and processes) — the internal step sequence ofclsHearingLocation.CanDeleteLocationwas not traced in this run's Stage 1 analysis; this callout is inferred/best-effort.* 3. If the check fails (location is in use) (BR-LGL-015): - On failure: block the deletion with"Error: this location is in use and cannot be deleted."4. Otherwise: delete the location.
Process flow¶
The following diagram visualizes this operation's control flow.
flowchart TD
Start([DeleteLocation invoked]) --> Check[clsHearingLocation.CanDeleteLocation]
Check --> InUse{In use?}
InUse -->|Yes| Blocked([Blocked: location in use])
InUse -->|No| Delete[Delete location]
Delete --> EndOk([Done])
Failure and edge-case behavior¶
- Location currently in use: deletion blocked with a user-facing error message; no exception is thrown to the caller.
Note: Statements marked with
*were inferred from code structure, naming conventions, or contextual evidence where direct confirmation was not available in source artifacts.
Related documentation¶
Sources¶
SAIF.Application.Claim.Legal\clsHearingLocationManager.vb