Create and validate a Coverage B task¶
Creates a Coverage B task, resolves and validates its claim, and applies the Coverage-B-specific due-date window.
| Field | Value |
|---|---|
| Operation ID | OP-13 |
| Trigger | Caller requests a new Coverage B task |
| Inputs | IDataPortalInfo, ClaimID, optional create user |
| Outputs | New, validated clsCoverageBTask |
| Primary components | clsCoverageBTask.NewTask, clsCoverageBTask.Create, clsCoverageBTask.OverrideRules |
| Entry point | SAIF.Business.Tasks.Claim/clsCoverageBTask.vb |
Steps¶
clsCoverageBTask.NewTask(dpi, claimId[, createUser])→CreateObject→Create()setsClaimIDand loads claim data; the constructor has already setTaskDateModifier = NextWorkDayso the base date logic rolls non-working due dates forward (BR-CB-05).- On
ClaimNumassignment,clsClaimData.GetDataresolves the claim andCheckRules("ClaimNum")runs BR-CB-01 (valid claim and coverage codeB). - On failure: fails at LevelOne with "Error: Please enter a valid claim number." or "Error: Claim number is not a Coverage B Claim."
OverrideRulesintercepts base ruleTASK2and re-evaluates the due-date window as today .. today + 1 year (BR-CB-03).PostFillcallsGetClaimData()for every loaded row — Coverage B has no bulk extra-fields procedure.
Process flow¶
flowchart TD
Start([NewTask called]) --> S1["CreateObject: set ClaimID,<br>load claim data"]
S1 --> S2["ClaimNum assignment resolves<br>claim"]
S2 --> S3{"Valid claim and coverage<br>code B?"}
S3 -->|No| Err([Validation failure])
S3 -->|Yes| S4["OverrideRules re-evaluates<br>due-date window"]
S4 --> EndOk([Validated Coverage B task])
Failure and edge-case behavior¶
- Non-Coverage-B claim or invalid claim number fails BR-CB-01.
- Due date outside today..+1 year fails BR-CB-03.
Related documentation¶
Sources¶
- SAIF.Business.Tasks.Claim/clsCoverageBTask.vb