Skip to content

Flow Name: Update Partnership on Create/Update

Last Updated: 2025-04-29 Source Code: Update_Partnership_on_Create_Update.flow-meta.xml

API Name: Update_Partnership_on_Create_Update Status: Active Type: Custom Trigger: After AANP_Representation__c create/update when Role is Member Representative or Staff Liaisons

Business Purpose

Maintains accurate representation counts on Partnership records by triggering recalculation when Member Representative or Staff Liaison relationships are created or updated, ensuring Partnership records reflect current organizational structure.

Process Flow

  1. Triggers after AANP_Representation__c record is created or updated
  2. Filters for Role__c = "Member Representative" OR "Staff Liaisons"
  3. Calls subflow "Count_the_Staff_and_Member_Representation" with parameters:
  4. aanPRepresentationId: Current record ID
  5. partnershipId: Partnership__c from current record
  6. eventAction: "Create/Update"
  7. Subflow performs count calculation and updates Partnership counts
📊 Click to view Process Flow Diagram 
flowchart TD
    Start([Start: AANP Representation<br/>Create/Update After Save]) --> Filter{Role is<br/>Member Representative<br/>OR Staff Liaisons?}

    Filter -->|Yes| Subflow[Call Subflow:<br/>Count_the_Staff_and_Member_Representation<br/>Pass: aanPRepresentationId, partnershipId, eventAction='Create/Update']
    Filter -->|No| End([End])

    Subflow --> End

    style Start fill:#e1f5ff
    style Filter fill:#fff4e1
    style Subflow fill:#f0e1ff
    style End fill:#e1f5ff

Key Business Rules

  • Only processes two role types: "Member Representative" and "Staff Liaisons"
  • Executes after save to ensure data is committed
  • Passes "Create/Update" action to subflow for full recount logic
  • No direct DML - delegates all updates to subflow

Dependencies

  • Objects: AANP_Representation__c, Partnership__c
  • Fields: Role__c, Partnership__c
  • Subflows: Count_the_Staff_and_Member_Representation (core calculation logic)
  • Related Flows: Update_Partnership_on_Delete (handles delete events)

Changes

No Pull Request references found in metadata.

⚠️ Pre-Go-Live Concerns

CRITICAL - Fix Before Go-Live

  • No Error Handling: If subflow fails, error is silent - no notification to user
  • Missing Validation: Doesn't verify Partnership__c is populated before calling subflow

HIGH - Address Soon After Go-Live

  • Performance: After-save triggers can cause delays for users - monitor execution time
  • Bulk Operations: Large bulk loads could trigger many subflow executions

MEDIUM - Future Enhancement

  • Error Logging: Add fault connector to log subflow failures
  • Conditional Execution: Only trigger if counts actually need recalculation

LOW - Monitor

  • Subflow Execution: Monitor Count_the_Staff_and_Member_Representation for failures
  • Data Accuracy: Periodically verify counts match actual representation records

Maintenance Notes

Complexity: Low - Simple trigger orchestration calling subflow Review Schedule: Review when representation or partnership logic changes Subflow Dependency: All business logic is in Count_the_Staff_and_Member_Representation Paired Flow: Works with Update_Partnership_on_Delete for complete lifecycle management After-Save Context: Provides transaction safety but can slow user experience