Flow Name: Relate Orders to Accreditation Application¶

Last Updated: 2025-10-22 Source Code: Relate_Orders_to_Accreditation_Application.flow-meta.xml

API Name: Relate_Orders_to_Accreditation_Application Status: Active Type: Custom Trigger: Manual/Screen Flow (invoked from Accreditation Application record)

Business Purpose¶

Enables manual association of orders with accreditation applications through interactive lookup interface. Provides search functionality to find and link relevant orders, establishing proper relationships for tracking and reporting.

Process Flow¶

1. Displays Order lookup screen using OrderSummary object
2. User searches and selects Order from lookup component
3. Updates selected Order's Accreditation_Application__c field with current application ID
4. Displays success message or error screen based on update result

flowchart TD
    Start([Start: Manual Invocation]) --> Screen[Display Order Lookup]
    Screen --> Select[User Selects Order]
    Select --> Update[Update Order Lookup Field]
    Update --> Success{Update<br/>Successful?}
    Success -->|Yes| SuccessMsg[Display Success Message]
    Success -->|No| ErrorMsg[Display Error Message]
    SuccessMsg --> End([End])
    ErrorMsg --> End

    style Start fill:#e1f5ff
    style Screen fill:#fff4e1
    style Select fill:#e1ffe1
    style Update fill:#ffe1e1
    style Success fill:#fff4e1
    style SuccessMsg fill:#e1ffe1
    style ErrorMsg fill:#ffe1e1
    style End fill:#e1f5ff

Key Business Rules¶

• Single order selection per flow execution
• Required field validation enforces order selection
• Uses OrderSummary for lookup but updates Order object
• SystemModeWithoutSharing allows broader data access
• Can overwrite existing order associations

Dependencies¶

• Order object with Accreditation_Application__c lookup field
• OrderSummary object for lookup interface
• Accreditation_Application__c custom object
• flowruntime:lookup component

Changes¶

No Pull Request references found in metadata.

Pre-Go-Live Concerns¶

CRITICAL - Fix Before Go-Live¶

• None identified

HIGH - Address Soon After Go-Live¶

• Validate OrderSummary to Order ID mapping is correct
• Add business rule validation for appropriate order-application relationships

MEDIUM - Future Enhancement¶

• Consider adding bulk order association capability
• Add validation to prevent duplicate associations
• Display related orders on success screen

LOW - Monitor¶

• Track usage patterns and common use cases
• Monitor for order selection errors

Maintenance Notes¶

Complexity: Low - Simple screen flow with lookup and update Review Schedule: Annual review recommended SystemMode: Runs without sharing - be aware of data access implications Testing: Requires Order and Accreditation Application test data