SAIF.Application.Claim operations and processes¶

This page is the operation catalog and cross-operation hub for this library. Each operation's detailed, step-by-step logic lives in its own page under operations/.

Operation catalog¶

Operation	Intent	Trigger	Inputs	Outputs	Rules	SQL
Establish claim context and load a claim	Bind a manager to a claim and load its data	UI screen or derived manager binds a claim	Claim number, claim id, or worker id	Populated `ClaimData`, access classification, user message	BR-CLM-001, BR-CLM-002, BR-CLM-003, BR-CLM-004	—
Evaluate claim access	Determine confidentiality access for the current claim	Invoked from `ChangeContext`	`ClaimData`, `SecurityPrincipal`	`ClaimSecurity` flags, `AppSecurityRole`, denial message	BR-CLM-005, BR-CLM-006, BR-CLM-011, BR-CLM-012	—
Recompute per-claim access flags	Translate claim sensitivity attributes into access flags	Called from claim access evaluation or directly by a consumer	`clsClaimData`	Four boolean access flags	BR-CLM-007, BR-CLM-008, BR-CLM-009, BR-CLM-010	—
Initialize the claim manager and data layer	Provision the Oracle claim data portal	`AppManagerBase.Initialize()` template method	none	`IDataPortalInfo` handle (`ClaimDPI`)	BR-CLM-013, BR-CLM-014	—
Transaction-bracketed save	Persist claim changes inside a managed transaction	UI save action on a derived manager	none (uses current context)	Success flag	BR-CLM-015, BR-CLM-016	—
Generate and save claim tasks	Raise and persist claim tasks during a save	Derived manager needing to raise claim tasks	`inMultiClaim` flag	Success flag	BR-CLM-017, BR-CLM-018	—
Retrieve	Gate screen-data retrieval on a valid context	`Retrieve()` call	none	Always `False`	BR-CLM-019, BR-CLM-020	—
Resolve ancillary handles	Build the claim application title, employee data, and imaging client	First access of `ApplicationTitle`, `EmployeeData`, or `ClaimImageApiClient`	Current claim/user context	Title string, employee record, imaging client	BR-CLM-021, BR-CLM-022	—

Process flow diagram¶

The following diagram visualizes the primary operational flow across operations.

flowchart TD
    Start([Set*Context called]) --> Valid{Key valid?}
    Valid -->|No| ClearCtx(["Message: enter valid claim<br>number"])
    Valid -->|Yes| ChangeCtx[ChangeContext]
    ChangeCtx --> Retrieve1[OnContextChanged: load claim]
    Retrieve1 --> Found{Claim valid?}
    Found -->|No| NotFound([Message: claim not found])
    Found -->|Yes| CheckSec["OnCheckSecurity: evaluate<br>access"]
    CheckSec --> Conflict{Conflict access denied?}
    Conflict -->|Yes, no override| NoAccess(["MarkNoAccess + denial<br>message"])
    Conflict -->|No, or override granted| ViewOnly[MarkViewOnly]
    ViewOnly --> OnRetrieve["OnRetrieve: derived screen<br>load"]

Inherited operations and processes¶

Operations in this section originate from base classes or services provided by dependency framework libraries. They are inherited or delegated, not implemented in this library.

From `AppManagerBase` (`SAIF.Application`)¶

Operation	Intent	Provided by	Origin	Embedded in
Initialize template method	Invokes `OnInitialize()` then `OnCreateDataLayer()` during manager construction	`AppManagerBase`	`SAIF.Application`	Initialize the claim manager and data layer

Origin: This operation is defined in SAIF.Application / AppManagerBase and inherited or delegated by this component. Its step-by-step logic is embedded inline (with > Origin callouts) in the consuming operation's detail page.

Database interactions¶

This library owns no SQL; all claim data access is delegated to SAIF.BOF.Business.View.Claim (clsClaimData, clsEmployeeData, ClaimServices) and claim task persistence to SAIF.Business.Tasks.Claim (clsClaimTaskGenerator). No SQL objects or tables were traced within this library — see the operation detail pages for delegated call sites.**

Failure and edge-case behavior¶

An invalid claim key short-circuits context establishment with no database access (BR-CLM-001).
A not-found claim leaves the context unset with a "claim not found" message; no exception is thrown.
OnCheckSecurity dereferences ClaimData without a null guard; whether a worker-only context or a failed retrieval can reach this path in production is unknown.**
A save failure (exception or False result) always rolls back the transaction (BR-CLM-016).

Note: Statements marked with * were inferred from code structure, naming conventions, or contextual evidence where direct confirmation was not available in source artifacts. Statements marked with ** could not be confirmed; treat as unknown until verified.

Sources¶

SAIF.Application.Claim/ClaimAppManager.vb
SAIF.Application.Claim/ClaimSecurity.vb
SAIF.Application.Claim/ClaimContext.vb
SAIF.Application.Claim/ClaimAppConstants.vb