Skip to content

Sync WCD number to Guidewire

This operation updates the WCD (Workers' Compensation Division) number on a Guidewire claim when a hearing-request case is saved with a new WCD number.

Field Value
Operation ID OP-LGL-007
Trigger Case save, when m_WCDNum was supplied — called from clsRequestManager.OnWrite
Inputs WCD number, WCD user
Outputs Guidewire claim WCD-number update (external system)
Primary components clsRequestManager.UpdateWcdData
Entry point SAIF.Application.Claim.Legal\LegalNet\clsRequestManager.vb

Steps

  1. On case save, check whether m_WCDNum was supplied.
  2. If not supplied: skip this operation entirely.
  3. If supplied: build a WcdRequest (wcdNumber, wcdUser).
  4. Call the GWClaimDataApi client via an Update route to claims/{claimID}/wcdNumber.
  5. On failure: catch and log the exception via Logging.clsLogError.CreateError without failing the save (BR-LGL-008).

Process flow

The following diagram visualizes this operation's control flow.

flowchart TD
    Start([Case save: OnWrite]) --> Supplied{m_WCDNum supplied?}
    Supplied -->|No| Skip([Skip sync])
    Supplied -->|Yes| Build[Build WcdRequest]
    Build --> Call[GWClaimDataApi Update route<br>claims/claimID/wcdNumber]
    Call --> Ok{Succeeded?}
    Ok -->|Yes| EndOk([Done])
    Ok -->|No| LogErr[Log error<br>no failure surfaced] --> EndOk

Failure and edge-case behavior

  • m_WCDNum not supplied: the sync step is skipped without error.
  • Guidewire update failure: logged via Logging.clsLogError.CreateError and never fails the underlying case save (BR-LGL-008) — reuses the same best-effort pattern as Sync hearing schedule to Guidewire.

Sources

  • SAIF.Application.Claim.Legal\LegalNet\clsRequestManager.vb
  • SAIF.Application.Claim.Legal\LegalNet\WcdRequest.vb