Skip to content

LegalManagerBase consolidated-case propagation

Propagate primary-case changes to consolidated secondary cases.

Field Value
Operation ID propagate-consolidated-case-changes
Trigger Primary-case file location, LCE state, case status, or DEF flags change.
Inputs Current manager state, current claim/case context, and workflow-specific parameters or collections.
Outputs Updated collections, messages, or side effects specific to the operation.
Primary components LegalManagerBase consolidated-case propagation
Entry point SAIF.Application.Claim.Legal\LegalManagerBase.vb

Steps

  1. Identify consolidated secondary cases attached to the current primary case.
  2. For file-location changes, create matching secondary-case file-location rows and save them.
  3. For LCE changes, load each secondary case, align evaluation state with the current hearing assignment, and save the case.
  4. For case-status and DEF-flag changes, copy the updated values to each secondary case and save.

Process flow

The following diagram visualizes this operation's control flow.

flowchart TD
  Start([Trigger]) --> S1[Load current state]
  S1 --> S2[Apply workflow rules]
  S2 --> D{"Validation or security<br>issue?"}
  D -->|Yes| EndErr(["Return message or block<br>action"])
  D -->|No| EndOk(["Return updated workflow<br>state"])

Failure and edge-case behavior

  • Secondary-case propagation runs only for consolidations marked as secondary.
  • Individual secondary-case saves can still fail if downstream business objects reject the update.

Sources

  • SAIF.Application.Claim.Legal\LegalManagerBase.vb