Skip to content

Appeal brief deadline cascade

When a Brief 1 due date or filed date is set on an appeal, the operation computes and cascades the dependent Brief 2 and Brief 3 due dates, including any granted extension days.

Field Value
Operation ID appeal-brief-deadline-cascade
Trigger Setting Brief1Due/Brief1Filed
Inputs Review level, filed/due dates
Outputs Cascaded Brief 2/3 due dates
Primary components clsAppeal property setters, clsAppealExtension
Entry point SAIF.Business.Claim.Legal\LegalNet\clsAppeal.vb

Steps

  1. Caller sets Brief1Due or Brief1Filed on a clsAppeal instance.
  2. The Brief 2 due date is computed and cascaded from Brief 1's date (BR-AP-005), which in turn cascades to the Brief 3 due date.
  3. If an extension has been granted (via AddExtension()/CreateExtension()), the granted extension days are added to the Brief 2 and Brief 3 due dates (BR-AP-007).

Process flow

flowchart TD
    Start(["Brief1Due /<br>Brief1Filed set"]) --> B2["Compute Brief 2<br>due date"]
    B2 --> B3["Cascade to Brief 3<br>due date"]
    B3 --> Ext{"Extension<br>granted?"}
    Ext -->|Yes| Add["Add extension days<br>to Brief 2 and Brief 3"]
    Ext -->|No| EndOk(["Dates finalized"])
    Add --> EndOk

Failure and edge-case behavior

  • No exceptional behavior beyond standard property-setter validation was identified for this operation.*

Note: Statements marked with * were inferred from code structure, naming conventions, or contextual evidence where direct confirmation was not available in source artifacts.

Sources

  • SAIF.Business.Claim.Legal\LegalNet\clsAppeal.vb