Case.Status — state machine
Case State Machine — Status
Section titled “Case State Machine — Status”Generated 2026-04-22T08:14:24.040Z via PWG Salesforce MCP. Shows the 8 active Status values and which Flows fire when a record is in each stage.
State diagram
Section titled “State diagram”Shows stage-specific Flow hits. A Flow binding of ‘any’ means it’s triggered on every Create/Update with no stage filter — shown in the ‘Any stage’ swimlane below.
Flows per stage (StageName EqualTo)
Section titled “Flows per stage (StageName EqualTo)”| Stage | Flows that fire while in this stage |
|---|---|
New (New) | — |
Not Started (Not Started) | — |
Waiting for Further Information (Waiting for Further Information) | — |
Draft In Progress (Draft In Progress) | — |
Paraplanner Review (Paraplanner Review) | — |
Vetting (Vetting) | — |
Draft Delivered (Draft Delivered) | — |
Completed (Completed) | Paraplanning: Close Tasks Once Completed |
Flows filtered by ‘NotEqualTo’ stage (fire on every stage EXCEPT)
Section titled “Flows filtered by ‘NotEqualTo’ stage (fire on every stage EXCEPT)”None.
Flows with no stage filter (fire on ANY stage change)
Section titled “Flows with no stage filter (fire on ANY stage change)”These flows will execute regardless of which stage the record is in. They’re the most dangerous for run-order and recursion issues.
| Flow | Trigger | Creates Tasks | Updates Objects |
|---|---|---|---|
| Case - Actions on Update After Update Flow | Update | Send Wholesale Advice Doc And Application Form To Client | Opportunity |
| Paraplanning: Assign Work When Case Created | Create | TaskSubjectDocCollection; TaskSubjectDocCreation; TaskSubjectDocReview; Loop_through_vetting_review_tasks.Task_Sub_Type__c; Get_Doc_Creation_Task1.Task_Sub_Type__c; Get_Doc_Creation_Task.Task_Sub_Type__c | AllocationDecision__c |
| Paraplanning: Email If Employee Available Hours Negative For Day | Create | — | — |
| Paraplanning: When reviewer assigned update review task | Update | — | Task |
Stages with ZERO Flow hits (potentially unused)
Section titled “Stages with ZERO Flow hits (potentially unused)”7 active stage value(s) have no Flow filtered to them by EqualTo. Either they’re handled by ‘any-stage’ Flows, by Apex triggers, or they’re dead picklist values.
| Stage | Label | Default? |
|---|---|---|
New | New | ✓ |
Not Started | Not Started | |
Waiting for Further Information | Waiting for Further Information | |
Draft In Progress | Draft In Progress | |
Paraplanner Review | Paraplanner Review | |
Vetting | Vetting | |
Draft Delivered | Draft Delivered |