Skip to main content

RaiseNow Fundraising Kit for Salesforce NPC v0.5.0 - Backend Upgrades v1.2.0

Release Date October 22 2024

This release focuses on backend and frontend enhancements for our NPC integration. It also includes initial implementations for Direct Debit support within NPC. Request the installation link from RaiseNow support.

Highlights in this release:

Configure touchpoint identifiers for campaign and outreach source code directly in Salesforce on the objects​

We’ve introduced a new feature to simplify campaign and outreach source code map configuration. Instead of manually mapping each campaign or outreach source code within the map configuration, you can now define a key directly on the campaign or outreach source code object. This key will automatically update the map configuration, saving you time and reducing manual steps. This enhancement streamlines the process and ensures your configurations are always up to date.

RaiseNow process selector​

With the addition of a new RaiseNow process for CAMT file uploads, you can now select a specific process directly from a dropdown menu. This feature streamlines the selection, allowing you to focus on a single process and easily choose the desired action. Additional processes will be added to this menu in the future.

Support for source urls longer than 500 characters​

When the RaiseNowNPOKit__ProductSourceUrl__c passed in a donation exceeds 500 characters, we now automatically trim characters that exceed the character limit for this field in Salesforce.

Support chargebacks and reversals​

Charge backs and reversals reported in a CAMT file or by an acquiring partner (reversal.succeeded event in RaiseNow) are now automatically reflected in Salesforce as follows:

  • A Salesforce Event (RaiseNowNPOKit__PaymentReversed__e) is created to notify about the reversal
  • The status of the GiftTransaction is set to what is mapped for reversed in the transaction-status-map
  • A GiftRefund is created (incl. the reason phrase from the CAMT file)

Custom field on account object for supporter salutation​

We added a field to the account object in Salesforce to pass the salutation provided with the donation record on a touchpoint. A RaiseNow field is required in this case, as the Salesforce object model does not provide a standardized field for this purpose. See also SupporterSalutation__c.

New objects​

ReconciliationReport__c​

This RaiseNow object stores information about each reconciliation report containing in particular the value date, the gross & net amount and an unique identifier. Learn more here.

PaymentInitiationMessage__c​

This RaiseNow object stores information about each pain.008 file containing in particular the location of the file and the service to retrieve affected subscriptions. Learn more here

Avoid data clutter by suppressing irrelevant notifications​

We now leverage a new filtering option for event subscriptions when processing data provided from the payment platform. When processing larger numbers of direct debit payments, this should result in a noticeable performance improvements as superfluous operations can be avoided. It also reduces clutter in the business process monitor as production instances of our integration layer will no longer show filtered processes for test payments.

Further improvements​

  • We have added a dialog for uploading CAMT files in preparation for direct debit support in our backend. Stay tuned.
  • We have added functionality to propagate gift commitment and gift commitment schedule updates to RaiseNow. Stay tuned for another backend update to finalize this feature.
  • Adjusting the notification to adapt to new requirements of our reconciliation service.
  • Improve validation of the donation record to be less strict with regards to the data passed by the touchpoint in order to create business processes regardless of data quality.
  • Provide support for uploading PDF attachments generated by a touchpoint to Salesforce