Skip to content

Flow Name: Flag Account When Number of Individuals Changes

Last Updated: 2025-05-01 Source Code: Flag_Account_When_Number_of_Individuals_Changes.flow-meta.xml

API Name: Flag_Account_When_Number_of_Individuals_Changes Status: Active Type: Custom Trigger: Record Update (Account) - After Save

Business Purpose

This flow monitors changes to the Number_of_Individuals__c field on Account records and sets a flag to indicate when this important business metric has been modified. This flagging system likely supports downstream processes that need to react to individual count changes for pricing, membership, or compliance purposes.

Process Flow

  1. Trigger Activation: Fires when Account records are updated with:
  2. Number_of_Individuals__c field is not null
  3. Number_of_Individuals__c field value has changed
  4. Flag Status Check: Evaluates current Individual_Count_Changed__c flag value:
  5. If Individual_Count_Changed__c = false → Proceed to update flag
  6. If Individual_Count_Changed__c = true → No action (flow exits)
  7. Flag Update: Sets Individual_Count_Changed__c = true on the account
📊 Click to view Process Flow Diagram 
flowchart TD
    Start([Start: Record Update (Account) - After Save]) --> Check{Entry Criteria<br/>Met?}

    Check -->|No| End([End])
    Check -->|Yes| Process[Execute Business Logic]

    Process --> Update[Update Records]
    Update --> End

    style Start fill:#e1f5ff
    style Check fill:#fff4e1
    style Process fill:#e1ffe1
    style Update fill:#ffe1e1
    style End fill:#e1f5ff

Key Business Rules

  • Only triggers when Number_of_Individuals__c has an actual value change
  • Flag is only set to true when currently false (prevents unnecessary updates)
  • Operates after the record is saved to ensure change detection accuracy
  • Field must not be null to trigger the flow

Dependencies

  • Objects: Account (Standard object)
  • Custom Fields:
  • Number_of_Individuals__c (tracks count of individuals)
  • Individual_Count_Changed__c (boolean flag field)
  • Trigger Logic: Uses IsChanged() function for change detection

Changes

No specific pull request references noted in the flow metadata.

⚠️ Pre-Go-Live Concerns

CRITICAL - Fix Before Go-Live

  • No Reset Mechanism: Flow only sets flag to true but provides no way to reset it to false
  • Missing Error Handling: No fault paths for failed record updates

HIGH - Address Soon After Go-Live

  • Flag Management: Need to identify what process resets Individual_Count_Changed__c flag
  • Business Process Gap: Unclear what downstream processes consume this flag
  • Infinite Loop Risk: If this flow triggers other processes that update the account, could cause recursion

MEDIUM - Future Enhancement

  • Audit Trail: Consider logging the old and new values of Number_of_Individuals__c
  • Conditional Logic: May need business rules about when changes should be flagged vs ignored
  • Notification Integration: Flag changes might warrant notifications to relevant stakeholders

LOW - Monitor

  • Performance: Monitor for unnecessary flag updates if multiple processes modify accounts
  • Data Consistency: Verify flag is being properly consumed and reset by downstream processes
  • Edge Cases: Watch for scenarios where Number_of_Individuals__c changes multiple times rapidly

Maintenance Notes

This is a simple flagging mechanism with low complexity, but it's part of a larger business process that needs to be understood. The flag serves as a trigger for other operations, so it's critical that the reset mechanism works properly. Recommend identifying and documenting all processes that consume this flag and ensuring proper flag lifecycle management. Consider implementing monitoring to detect if flags remain true for extended periods, which might indicate broken downstream processes.