RaiseNow Fundraising Kit Managed Package Release 1.18 (April 2021)
Improved mechanism to transfer failed installment payment to Salesforce
This release introduces support for blocking the transfer of failed one-off donations to Salesforce in order to reduce unnecessary API consumption, while retaining the option to transfer failed installment payments.
Improved data type conversion to match custom field data type automatically
RaiseNow will now automatically identify the data type of a custom field in Salesforce and convert data passed by the touchpoint automatically to these requirements.
Extended camt.054 processing to support multiple banks
We have added an option to specify a bank when uploading a camt.054 file via Salesforce to support processing different camt.054 variants for the same organization.
Support for cover the fee
Late last year RaiseNow introduced the cover-the-fee feature in Tamaro in cooperation with several pilot customers. The feature has significantly improved revenue in our pilot projects. This release adds support within Salesforce to provide visibility on the revenue generated by this feature. Check out our updated documentation here.
Support of custom record types for NPSP objects
You can specify custom record types for NPSP recurring donation objects and NPSP payment objects in addition to the existing functionality regarding opportunities and payments. Check out our updated documentation.
Support for new standard field mappings for Hub
This release introduces support for new standard field mappings for one-off donations and recurring donations created via the new RaiseNow payment gateway:
- phone
- mobile_phone
- birthdate
- language
- email_permission
- administrative_region_level_1
- horific_prefix
Support for new direct debit payment processes
This release introduces support for processing both camt.054 and pain.008 files via the new RaiseNow payment gateway. Check our documentation on the process here for details.
Further Bug Fixes
- Fixed a data conversion problem when a touchpoint passes a string for an integer data type in Salesforce
- Fixed a user interface issue where only the latest saved payment method could be selected for charging an opportunity.
- Fixed naming for an edge case in which payment references were generated with names exceeding the maximum number of allowed characters
- Fixed a bug where the closed date on an opportunity generated from processing a camt file was set to the processing date instead of the actual payment date.
How do I get those updates?
To update your current version two actions are needed:
- A coordinated deployment of our backend component
- Upgrading the managed package to version 1.18 of the RaiseNow Fundraising Kit.
Please contact support to schedule the upgrade.
RaiseNow Fundraising Kit Managed Package Release 1.15 (January 2021)
Support for custom record types in Salesforce
You can now configure a touchpoint to create new contacts and opportunities with custom record types configured in Salesforce. See this article in our knowledge base for details.
Create payment references for individual opportunities
You can now create individual payment references for opportunities with a non-final status. This can be leveraged if you want to send payment instructions to individual donors. RaiseNow will match payments to those opportunities in conjunction with our reconciliation services when processing camt.054 files. See this article in our knowledge base for details.
Account for daylight saving time in time zone conversion
Daylight saving time was not correctly accounted for in the conversion to the Salesforce target Org’s time zone. Transactions created close to midnight could therefore have a wrong date. With this release daylight saving will be correctly converted according to the target Org.
Removed support for HasOptedOutOfEmail
Breaking change: RaiseNow will no longer convert the value from the RaiseNow transaction field stored_customer_email_permission to the field HasOptedOutOfEmail on the contact object. The field from the transaction record is written to RaiseNow__Newsletter_Permission_Given__c on the contact object.
RaiseNow will no longer generate opportunities for direct marketing campaigns
Breaking change: Starting with this release, if you generate payment references for campaign members, opportunities will no longer be created for each payment reference/campaign member. Opportunities will be created if RaiseNow processes a successful payment via our reconciliation services and linked to the contact corresponding to the payment reference.
Improvements to the Business Process Monitor
Though the Business Process Monitor is not directly a part of our Salesforce integration, it is an important quality-of-life element for our customers. The following improvements are provided with this release:
- Catch edgecases in the Business Process Monitor that left processes in an uneditable state.
- Allow to ignore a business process for automatic processing.
- Save search filters while navigating between business processes.
- Improved presentation of error notifications.
How do I get those updates?
To update your current version two actions are needed:
- A coordinated deployment of our backend component
- Upgrading the managed package to version 1.15 of the RaiseNow Fundraising Kit.
For production environments: Please contact support@raisenow.com to coordinate the update with our Customer Success team for updating your production environment.
For test environments: Our backend component for test instances will be upgraded automatically by Wednesday, 3 February. Version 1.15 will be available in the AppExchange starting Tuesday, 2 February. To ensure compatibility you must upgrade your test instances to version 1.15.
RaiseNow Fundraising Kit Managed Package Release 1.13 (November 2020)
Support for enhanced recurring donations across the board
We have added support for all remaining recurring payment methods available through RaiseNow.
Improved Support for Camt file processing
If there is no direct integration set up with your bank to automatically retrieve camt files, you can now use Salesforce to upload a camt file and generate opportunities and payments within Salesforce automatically.
Please contact RaiseNow for activation of the necessary licensing options.
If RaiseNow automatically processes the camt file from the bank, that file will now be uploaded to Salesforce automatically.
Further improvements:
New field mappings in the standard ontology
- You can now populate the field LeadSource on the Contact object by passing stored_customer_lead_source as an EPP transaction parameter. You must ensure valid picklist values according to your Salesforce configuration.
- CurrencyISO code will now be set both on the Payment object as well as on the Contact object when new objects are created as a result of a RaiseNow transaction.
- The field MobilePhone on the Contact object can now be set by passing stored_customer_mobile_phone as an EPP transaction parameter.
Newsletter subscriptions - New RaiseNow field on Contact object
We have introduced a new field on the Contact object to reflect the donors preferences regarding newsletter subscriptions. The RaiseNow EPP field stored_customer_email_permission will now map to RaiseNow_Newsletter_Permission_Given_c.
Improved handling for anonymous payments retrieved from a camt file
If the information retrieved from a Camt file contains null values in mandatory Salesforce fields, RaiseNow will now set the following default values:
- salutation: ”ms”
- first name: “unknown”
- last name: “unknown”
- email address: “unknown@example.com”
Transaction object - Prevent requesting duplicate refunds
We have fixed a bug where transaction refunds could still be requested for transactions that had previously been refunded. The bug was mitigated by the fact that a refund could not actually be executed twice.
The button is now automatically deactivated if the opportunity linked to the transaction has the status “Closed Lost”.
How do I get those updates?
To update your current version two actions are needed:
- A coordinated deployment of our backend component
- Upgrading the managed package to version 1.13 of the RaiseNow Fundraising Kit.
RaiseNow Fundraising Kit Managed Package Release 1.12 (October 2020)
Enhanced Recurring Donations
This release introduces support for the new Salesforce Enhanced Recurring Donations Module for NPSP. It is now possible to collect recurring credit card donations through Stripe and PayU using RaiseNow touchpoints. You can even use Stripe and PayU in parallel, for example if you are fundraising in different countries - all donation data is sent to Salesforce immediately. Support for additional payment service providers and payment methods will follow soon.
New view for monitoring data transfer
This release provides a new monitoring service which we will roll out to customers in a pilot program starting November. You can see at a glance whether all data was transferred smoothly or if you need to take action somewhere. Please contact us through this form if you are interested in participating.
Subscription Management for Enhanced Recurring Donations
These features, already available for the legacy recurring donation module, are now also supported for Enhanced Recurring Donations. We hope they will save fundraisers time on handling daily tasks regarding subscriptions.
Update Recurring Donation Amount in Salesforce
If you update the amount for an enhanced recurring donation in Salesforce, the corresponding subscription in RaiseNow will be updated automatically and future charges will be executed with the specified amount.
Cancel a Recurring Donation in Salesforce
Users can cancel an enhanced recurring donation directly in Salesforce. This change will be automatically propagated to RaiseNow and the corresponding subscription will not be charged in the future.
Improved support for Camt.054 processing
We have improved our reconciliation engine as well as our integration with Salesforce to create contacts, opportunities and payments in Salesforce based on transaction records retrieved from a Camt.054 file. We now support payments with reference numbers to match existing records in Salesforce as well as payments without reference numbers such as a direct online banking transaction.
Upgrading Process
If those improvements sound exciting to you learn here how to update your current version. Two updates are necessary:
- A component update on the side of RaiseNow
- An upgrade for the managed package installed in your organization to version 1.12, available through the AppExchange
Attention: Please contact us prior to updating the package to coordinate deployment of the RaiseNow component.
The RaiseNow component will be backwards compatible until version 1.10 of our managed package.
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:
https://my-domain/widget.html?rnw-stored_crm_opportunity_id=[salesforce_opportunity_uid]
Here is a life example: https://tamaro.raisenow.com/futurogoal-salesforce-preprod/latest/index.html?rnw-stored_crm_opportunity_id=0061i00000CW4YSAA1
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
//EPMS
crm_fundraiser_id
//EPP
stored_crm_fundraiser_id
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
//EPMS
crm_fundraiser_team_id
//EPP
stored_crm_fundraiser_team_id
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
//EPMS
marketing_location_identifier
//EPP
stored_marketing_location_identifier
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.
Deduplication
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 support@raisenow.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.
Comments
0 comments
Please sign in to leave a comment.