SAIF.Application.Claim operations and processes¶
This page is the operation catalog and cross-operation hub for SAIF.Application.Claim. The library extends the BOF application framework with claim-specific context entry, security evaluation, retrieval/write orchestration, task generation, and data-portal initialization for ClaimAppManager subclasses. Each operation's detailed, step-by-step logic lives in its own page under operations/.
This library has no direct database interactions of its own; all data access is delegated to referenced libraries (see Inherited operations and processes below). Accordingly, the catalog omits Tables and SQL columns.
Operation catalog¶
| Operation | Intent | Trigger | Inputs | Outputs | Rules |
|---|---|---|---|---|---|
| Set claim context | Load an application session by claim number or claim ID | Caller calls SetClaimContext(String) or SetClaimContext(Decimal) |
Claim number or claim ID | Active claim context, claim data, security snapshot, subclass retrieval state | BR-001, BR-002, BR-003, BR-004, BR-006 |
| Set worker context | Load an application session from a worker identifier | Caller calls SetWorkerContext(Decimal) |
Worker ID | Active worker-scoped claim context, claim lookup attempt, security snapshot, subclass retrieval state | BR-001, BR-002, BR-003, BR-004 |
| Retrieve claim application data | Re-run application-specific retrieval for the current valid context | Caller calls Retrieve() |
Active claim context | Refreshed application data (when context is valid) | BR-005 |
| Write claim application changes | Run the subclass save path inside an Oracle transaction | Caller calls Write() |
Pending application changes | Commit or rollback result | None documented* |
| Generate claim tasks | Create and optionally save claim-task work items for the active claim or multiple claims | Subclass calls NewTaskGenerator and optionally SaveTasks |
Claim context or multi-claim flag | Populated clsClaimTaskGenerator state and save result |
None documented* |
| Initialize claim data portal | Prepare the claim data portal and default messaging for the manager instance | AppManagerBase initialization sequence calls OnInitialize/OnCreateDataLayer |
Security principal and environment configuration | ClaimDPI Oracle portal and initial status message |
None documented* |
Process flow diagram¶
The following diagram shows the common context-entry flow through the library, converging on the shared security-evaluation and retrieval pipeline.
flowchart TD
Start([Caller requests claim<br>or worker context]) --> Context[Create ClaimContext]
Context --> Load[GetClaimData via<br>clsClaimData.GetData]
Load --> Security[CheckClaim: conflict, exposure,<br>hostile, health-issue access]
Security --> Override{Conflict access denied?}
Override -->|Yes, no override| NoAccess([MarkNoAccess;<br>confidential-access message])
Override -->|No, or override granted| Retrieve[Run subclass OnRetrieve]
Retrieve --> Result([Return application state])
Result --> RefreshCall{Caller invokes Retrieve again?}
RefreshCall -->|Yes| ValidCheck{ValidContext?}
ValidCheck -->|Yes| Retrieve
ValidCheck -->|No| NoOp([No retrieval performed])
Result --> WriteCall{Caller invokes Write?}
WriteCall -->|Yes| TxStart[OnTransactionStart]
TxStart --> OnWrite[Subclass OnWrite]
OnWrite --> TxStop[OnTransactionStop:<br>commit or rollback]
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 |
|---|---|---|---|---|
| Application context initialization | Initialize a manager and prepare its data layer† | AppManagerBase |
SAIF.Application |
Initialize claim data portal |
| Security role assignment | Set a single effective application access role† | AppManagerBase |
SAIF.Application |
Set claim context, Set worker context |
| Context validity check | Confirm the manager is in a usable context† | AppManagerBase |
SAIF.Application |
Retrieve claim application data |
| Multi-database portal registration | Register keyed Oracle portal information† | ApplicationDataAccess |
SAIF.Application |
Initialize claim data portal |
Origin: These operations are defined in
SAIF.Application/AppManagerBaseand inherited or delegated by this component.SAIF.Applicationis documented in the previous format, so no per-operation page exists for these; their step-by-step logic is embedded inline (with> Origincallouts) in the consuming operation's detail page, referencing Operations and processes in theSAIF.Applicationdocumentation set.
From clsClaimData (SAIF.Business.View.Claim)¶
| Operation | Intent | Provided by | Origin | Embedded in |
|---|---|---|---|---|
| Retrieve claim summary data | Load claim-level summary data by claim ID or claim number† | clsClaimData |
SAIF.Business.View.Claim |
Set claim context, Set worker context |
Origin: This operation is defined in
SAIF.Business.View.Claim/clsClaimDataand inherited or delegated by this component. That library is documented in the previous format, so no per-operation page exists; see Operations and processes in theSAIF.Business.View.Claimdocumentation set.
From ClaimServices (SAIF.Business)¶
| Operation | Intent | Provided by | Origin | Embedded in |
|---|---|---|---|---|
| Claim authorization and visibility checks (security-override lookup) | Resolve whether a user has an active security override for a claim† | ClaimServices |
SAIF.Business |
Set claim context, Set worker context |
Origin: This operation is defined in
SAIF.Business/ClaimServicesand inherited or delegated by this component. That library is documented in the previous format, so no per-operation page exists; see Operations and processes in theSAIF.Businessdocumentation set.
From clsClaimTaskGenerator (SAIF.Business.Tasks.Claim)¶
| Operation | Intent | Provided by | Origin | Embedded in |
|---|---|---|---|---|
| Generate batch claim tasks | Create claim-task work items for a single claim or across multiple claims† | clsClaimTaskGenerator |
SAIF.Business.Tasks.Claim |
Generate claim tasks |
| Save entity lifecycle (inherited) | Persist a business entity and accumulate validation errors† | clsClaimTaskGenerator (via clsBusinessBase) |
SAIF.Business.Tasks.Claim |
Generate claim tasks |
Origin: These operations are defined in
SAIF.Business.Tasks.Claim/clsClaimTaskGeneratorand inherited or delegated by this component. That library is documented in the previous format, so no per-operation page exists; see Operations and processes in theSAIF.Business.Tasks.Claimdocumentation set.
Failure and edge-case behavior¶
- Blank claim numbers and non-positive claim IDs leave the manager out of context and set the
PLEASEENTERCLAIMmessage; a non-positive worker ID is silently ignored with no message at all (BR-006). - Missing or invalid claim data leaves the application out of context with the
CLAIMNOTFOUNDmessage. - Conflict-claim access failures without a security override mark the application
NoAccessand return the confidential-access message (BR-001). Retrieve()never explicitly assigns its return value, so it always yieldsFalseto callers regardless of whether retrieval executed or succeeded — see Retrieve claim application data.- Data-portal creation failures throw
ApplicationExceptionafter the manager is marked out of context and denied access — see Initialize claim data portal. - A worker-only context resolves claim data through a blank claim-number lookup in the base implementation, because
GetClaimData()never readsContext.WorkerID— see Set worker context.**
Related documentation¶
- Index
- Overview
- Architecture
- Dependencies
- Business rules
- Security and authorization
- Configuration
- API reference
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. Statements marked with†are derived from dependency library documentation and describe inherited or delegated behavior from the indicated origin library; they should be verified if the dependency version changes.
Sources¶
Application\SAIF.Application.Claim\ClaimAppManager.vbApplication\SAIF.Application.Claim\ClaimSecurity.vbApplication\SAIF.Application.Claim\ClaimContext.vbApplication\SAIF.Application.Claim\ClaimUserAccess.vbApplication\SAIF.Application.Claim\ClaimAppConstants.vbBusiness\SAIF.Business\ClaimServices.vb