Skip to content

Manage schedules, file locations, and LCEs

This workflow loads and saves hearing schedules, file locations, and legal case evaluation (LCE) records, propagates state across consolidated cases, and sends qualifying events to Guidewire.

Field Value
Operation ID OP-APP-003
Trigger User saves frmSchedule
Libraries involved SAIF.Application.Claim.Legal, SAIF.Business.Claim.Legal
Screens frmSchedule
Inputs Schedule, file location, and LCE row edits
Outputs Persisted clsLegalSchedule, clsLegalFileLocation, clsLegalCaseEvaluation; propagated consolidated-case state; optional Guidewire activity update

Steps

  1. clsScheduleManager drives frmSchedule and loads schedules, file locations, and LCE rows — owned by SAIF.Application.Claim.Legal.
  2. LCE update flags (LNLCEUpdate, LNDueDateUpdate) determine whether the user may edit LCE and due-date fields.
  3. SAIF.Business.Claim.Legal retrieves and saves clsLegalSchedule, clsLegalFileLocation, and clsLegalCaseEvaluation objects (LEGAL_SCHEDULE, LEGAL_FILE_LOCATION, LEGAL_CASE_EVALUATION).
  4. LegalManagerBase applies screen-level security, delete restrictions, and consolidated-case propagation — owned by SAIF.Application.Claim.Legal (BR-APP-003).
  5. SAIF.Business.Claim.Legal updates the underlying case and schedule state after save, propagating case status, file location, LCE state, and DEF state to linked CONSOLIDATED_CASE rows.
  6. SAIF.Application.Claim.Legal sends qualifying hearing and mediation events to Guidewire through GwMatterApi and GWActivityData.
  7. On failure: the Guidewire call failure is logged but does not fail the schedule save (BR-APP-006).

Process flow

The following diagram visualizes this workflow across components.

flowchart TD
    Start([User saves frmSchedule]) --> S1[clsScheduleManager loads schedules, file locations, LCEs]
    S1 --> S2[SAIF.Business.Claim.Legal persists schedule/file-location/LCE records]
    S2 --> S3[LegalManagerBase applies security and propagation rules]
    S3 --> D{Case is consolidated?}
    D -->|Yes| S4[Propagate status/file-location/LCE/DEF state to linked cases]
    D -->|No| S5[Send qualifying events to Guidewire]
    S4 --> S5
    S5 --> EndOk([Schedule saved])

Failure and edge-case behavior

  • Guidewire hearing/mediation event send failure: logged, does not fail the schedule save (BR-APP-006).
  • Consolidated case propagation failure or partial update is not separately documented in the analyzed source and is treated as unknown.**

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.Legal/LegalNet/clsScheduleManager.vb
  • SAIF.Application.Claim.Legal/LegalManagerBase.vb