RaiseNow Fundraising Kit Managed Package Release 1.11 (June 2020)
Added support for changing the recurring donation amount from within Salesforce
If you update the amount on an NPSP recurring donation object, the change will automatically be propagated to RaiseNow.
Retrieve amount for charging a saved payment method from Opportunity
If you charge a saved payment method for an opportunity in Salesforce, the default amount for the charge will now automatically be set to the amount of the opportunity.
Fix a bug in the P2P campaign creation
A bug for the P2P integration could lead to campaigns not properly being set up in Salesforce. No production instances were impacted by this bug.
RaiseNow Fundraising Kit Managed Package Release 1.10 (May 2020)
Significantly reduce the number of required API calls
Certain checks to verify the existence of custom fields or configurations within Salesforce are now cached. Hence we no longer need to check this for each donation which in turn reduces the number of API calls, especially when dealing with large transaction volumes. We have also increased the usage of composite API requests to Salesforce.
Set Scheduled date for NPSP Payments
We now set the scheduled date when creating NPSP Payments. The Scheduled date will always be set to the current date.
Readable labels for payment methods
Instead of identifiers we now use readable labels for the payment methods set by RaiseNow.
One-off direct debit pledges no longer create an NPSP Payment
If we receive an order for a direct debit payment we no longer create NPSP payment objects.
RaiseNow Fundraising Kit Managed Package Release 1.9 (May 2020)
Improved support for saved payment methods (payment sources)
If the primary contact for a given opportunity has an associated stored payment method, a new button in the RaiseNow Opportunity layout allows you to directly create a payment for that opportunity. If the payment is successful the Opportunity will be updated accordingly.
Improved support for direct debit payment method and direct debit mandates
If a RaiseNow transaction or subscription is created with the payment method direct debit (payment method identifier "dd") the corresponding RaiseNow Transaction or Subscription object will link to a RaiseNow Bank Account object.
If the transaction has been created using the RaiseNow mandate template feature, the transaction will contain the parameters "pdflink" pointing to a PDF document url and form_template. In this case a direct debit mandate object will be created and the PDF will be uploaded and attached to that object. The mandate object will link to the corresponding RaiseNow Transaction or Subscription object in Salesforce.
For donations from the Formunauts DonutApp the transaction parameter stored_dd_document_reference will point to a signed PDF document. This will also be automatically uploaded and attached to the created mandate object. The onboarding wizard has been extended with a new "Document Download" service for this purpose. It will require you to add the DonutApp client_id and secret.
Support for passing a Salesforce Opportunity Id as a query string to the donation widget
If you add a Salesforce Opportunity object ID as a query string to the URL when loading the widget, a resulting donation will directly update that Opportunity. For example:
You can leverage this feature for example when using tools like Marketing Cloud or other Email marketing applications to send individual links to donors with Opportunities already prepared.
Support for passing fundraisers as a transaction parameter
If the transaction contains a parameter
corresponding to a Salesforce ContactId a relationship record between the Donor and the Fundraiser with the role "solicitor" will be created. The value must be a valid ContactId
Support for passing fundraising teams as a transaction parameter
If the transaction contains a parameter
corresponding to the Id of a Fundraising Team object record in the RaiseNow Fundraising Kit managed package for Salesforce the resulting RaiseNow Transaction or Subscription object will have a link to that team. The value must be a valid object Id.
Support for passing a marketing location identifier as a transaction parameter
If the transaction contains a parameter
the resulting RaiseNow Subscription or Transaction object will have the corresponding field value. Only the datatype "string" is supported for this field.
RaiseNow Fundraising Kit Managed Package Release 1.5 (March 2020)
Generating direct marketing campaign data in Salesforce
With just a few clicks, select your campaign members and generate payment references for direct marketing campaigns. These payment references are unique for each campaign member and can be used to automatically match offline payments later on. A .csv export for use with the letter shop will be available directly on your campaign object.
Generating unique payment reference for online pledges
In the online donation process, RaiseNow supports generation of unique payment references for one-off and recurring donation pledges starting with this release.
Processing and matching information from camt.054 files
RaiseNow supports retrieval and processing of camt.054 files from banks. This release adds support for the following business processes for Salesforce NPSP:
- Matching payment references from direct marketing campaigns, identifying the contact and the campaign, and creating opportunities and payments accordingly.
- Creating new contacts, opportunities, and payments based on transaction data retrieved from the bank.
- Matching transactions to existing one-off and/or recurring pledges based on previously created payment references.
- Detecting and matching multiple usages of the same payment reference.
Trigger Actions at RaiseNow from within Salesforce
This release lays the foundations to trigger particular actions in RaiseNow from within Salesforce. The first two provided with this release are:
- refunding transactions from within Salesforce
- canceling of subscriptions from within Salesforce
Facilitate the on-boarding process
Refund or cancel payments from within Salesforce
The newly introduced RaiseNow transaction object allows you to cancel a transaction within 24 hours. After 24 hours the payment is automatically refunded instead.
Cancel recurring donations from within Salesforce
By setting the "Open Ended Status" on a recurring donation object to "Closed" or by clicking the cancel subscription button on the RaiseNow subscription object, the corresponding RaiseNow subscription will be automatically canceled.
Donor tax receipt preferences
If a donor requests a tax receipt during the donation process the created opportunity will now have a corresponding flag.
RaiseNow Fundraising Kit 1.0
A new configuration interface allows you to switch the targeted Salesforce instance if you are not yet running in production or still targeting a Salesforce Sandbox instance. This will be particularly useful for our SI partners but also allows customers to make the switch from testing to production in their own time. Please note that the interface uses the RaiseNow manager for authentication. So you need an active RaiseNow merchant to make use of this feature.
Real-time data transfer
One-off and recurring donations are now transferred to Salesforce in real-time, once the payment has received the 'final success' status in RaiseNow which indicates that the payment has been completed successfully. This is of particular importance if you are relying on Salesforce to take over your follow up communication instead of using the built-in confirmation emails from RaiseNow. But our SI partners will also appreciate it during product demos.
Support for the RaiseNow Peer-To-Peer platform
If you have licensed the RaiseNow Peer-To-Peer platform this can now be connected to Salesforce. Campaigns created in the Peer-To-Peer Platform can now be linked to Salesforce campaigns using the merchant administration interface. Fundraising pages created for such a campaign will automatically be set up as child campaigns within Salesforce. Donations collected on the fundraising pages will be linked to the respective child campaigns within Salesforce. Fundraisers will be added to both the parent campaign and the child campaign as campaign members with the status "Fundraiser" while donors will receive the status "Donor". Please check out our documentation for more details.
As a default, RaiseNow will perform a simple query on the Salesforce API searching for an exact match of first name, last name, and email. However, we do also support using the Salesforce deduplication logic, utilizing Salesforce duplicate and matching rules. At the moment this requires us to deploy a piece of custom code within your Org. We will soon resolve this through supplying our own managed package. Until then, please contact email@example.com
Support for refund transactions
If you trigger a refund transaction in RaiseNow, this will now be reflected on the opportunity created for the original donation by updating the opportunity StageName and adding a second negative transaction.
Support for Salesforce country picklists
We now pass the country ISO code instead of the country name to Salesforce when processing donations. This is a breaking change as it requires country picklists to be activated within your Salesforce instance. Our onboarding documentation has been updated accordingly. Please also check out this Salesforce documentation on how to activate country picklists.
Support for payment slip donations
One-off donations with payment slips will now result in the creation of an opportunity within Salesforce as well as a payment. In contrast to electronic payment methods, the opportunity will retain the status "Pledged" and the payment will not be marked as "Paid" within Salesforce.
Support for payment slip pseudo-recurring payments
If you have activated the payment slip option for recurring payments in a RaiseNow widget this will now trigger the creation of a recurring payment object within Salesforce. In contrast to RaiseNow subscriptions, RaiseNow will not execute any charge for such a pledge. Hence, opportunities will not be updated by RaiseNow, retaining the status "Pledged" and the initial payment will not be marked as paid within Salesforce.