Skip to main content

RaiseNow Fundraising Kit for Salesforce Nonprofit Cloud v1.0.0

Release Date April 16 2024

This update provides the first production release for the Salesforce Nonprofit cloud.

tip

The Nonprofit Cloud integration consists of a managed package and a backend component. Request the installation link for the package from RaiseNow support. The backend component will be provided during the onboarding process.

Support for Salesforce Fundraising Business Process API

RaiseNow leverages the Fundraising Business Process API to create

  • Accounts
  • Gift Commitments
  • Gift Transactions in Salesforce. The Fundraising Business Process API handles Org specific settings such as record type and account deduplication.

Support for one-off payments from RaiseNow Hub

Payments created through the RaiseNow Hub will result in creation of the following objects in Salesforce:

  • (Person/Business) Account
  • Gift Transaction

Support for recurring commitments from RaiseNow Hub

Subscriptions created through the RaiseNow Hub will now result in the creation of the following objects in Salesforce:

  • (Person/Business) Account
  • Gift Commitment
  • Payment Schedule

Support for recurring payments from RaiseNow Hub

Payments created through the RaiseNow Hub that are associated with a RaiseNow subscription will result in a new Gift Transaction for the corresponding Gift Commitment in Salesforce. Successful and failed payments will be transferred.

Support for cancellation of recurring commitments from RaiseNow Hub

If a RaiseNow subscription is cancelled, either from Hub, via API or self-service forms, the corresponding Gift Commitment in Salesforce will be closed.

Support for suspension of recurring commitments from RaiseNow Hub

If a RaiseNow subscription is suspended, either from Hub, via API or self-service forms, the corresponding Gift Commitment in Salesforce will be lapsed.

Support for reactivation of suspended recurring commitments from RaiseNow Hub

If a suspended RaiseNow subscription is activated, either from Hub, via API or self-service forms, the corresponding Gift Commitment in Salesforce will be activated.

Always add last4 to Payment Instrument

Due to a bug in the current implementation of the Fundraising Business Process API, the API expects the parameter last4 to be always set, also if the payment method is not a credit card. If the selected payment method is not a credit card, RaiseNow will pass 4242 as the value.

Add RaiseNow configuration object in Salesforce

A new configuration object stores essential configurations to control how RaiseNow interacts with Salesforce NPC. Configuration values are read when the connection between RaiseNow and Salesforce is initially established. Subsequent updates to the configurations are automatically propagated to RaiseNow once the connection has been established. Configuration options include:

  • outreach-source-code-map: Map the RaiseNow campaign_subid to a valid Salesforce OutReachSourceCode ID.
  • campaign-map: Map the RaiseNow campaign_id to a valid Salesforce Campaign ID
  • address-type: Define the type of address to be set in account objects created in Salesforce. For example: Mailing
  • salutation-map: Map the combination of the RaiseNow a 2-letter ISO language code and the RaiseNow salutation value to the desired salutation value for Salesforce.
  • payment-instrument-map: Map RaiseNow payment methods as set by RaiseNow touch-points to payment instruments in Salesforce. The RaiseNow payment method must be mapped to a valid value for the picklist field in PaymentInstrument.Type in the Salesforce object configuration.
  • default-update-logic: Sets the update logic for the Fundraising Business Process API. See this documentation by Salesforce on valid values.
  • transaction-status-map: Map RaiseNow status codes to valid values for the GiftTransaction.Status picklist field.

Documentation added with this release: