Retrieve¶
This operation is the public entry point derived managers' UI code calls to (re)load screen data, but it never reports success back to the caller.
| Field | Value |
|---|---|
| Operation ID | OP-CLM-7 |
| Trigger | ClaimAppManager.Retrieve() call |
| Inputs | none |
| Outputs | Always False |
| Primary components | ClaimAppManager.Retrieve, ClaimAppManager.OnValidContext |
| Entry point | SAIF.Application.Claim/ClaimAppManager.vb |
Steps¶
- Evaluate
ValidContext, which callsOnValidContext():ContextSetandSecurityRole <> NoAccessandClaimData.IsValid(BR-CLM-019). - If the context is valid, call
OnRetrieve()— the derived manager's screen-data retrieval (abstract in this library). Retrieve()assigns no return value on any path, so it always returnsFalseregardless of outcome (BR-CLM-020).
Process flow¶
The following diagram visualizes this operation's control flow.
flowchart TD
Start([Retrieve called]) --> Valid{ValidContext?}
Valid -->|Yes| OnRetrieve["OnRetrieve: derived screen<br>load"]
Valid -->|No| Skip[Skip retrieval]
OnRetrieve --> ReturnFalse([Return False])
Skip --> ReturnFalse
Failure and edge-case behavior¶
- Callers cannot use the
Booleanreturn value to detect success; they must instead judge success fromMessage,ValidContext, or manager state.*
Related documentation¶
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