Skip to content

Manage a legal case request

This workflow captures a legal case request, creates or loads the underlying legal case, persists request issues and consolidations, and optionally triggers letter production and Guidewire WCD updates.

Field Value
Operation ID OP-APP-002
Trigger User submits frmRequest
Libraries involved SAIF.Application.Claim.Legal, SAIF.Business.Claim.Legal, SAIF.Business.View.Policy, SAIF.Services.Appworx
Screens frmRequest
Inputs Request fields, requested issues, consolidation selections
Outputs Persisted clsLegalCase, clsRequestIssue, clsConsolidations; optional LegalNet letter batch job; optional Guidewire WCD update

Steps

  1. clsRequestManager handles frmRequest, binds request fields, and assembles request issues and consolidation selections — owned by SAIF.Application.Claim.Legal.
  2. LegalManagerBase.CreateCase and SetCurrentCase create a new case or load an existing one — owned by SAIF.Application.Claim.Legal.
  3. SAIF.Business.Claim.Legal persists clsLegalCase, clsRequestIssue, clsConsolidations, and related case fields (REQUEST_ISSUE, CONSOLIDATED_CASE).
  4. SAIF.Application.Claim.Legal inserts recon-request letter work when required and updates cross-case state.
  5. Policy and policyholder context for the request is resolved through SAIF.Business.View.Policy, applying the secure-policy and demo-masking rule (BR-APP-007) before displaying policyholder details.
  6. SAIF.Services.Appworx submits the LegalNet letter batch job when correspondence must be produced.
  7. External Guidewire integration is invoked from SAIF.Application.Claim.Legal through the configured claim-data APIs when WCD updates are required.
  8. On failure: the Guidewire call failure is logged but does not fail the underlying case save (BR-APP-006).

Process flow

The following diagram visualizes this workflow across components.

flowchart TD
    Start([User submits frmRequest]) --> S1[clsRequestManager binds request fields and issues]
    S1 --> S2[LegalManagerBase creates or loads case]
    S2 --> S3[SAIF.Business.Claim.Legal persists case, issues, consolidations]
    S3 --> S4[Policy context resolved with secure/masking checks]
    S4 --> D{Correspondence required?}
    D -->|Yes| S5[Appworx submits LegalNet letter job]
    D -->|No| S6{WCD update required?}
    S5 --> S6
    S6 -->|Yes| S7[Guidewire WCD update attempted]
    S6 -->|No| EndOk([Request saved])
    S7 --> EndOk

Failure and edge-case behavior

  • Guidewire WCD update failure: logged and swallowed; the request save still completes (BR-APP-006).
  • Secure or demo policy: policyholder details are masked or access-denied per the policy access rule before being surfaced on the request screen (BR-APP-007).

Sources

  • SAIF.Application.Claim.Legal/LegalNet/clsRequestManager.vb
  • SAIF.Application.Claim.Legal/LegalManagerBase.vb
  • SAIF.Business.View.Policy/clsPolicySecurity.vb