Flow Name: [Before Save] Updates on Committee Member Record¶
Last Updated: 2025-07-25 Source Code: Before_Save_Updates_on_Committee_Member_Record.flow-meta.xml
API Name: Before_Save_Updates_on_Committee_Member_Record Status: Active Type: Custom Trigger: Before Committee Member record is created or updated
Business Purpose¶
Automatically maintains data consistency by updating the Committee lookup field on Committee Member records when the Committee Term relationship changes. This ensures members are always associated with the correct committee.
Process Flow¶
- Flow triggers when a Committee Member record is created or updated and the Committee Term field has changed
- Automatically copies the Committee value from the related Committee Term record
- Updates the Committee lookup field directly on the Committee Member record
📊 Click to view Process Flow Diagram
flowchart TD
Start([Start: Committee Member<br/>Create/Update Before Save<br/>Committee_Term__c Changed]) --> Update[Update Committee Lookup:<br/>Committee__c =<br/>Committee_Term__r.Committee__c]
Update --> End([End])
style Start fill:#e1f5ff
style Update fill:#ffe1e1
style End fill:#e1f5ff
Key Business Rules¶
- Only executes when the Committee_Term__c field changes
- Pulls Committee reference from: Committee_Term__r.Committee__c
- Operates in Before Save context for optimal performance
- No validation or error handling beyond standard Salesforce mechanisms
Dependencies¶
- Objects: Committee_member__c, Committee_Term__c (custom objects)
- Fields: Committee_Term__c (lookup), Committee__c (lookup)
- Relationships: Committee Term must have valid Committee relationship
Changes¶
No Pull Request references found in flow description or metadata.
⚠️ Pre-Go-Live Concerns¶
CRITICAL - Fix Before Go-Live¶
- Missing Null Check: Flow does not validate that Committee_Term__r.Committee__c exists before assignment, which could cause failures if Committee Term lacks a Committee
- No Error Handling: No fault path configured - any lookup failures will cause silent errors
HIGH - Address Soon After Go-Live¶
- User Experience: No error message displayed to users when Committee Term has no associated Committee
- Data Quality: No validation that the Committee Term is active or valid for the assignment
MEDIUM - Future Enhancement¶
- Audit Trail: Consider logging when Committee assignments are auto-updated for compliance purposes
- Business Logic: May want to validate that the Committee Member's role is valid for the assigned Committee
LOW - Monitor¶
- Performance: Before-save flows are efficient, but monitor if large bulk operations occur
- Documentation: Flow description could be added to explain the business purpose
Maintenance Notes¶
Complexity: Low - Simple field update with single relationship traversal Review Schedule: Quarterly review recommended if Committee/Term data model changes Dependencies: Tightly coupled to Committee and Committee Term object structure