Contact post-upsert flow
Note
This flow is self-documenting and should be viewed within Salesforce (Setup > Process Automations > Flows). This document is to support working through a visual flow. Please note: the flow commentary is produced using AI.
Overview#
Flow name: MoveData_Commerce_Contact_Post Label: [MoveData] Commerce: Contact - Post Upsert Type: Auto-Launched Flow Template API version: 56.0 Status: Active
This flow handles post-processing operations after contact records are created or updated, focusing specifically on platform key association for commerce transactions. The flow provides a streamlined approach to linking contacts with external platform identifiers.
Purpose#
The flow performs post-upsert operations that:
- Creates platform key associations linking contacts to external platform identifiers
- Provides configurable platform key processing with disable options
- Supports commerce platform integration through external system tracking
- Implements streamlined processing focused on platform key management
Salesforce fields#
This flow interacts with the Salesforce Contact object and its related fields. Below is a mapping of all fields utilised:
| Field API name | Field type | Purpose in flow |
|---|---|---|
| Id | ID | Unique record identifier |
Input variables#
Core contact data#
| Variable | Type | Required | Description |
|---|---|---|---|
Record |
Contact SObject | Yes | The Contact record that was created/updated |
Platform |
String | Yes | External platform identifier |
PlatformKey |
String | Yes | External platform's contact identifier |
Configuration variables#
| Variable | Type | Default | Description |
|---|---|---|---|
Config_ContactDisablePlatformKey |
Boolean | false | Completely disable platform key processing |
Config_MoveDataEngine |
Number | - | Engine version identifier |
Output variables#
| Variable | Type | Description |
|---|---|---|
Record |
Contact SObject | Updated contact record |
Errors |
String Collection | Updated error collection from processing |
Flow logic#
1. Platform key configuration check#
The flow begins by evaluating platform key processing settings:
- Condition: Checks if
Config_ContactDisablePlatformKeyis not true - Purpose: Allows complete bypassing of platform key processing when disabled
- Path Selection: Determines whether to proceed with platform key creation or end processing
2. Platform key creation#
When platform key processing is enabled:
- Subflow Call: Invokes
MoveData_Commerce_Helper_Set_Contact_Platform_Key - Stage Parameter: Sets processing stage to "post" for post-upsert operations
- Input Parameters: Passes contact record, platform details, and configuration settings
- Output Handling: Captures updated contact record and any errors from processing
Processing summary#
- Configuration Check: Evaluate platform key processing settings
- Platform Key Creation: Create platform key association (if enabled)
Configuration options#
Platform key control#
- Complete Disable:
Config_ContactDisablePlatformKey = trueskips all platform key processing - Engine Version:
Config_MoveDataEnginespecifies the processing engine version
Error handling#
Platform key error management#
- Error Collection: Platform key creation failures are captured and returned in
Errorscollection - Subflow Integration: Errors from the helper subflow are properly propagated to the main flow
- Data Integrity: Ensures complete record processing or graceful failure reporting
Error handling#
Common error conditions handled:
- Duplicate Platform Keys: When platform key already exists for different contact
- Invalid Platform Configuration: When platform settings are misconfigured
- Processing Engine Issues: When engine version conflicts occur
Dependencies#
MoveData_Commerce_Helper_Set_Contact_Platform_Key(Subflow)