Overview#

Class name: NpspInitialiseCampaignMemberProxy Friendly name: NPSP Initialise Campaign Member Statuses Proxy Category: Commerce Extensions Purpose: Provides a proxy interface to create and configure standardised Campaign Member Status records without creating hard dependencies on NPSP extension packages

Class description#

The NpspInitialiseCampaignMemberProxy serves as a decoupling mechanism that enables Campaign Member Status standardisation 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 InitialiseCampaignMemberComponent 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, ensuring campaign operations continue uninterrupted.

Input parameters#

Output parameters#

None

Behaviour#

Proxy pattern implementation#

• Uses reflection to dynamically instantiate the target NPSP component (md_npsp_pack.InitialiseCampaignMemberComponent)
• 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 InitialiseCampaignMemberRequest 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
• Maintains parameter integrity across all status configuration options

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
• Ensures campaign operations continue even when NPSP status standardisation is unavailable

Parameter mapping#

• Comprehensively maps all status configuration parameters including labels and sort orders
• Preserves boolean flags for cleanup operations and error handling preferences
• Maintains parameter defaults through the underlying component when NPSP package is available

Delegation behaviour#

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

• Creates five standardised campaign member statuses in hierarchical order
• Sets appropriate HasResponded values and designates Prospect as default status
• Queries and manages existing campaign member statuses
• Optionally removes non-standard statuses based on configuration
• Handles duplicate sort order conflicts with specific error messaging
• Provides configurable error suppression for batch processing scenarios

Default status hierarchy#

When successfully delegated, the component creates the following standardised hierarchy:

Error handling#

Validation requirements#

• Campaign ID must be provided for status configuration
• When NPSP components are available, comprehensive validation occurs for status configuration conflicts

Graceful degradation#

• Silently skips processing when NPSP package is unavailable rather than throwing exceptions
• Allows campaigns to function with standard Salesforce statuses when NPSP standardisation is not possible
• Supports scenarios where status standardisation may be optional

Dependencies#

Optional dependencies#

• md_npsp_pack.InitialiseCampaignMemberComponent: The target component that performs the actual Campaign Member Status standardisation logic
• Campaign: Standard Salesforce object
• CampaignMemberStatus: Standard Salesforce object for campaign member status configuration

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
• Configuration preservation: Maintains all customisation options for labels and sort orders when underlying components are available
• Error isolation: Prevents NPSP package availability issues from affecting core campaign functionality

Related articles#

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