Single-step pipeline mode
Single-step pipeline mode is an alternative processing approach where MoveData handles all business logic within a single Lightning Flow or Apex handler, bypassing the standard multi-stage pipeline.
Advanced configuration for rare use cases
The vast majority of MoveData implementations should use the default multi-step pipeline. Single-step mode removes the structured stage-by-stage processing that handles record relationships, duplicate management, and complex fundraising scenarios. Only use this mode if you have a specific requirement that the multi-step pipeline cannot meet.
When to use single-step mode#
Single-step mode is appropriate in a small number of scenarios:
- Salesforce staging object imports — your organisation has invested heavily in importing data from a Salesforce staging object and you want MoveData to write directly to that object rather than processing through the full pipeline.
- Simple integration requirements — the data being processed is straightforward and does not require the relationship management, duplicate detection, or campaign attribution that the multi-step pipeline provides.
- Performance-optimised Apex processing — you have built a custom Apex handler that processes the entire notification in a single transaction for performance reasons.
- Legacy system compatibility — you need to maintain compatibility with an existing system that expects data in a specific format or location.
When not to use single-step mode#
Do not use single-step mode if your implementation requires any of the following:
- Automatic duplicate detection and matching across contacts, accounts, or donations
- Hierarchical campaign processing (peer-to-peer fundraising structures)
- Recurring donation management
- Matched gift or tribute donation relationships
- The field mapping, post-processing, and platform key phases provided by each multi-step stage
If you are unsure which mode to use, use the default multi-step pipeline. It covers the requirements of virtually all MoveData implementations.
How to enable single-step mode#
To switch from the default multi-step pipeline to single-step mode, create a custom metadata record that directs the pipeline to use the single-step handler.
Step 1: Open custom metadata in Salesforce Setup#
- Navigate to Setup > Custom Metadata Types.
- Find the MoveData Schema Map (
movedata__Movedata_Schema_Map__mdt) custom metadata type. - Click Manage Records.
Step 2: Create the metadata entry#
- Click New.
-
Enter the following values:
Field Value Label EXTENSION_DONATION_MODEHandler single_stepType Config -
Click Save.
Once saved, the donation pipeline will bypass all multi-step stages and route processing to the single-step stage instead.
How it works#
In the default multi-step mode, the donation pipeline processes each notification through six sequential stages: configuration, pre-processing, accounts, contacts, campaigns, recurring donations, and donations. Each stage handles a specific aspect of the data and manages relationships between records.
In single-step mode, the pipeline skips all of these stages.
Instead, it executes a single Lightning Flow identified by the configuration key PIPELINE_DONATION_SINGLE_STEP.
Your single-step flow receives the full notification payload and is responsible for all processing logic, including:
- Reading and interpreting the notification data
- Creating or updating any Salesforce records
- Managing relationships between records
- Handling errors and validation
You must provide the processing flow
Single-step mode does not include any out-of-the-box processing logic. You must create a Lightning Flow (or Apex handler invoked from a flow) that handles the entire notification.
Configuration reference#
| Metadata key | Value | Purpose |
|---|---|---|
EXTENSION_DONATION_MODE |
single_step |
Switches the donation pipeline from multi-step to single-step mode |
PIPELINE_DONATION_SINGLE_STEP |
Your flow API name | Identifies the Lightning Flow that processes the notification |