Email History and Merge Contacts Feature
1. What's new
We have added several new features to OnlineFundraising which makes administration much easier. Read along to get an overview of what's new.
1.1 Email History
Communications now features Email History. Users can inspect emails sent via OnlineFundraising and verify that a Communication is running as expected.
Use the Email History to lookup emails to specific recipients and obtain details of the content, connected entities and more. This is especially handy if an end-user is enquiring about email activity from your organisation. Read our support guide to learn more.
We have also added the ability to resend confirmation message on a Subscription.
1.2 Merge Contacts
Users are now able to merge Contacts directly in the UI.
Select Contact data to keep and review the result before merging. Learn about the details of merging Contacts in our support guide.
1.3 Advanced Administration of Transactional Data
We've added several new functions which make it easier to administer transactional data in OnlineFundraising:
- Users can now select active Payment Method for a Subscription if there are multiple Payment Methods. This is possible for all Payment Methods except SMS.
- We have added the ability to edit the Form Result on a DataSet. This is used for error correcting, and editing a DataSet will trigger a webhook.
- It is now possible to edit Purpose Accounting Code on a Payment. This is used for error correcting, and editing a Payment will trigger a webhook.
1.4 Additional Features
- Notifications: We have added notifications to OnlineFundraising. This way, we can easily communicate upcoming changes that may affect your organisation.
- Live filter: Table views now update live when you select a filter - one click saved!
2. Bug Fixes
- Edge case in DIBS Engine callback: We fixed a bug in the DIBS Engine where a successful outcome was reported based on a callback that arrives before the response of a failed HTTP request.
- Check if keyword is availble: Keywords are now trimmed of trailing white spaces before executing keyword availability check.