Overview#

Class name: NpspCreateCampaignMemberProxy Friendly name: NPSP Create Campaign Members Proxy Category: Commerce Extensions Purpose: Provides a proxy interface to create and manage Campaign Member records with hierarchical status management without creating hard dependencies on NPSP extension packages

Class description#

The NpspCreateCampaignMemberProxy serves as a decoupling mechanism that enables Campaign Member creation and management functionality while avoiding hard dependencies on the NPSP extensions package. This proxy pattern allows the Commerce extensions to conditionally invoke NPSP functionality when the package is available, ensuring the system remains functional even when NPSP components are not installed.

The class acts as an invocable method wrapper that safely attempts to instantiate and call the underlying CreateCampaignMemberComponentWithLogs through reflection. If the NPSP package is not available or the target class cannot be instantiated, the proxy gracefully handles the failure without throwing exceptions while still returning appropriate response structures.

Input parameters#

Output parameters#

Behaviour#

Proxy pattern implementation#

• Uses reflection to dynamically instantiate the target NPSP component (md_npsp_pack.CreateCampaignMemberComponentWithLogs)
• Converts input parameters to a generic object map for cross-package method invocation using the ToObjectMap() method
• Implements safe instantiation with exception handling to prevent failures when NPSP package is unavailable

Request processing#

• Accepts a list of CreateCampaignMemberRequest objects through the @InvocableMethod
• Transforms each request into a parameter map suitable for the underlying component
• Iterates through all requests in the input list, processing each individually
• Returns a list of response objects maintaining the expected return structure

Error handling#

• Gracefully handles cases where the target NPSP class is not available
• Skips processing during test execution to avoid dependency issues
• Does not throw exceptions when the underlying component cannot be instantiated
• Provides workaround response objects to maintain Flow compatibility

Response management#

• Creates placeholder response objects when NPSP components are unavailable
• Maintains consistent return structure for Flow integration
• Ensures calling flows receive expected response types even when underlying functionality is unavailable

Delegation behaviour#

When the NPSP package is available, the proxy delegates to the underlying component which:

• Uses default hierarchy if none provided: Team Leader, Fundraiser, Recurring Donor, Donor, Prospect
• Prevents status downgrades by comparing current status position against target status
• Allows status upgrades when target status has higher priority than existing status
• Creates new campaign member records when no existing relationship exists
• Performs bulk upsert operations for efficiency across all changes
• Provides comprehensive logging capabilities for processing details

Error handling#

Validation requirements#

• Campaign ID List must be provided (Contact ID is optional for graceful handling)
• Value (target status) must be present
• When NPSP components are available, target value must exist within the provided value hierarchy

Graceful contact handling#

• Silently skips processing when Contact ID is null rather than throwing exceptions
• Allows for conditional campaign member creation based on contact availability
• Supports scenarios where contact association may be optional

Dependencies#

Optional dependencies#

• md_npsp_pack.CreateCampaignMemberComponentWithLogs: The target component that performs the actual Campaign Member creation and management logic
• Contact: Standard Salesforce object
• Campaign: Standard Salesforce object
• CampaignMember: Standard Salesforce object (when NPSP package is installed)
• movedata.MoveDataLogEntry: Logging framework for processing details

Design benefits#

• Loose coupling: Eliminates hard dependencies on NPSP package installation
• Graceful degradation: System continues to function when NPSP components are unavailable
• Package independence: Commerce extensions can be deployed independently of NPSP extensions
• Runtime flexibility: Automatically utilises NPSP functionality when available without requiring configuration changes
• Flow compatibility: Maintains consistent response structures for seamless Flow integration
• Logging support: Preserves comprehensive logging capabilities when underlying components are available

Related articles#

• Create Campaign Members flow component (NPSP source component)
• NPSP GAU Campaign Copy Proxy flow component
• NPSP Initialise Campaign Member Statuses Proxy flow component
• Commerce extension overview