Skip to content

Attorney-to-claim assignment

This workflow lets legal staff assign an attorney to a claim/worker through the frmAttorneyAssignment screen, resolving claim context and security, persisting the assignment, and triggering claim-task and Exchange calendar side effects.

Field Value
Operation ID OP-APP-002
Trigger User opens frmAttorneyAssignment.aspx and selects a claim/worker context
Libraries involved SAIF.Application.Claim, SAIF.Application.Claim.Legal, SAIF.Business.Claim.Legal, SAIF.Business.Tasks.Claim
Screens Attorney Assignment screen (frmAttorneyAssignment.aspx)
Inputs Claim/worker context, selected attorney
Outputs New ATTORNEY_WORKER_ASSIGNMENT/ATTORNEY_CONFLICT records, a raised claim task, optional Exchange calendar sync

Steps

  1. User opens frmAttorneyAssignment.aspx and selects a claim/worker context.
  2. ClaimAppManager (SAIF.Application.Claim) resolves claim context via ChangeContext() and evaluates ClaimSecurity — see Evaluate claim access (conflict/exposure checks) (BR-APP-002).
  3. The legal manager (SAIF.Application.Claim.Legal) calls clsAssignmentManager.RunAssignmentProcess, which runs SAIF.Business.Claim.Legal's Attorney assignment batch operation to persist the assignment against ATTORNEY_WORKER_ASSIGNMENT/ATTORNEY_CONFLICT tables.
  4. As a side effect, a claim task is raised through SAIF.Business.Tasks.Claim's Bulk-raise claim tasks operation, enriched with claim data via clsClaimData.
  5. SAIF.Business.Claim.Legal's Attorney assignment batch operation optionally syncs the attorney's Exchange calendar, gated by an environment check that determines whether real e-mail/calendar actions occur (BR-APP-004).

Process flow

The following diagram visualizes the attorney-to-claim assignment workflow, including its side effects.

flowchart TD
    Start(["User selects claim/worker<br>context"]) --> S1["ClaimAppManager resolves<br>claim context and<br>ClaimSecurity"]
    S1 --> S2["Legal manager persists<br>ATTORNEY_WORKER_ASSIGNMENT /<br>ATTORNEY_CONFLICT"]
    S2 --> S3["Bulk claim task raised via<br>SAIF.Business.Tasks.Claim"]
    S3 --> S4{Environment is production?}
    S4 -->|Yes| S5[Real Exchange calendar sync]
    S4 -->|No| S6[Test/no-op calendar sync]
    S5 --> EndOk([Assignment complete])
    S6 --> EndOk

Failure and edge-case behavior

  • If the production/non-production environment check is misclassified, non-production environments can perform real-world e-mail/calendar side effects.*

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

Sources