Skip to content

Flow Name: OrderSummary before create

Last Updated: 2025-10-15 Source Code: OrderSummary_before_create.flow-meta.xml

API Name: OrderSummary_before_create Status: Active Type: Modified Standard Trigger: Before OrderSummary is created

Business Purpose

Ensures OrderSummary records have a valid OrderedDate by copying the ActivatedDate from the OriginalOrder when OrderedDate is null, maintaining data completeness for order processing and reporting.

Process Flow

  1. Triggers before OrderSummary record creation
  2. Checks if OrderedDate field is null
  3. If null, copies OriginalOrder.ActivatedDate to OrderedDate
  4. Updates the record before save
📊 Click to view Process Flow Diagram 
flowchart TD
    Start([Start: OrderSummary Create<br/>Before Save<br/>OrderedDate is Null]) --> Update[Update OrderSummary:<br/>OrderedDate =<br/>OriginalOrder.ActivatedDate]

    Update --> End([End])

    style Start fill:#e1f5ff
    style Update fill:#ffe1e1
    style End fill:#e1f5ff

Key Business Rules

  • Only executes when OrderedDate is null
  • Uses OriginalOrder relationship to get ActivatedDate
  • Operates in Before Save context for efficiency
  • No validation that OriginalOrder.ActivatedDate exists

Dependencies

  • Objects: OrderSummary (standard), Order (standard)
  • Fields: OrderedDate, OriginalOrder.ActivatedDate
  • Relationships: OrderSummary to Order (OriginalOrder lookup)
  • Commerce Context: Part of Salesforce Order Management system

Changes

No Pull Request references found in metadata.

⚠️ Pre-Go-Live Concerns

CRITICAL - Fix Before Go-Live

  • Missing Null Check: Doesn't verify OriginalOrder.ActivatedDate exists before copying - could fail
  • No Error Handling: No fault path configured for lookup failures

HIGH - Address Soon After Go-Live

  • Silent Failures: If OriginalOrder.ActivatedDate is null, OrderedDate remains null with no warning
  • Data Quality: No validation that ActivatedDate is a reasonable value (not future, not too far in past)

MEDIUM - Future Enhancement

  • Default Date: Consider using current date/time if OriginalOrder.ActivatedDate is also null
  • Audit Trail: Log when OrderedDate is auto-populated for troubleshooting

LOW - Monitor

  • Edge Cases: Monitor for OrderSummaries with null OrderedDate despite this flow
  • Performance: Before-save trigger should be fast, but monitor in bulk scenarios

Maintenance Notes

Complexity: Very Low - Single field copy operation Review Schedule: Annual review sufficient unless Order Management processes change Commerce Dependency: Part of Salesforce Order Management - changes must align with commerce architecture Standard Object Customization: Modifying standard Order Management objects - test thoroughly with commerce processes