v1.36 – RaiseNow Digital Fundraising Kit with NPC & NPSP Integration Backend Upgrade V1.18

When RaiseNow tries to create a new contact in Salesforce, Salesforce may report one or multiple existing records that match the provided details. RaiseNow will select the best match as reported by Salesforce. Details provided by the donor with their donation will be updated in Salesforce automatically on that contact. 

As an organisation may have certain business rules in place that prohibit an update auf certain fields, you can define "protected" fields. RaiseNow will automatically omit updates on those fields. When RaiseNow omits a field update, a platform event in Salesforce will be triggered. This platform event is intended to facilitate implementation of your own semi-automated review and update process on such object fields. 

Example:

  "RaiseNow__Object_Duplicate_Detected__e": {
    "RaiseNow__Matched_Record_Identifier__c": "0037Q00000eLLt7QAG",
    "RaiseNow__Matched_Record_Entity_Type__c": "Contact",
    "RaiseNow__RaiseNow_Record_Identifier__c": "fd2dd3c5-f4ac-4c3b-b82b-26776167d2f9",
    "RaiseNow__Report_Message__c": "These fields were not updated as they have been configured as protected.",
    "RaiseNow__Ignored_Fields__c": "{\"external_identifer__c\":\"43212new123ab\"}"
  }

RaiseNow will also never update a boolean field (checkbox) in Salesforce from true (checked) to false (unchecked). To illustrate the reasoning behind this, consider the following use case. Not checking a newsletter optin on a donation page is not the same as providing an explicit opt-out. 

We advise that you study this change carefully with regards to implications this may have for your organisation. 

Example:

"RaiseNow__Card_Expiration_Notice__e": {
  "RaiseNow__Expiration_Month__c": "05",
  "RaiseNow__Expiration_Year__c": "23",
  "RaiseNow__Masked_Card_Number__c": "424xxxxxxxx42",
  "RaiseNow__Subscription_Identifier__c": "876948e6c44befd482282dd495df2011bbc5dc6a"
}

 

Improved dunning mechanics for retrying failed payments

We have extended support for existing methods to execute recharges for opportunities programmatically. Previously it was only possible to recharge opportunities if they belonged to direct debit subscription collected via our new Hub platform. 

Example:

List<List<Id>> opps = new List<List<Id>>(); 
opps.add(new List<Id>{'0067Q00000I2UcWQAV','0061i00000b5b4XAAQ'});

for (List<Id> entry : opps) { 
RaiseNow.ProcessBuilderOpportunityChargeHandler.requestOpportunityCharge(entry); 
}

Note that you list must not exceed 2000 entries. If you need to process lists with more than 2000 opportunities you have to call this method in batches.   

Saving payment methods using the RaiseNow forms

RaiseNow tokenizes payment methods for recurring payments. Given the donor provides an opt-in in the donation process, RaiseNow can also tokenize card payments for one-off donations. The donation form will feature an additional checkbox in the payment method step:

Given the donor has provided such an optin, you can enable a lightnin web component in your page layout in Salesforce. 

Using that button on the opportunity will allow you to charge an opportunity directly in Salesforce. 

Note: Payment processed in this way will be directly attributed to this opportunity. Regardless of opportunity status or contact information. Contact information will not be updated. 

 

Other bugs and improvements 

• Reduce batch size when passing reconciliation information to Salesforce to avoid breaching Salesforce SOQL limits for large reconciliation reports. 
• Improved handling of composite requests to Salesforce to automatically deal with row lock errors. 
• Automatically create opportunity for a recurring donation payment if no open opportunity can be identified. This was done to mitigate a behaviour observed with some legacy recurring donation configurations in Salesforce NPC & NPSP as well as automatically dealing with recurring donation payments when the recurring donation has been closed between payment initiation and reporting of a successful payment. 
• Automatically cancel non-initiated outstanding payments for RaiseNow subscriptions when the corresponding recurring donation is either suspended or lapsed in Salesforce. 

Knowledgebase articles provided with this release:

• Enhanced Duplicate Management with Salesforce Duplicate Detection
• Use Salesforce Flow with Enhanced Duplicate Management