Overview#

Flow name: MoveData_Donation_Recurring_Post Label: [MoveData] Donation: Recurring - Post Upsert Type: Auto-Launched Flow Template API version: 60.0 Status: Active

This flow handles post-processing operations after recurring donation records are created or updated in Nonprofit Cloud, focusing on Gift Commitment Schedule management, status synchronisation, and gift designation processing.

Purpose#

The flow performs post-upsert operations that:

• Create and manage Gift Commitment Schedules for recurring donations
• Synchronise Gift Commitment status with external platform status
• Process gift designations from campaigns or overrides
• Handle payment method configuration and frequency settings
• Manage outreach source code associations

Salesforce fields#

This flow interacts with the Nonprofit Cloud Gift Commitment object and its related fields. Below is a mapping of all fields utilised:

Input variables#

Core recurring donation data#

Date and schedule configuration#

Frequency and payment settings#

Fee processing#

Marketing and source tracking#

Configuration variables#

Gift designation override#

Flow logic#

1. Status determination and schedule type configuration#

The flow first determines the appropriate Gift Commitment Schedule status and type based on the input status:

Status mapping:

IF Status = "complete" OR "cancelled" THEN
  GCS_Status = "Closed"
  GCS_Type = "CreateTransactions"
ELSE IF Status = "failed" THEN
  GCS_Status = "Lapsed"
  GCS_Type = "CreateTransactions"
ELSE IF Status = "paused" THEN
  GCS_Status = "Paused"
  GCS_Type = "PauseTransactions"
ELSE
  GCS_Status = "Active"
  GCS_Type = "CreateTransactions"

2. Start date resolution#

The flow prioritises start dates in the following order:

1. Donation start date - If Donation_StartDate is provided
2. Modified date - If ModifiedAt is provided
3. Start date - If StartDate is provided
4. Default - Uses current processing date

All dates are converted to local time using the ConvertToLocalDateFlowComponent.

3. Payment schedule configuration#

Day calculation:

Day = DAY(StartDate)
IF Day > 30 THEN Day = "30"

Next payment date processing: If NextPaymentDate is provided:

• Convert to local time
• Extract day of month for scheduling

4. Transaction period and frequency mapping#

Standard frequencies:

• Daily: GCS_TransactionPeriod = "Daily", GCS_TransactionInterval = 1
• Weekly: GCS_TransactionPeriod = "Weekly", GCS_TransactionInterval = 1
• Monthly: GCS_TransactionPeriod = "Monthly", GCS_TransactionInterval = 1
• Quarterly: GCS_TransactionPeriod = "Monthly", GCS_TransactionInterval = 3
• Yearly: GCS_TransactionPeriod = "Yearly", GCS_TransactionInterval = 1

Dynamic frequencies: When FrequencyUnit and FrequencyInterval are provided:

• Map FrequencyInterval to appropriate period (day/week/month/year)
• Set GCS_TransactionInterval to FrequencyUnit value
• Default to "Custom" period if mapping fails

5. Payment method determination#

IF Donation_CardInformationType = "paypal" THEN
  GCS_PaymentMethod = "PayPal"
ELSE
  GCS_PaymentMethod = "Credit Card"

6. Amount calculation with fee processing#

AmountCalculated = IF Config_DonationAmountSubtractFeePlatform = true
  THEN Amount - FeePlatformCalculated
  ELSE Amount

FeePlatformCalculated = COALESCE(FeePlatformPublic, FeePlatform, Donation_FeePlatformPublic, Donation_FeePlatform, 0)

7. Campaign and source code processing#

Campaign association: If Record.CampaignId is populated, set GCS_CampaignId for the schedule.

Outreach source code resolution:

• Skip if Config_MarketingSuppressSource = true
• Use GetOutreachSourceCodeComponent to match Donation_Marketing_Source
• Set GCS_OutreachSourceCode if match found

8. Gift Commitment Schedule management#

Schedule creation:

GiftCommitmentScheduleComponent Parameters:
- Mode: "Create"
- GiftCommitmentId: Record.Id
- All configured schedule parameters

Result processing:

• Track original schedule ID if different from new schedule
• Add both original and new schedule IDs to result list
• Handle success/failure scenarios

9. Gift Commitment status synchronisation#

The flow updates the Gift Commitment record status to match the schedule status:

Status updates:

IF Status = "closed/complete/cancelled" AND Record.Status != "Closed" THEN
  Record.Status = "Closed"
ELSE IF Status = "failed" AND Record.Status != "Lapsed" THEN
  Record.Status = "Lapsed"
ELSE IF Status = "paused" AND Record.Status != "Paused" THEN
  Record.Status = "Paused"
ELSE IF Status = "success/active" AND Record.Status != "Active" THEN
  Record.Status = "Active"

10. Gift designation processing#

Designation source priority:

1. Override: Use Override_GiftDesignationId if provided
2. Campaign: Copy designations from DonationCampaign if available
3. Default: Apply default gift designations

Processing control: Skip gift designation processing if Config_DonationSuppressGiftDesignations = true.

Error handling#

Validation failures#

• Schedule creation failures: Captured in ScheduleErrorMessage and added to Errors collection
• Status update failures: Logged separately with failure context
• Apex component failures: Fault connectors capture and process errors

Continuation logic#

When Config_RecurringCommitmentContinueOnErr = true, the flow continues processing even after encountering errors, collecting all error messages for final reporting.

Dependencies#

• ConvertToLocalDateFlowComponent (Date/time conversion)
• GetOutreachSourceCodeComponent (Source code matching)
• GiftCommitmentScheduleComponent (Schedule management)
• CopyGiftDesignationsComponent (Gift designation processing)
• WriteToLogFlowComponent (Logging operations)

Related articles#

• Recurring Mapping Flow
• Recurring Platform Key Flow
• Recurring Record Match Flow
• NPSP Recurring Post Upsert Flow
• Non-Profit Cloud fields and objects