Salesforce process maps — index

Business Process Maps

Generated 2026-04-22T07:01:31.951Z via PWG Salesforce MCP. Aggregates 271 active Flows + 111 Apex triggers into per-SObject automation maps, plus heuristic cross-Flow chain detection.

How to read a per-object map:

• Orange node = SObject
• Blue = Flow triggered by this object
• Grey = Flow triggered elsewhere that mutates this object
• Green = Apex trigger
• Yellow = Task created
• Purple = Subflow invoked

Objects by automation footprint

Object	Record-triggered Flows	External Flows	Apex Triggers	Total	Doc
Task	7	40	3	50	Task.md
Opportunity	17	19	3	39	Opportunity.md
Employee_Availability__c	0	27	0	27	Employee_Availability__c.md
Account	12	8	3	23	Account.md
Lead	11	0	3	14	Lead.md
Case	5	5	1	11	Case.md
acl__Investment__c	2	8	1	11	acl__Investment__c.md
AccountContactRelation	3	5	3	11	AccountContactRelation.md
Event	6	1	2	9	Event.md
FinServ__FinancialAccount__c	2	2	3	7	FinServ__FinancialAccount__c.md
FinServ__Revenue__c	5	0	2	7	FinServ__Revenue__c.md
Contact	2	1	3	6	Contact.md
Business_Process__c	3	3	0	6	Business_Process__c.md
acl__Transaction2__c	1	2	2	5	acl__Transaction2__c.md
Fact_Find_Submission__c	2	2	0	4	Fact_Find_Submission__c.md
OpportunityLineItem	3	0	1	4	OpportunityLineItem.md
FinServ__FinancialGoal__c	1	1	2	4	FinServ__FinancialGoal__c.md
User	1	0	2	3	User.md
Invoice__c	3	0	0	3	Invoice__c.md
asp04__Payment__c	2	0	1	3	asp04__Payment__c.md
acl__Fund__c	1	0	1	2	acl__Fund__c.md
FinServ__FinancialAccountTransaction__c	2	0	0	2	FinServ__FinancialAccountTransaction__c.md
Campaign	0	1	0	1	Campaign.md

Cross-flow chains

6 detected chain(s) where one Flow creates a Task whose subject is matched by another Flow’s trigger condition.

Method notes

• Trigger info extracted from Flow.Metadata.start. Filters only appear where a record-triggered Flow has a filter (not all do).
• “Task created” means a recordCreate element with object='Task'; the Subject is captured only when it’s a static string literal in the inputAssignments.
• Dynamic subjects (formula-built from fields) show as (dynamic subject) — can’t be matched for chain detection.
• Apex-to-Flow and Flow-to-Apex chains aren’t detected here — add a second pass if those become interesting.
• Process Builder Flows (ProcessType=Workflow) are included but with simplified metadata; treat with care.