What's new

Nothing pleases our Data Protection Officer more than working with data minimization and automatic cleanup of outdated data, which has been the primary focus of this release.

At OnlineFundraising, we strive to make it as easy as possible for your members and donors to provide their personal information to you as a charitable organization, whether it is via a web form, telemarketing call, street fundraising, SMS campaign, or custom-built integration with OnlineFundraising.

As a data processor, we are committed to ensuring that this is done securely, both in terms of where and how data is stored, and equally importantly, how long data is retained in our primary and secondary subsystems.

So this time, you will have to wait a bit longer for new features.

What's new

In this release, we have compiled various smaller and scattered tasks related to bugs or optimization opportunities across our system landscape. From a long list of items, we will highlight the following.

UPDATED : 2024-06-13

Following this, we have unfortunately discovered that we released a breaking change that affects the accounting of payments via ePay. This change was not intended to be released without further clarification and notification to organizations and integrators. We deeply regret this and are working on a proper handling of the situation. We will review our procedures for such releases to prevent this from happening again.

UPDATED : 2024-07-16

We have decided to roll back the above mentioned change as of August 1, 2024. This means that from August 1, you will find ePay's Order ID as before. The ePay payments that have been processed in the meantime will remain unchanged to avoid further unintended consequences.

To assist you as best as possible, we will provide full export files of your payment data, and you can always contact us at support@onlinefundraising.dk for questions or clarifications.

We apologize once again for the inconvenience, and we are in the process of revising our procedures to avoid similar situations in the future.

What's changed

• Email Service: We have improved our ability to validate domains for sending email addresses from the organization's domain.

• Communications: We have added standard fields for the organization's postal code and city.

• Export: We have updated the interface for the export module to align with our standards for future development.

• Form: We have added support for the URL parameter: "utm_id".

• Web Resources: We have adjusted the caching duration of web resources in OnlineFundraising's portal to prevent users from using a locally cached and outdated version.

• Internationalization: We have been working on further internationalization and translation of Danish terms for the benefit of our Icelandic customers.

Bugfixes

• MobilePay: Until now, we have not updated the agreement's amount in MobilePay's app, which is particularly relevant following upgrades via telemarketing.
• MobilePay: We have updated our handling of Refund callbacks according to the new API following MobilePay's migration with Vipps.
• QuickPay: Customers experienced that QuickPay no longer forwarded the provided phone number to MobilePay, which we have reviewed and fixed initially, however it seems several gateways are experiencing a similar issue in relation to MobilePay.
• QuickPay: In the event of failed charge attempts via QuickPay, we did not register the error code and message from QuickPay. This has now been corrected.
• QuickPay: We have improved our logging and handling of payment sessions where Strong Customer Authentication (SCA) was required, failed from the user's side, and then successfully retried.
• ePay: We have registered ePay's Order ID as the transaction number in OnlineFundraising, which we have now corrected.
• NETS Easy: We have fixed our handling of callbacks if the gateway is temporarily down.
• Teya: We have fixed various minor errors in our handling of callbacks from Teya.
• SMS Keyword: We have added a date restriction for SMS campaigns run by organizations that are not members of ISOBRO, as required by 4T under rammeaftalen.dk.
• DataSet: The information "isTransactional" was not correctly derived in all cases.
• Internationalization: We have fixed our validation of the Icelandic Kennitala (National ID).

What's new

In this release, we have practiced crossing national borders, starting with Iceland, which is why this release is named after Iceland's national flower.

Although all interfaces in OnlineFundraising are in English, we have realized how much we still think in Danish. Therefore, in this release, we have worked on our ability to translate and contextualize everything related to Forms and Communications.

However, the most significant addition is our integration with the Icelandic payment gateway, Teya (formerly SaltPay), allowing payment by card in Iceland via OnlineFundraising. We are incredibly pleased to offer this to our Icelandic customers, making it our fourth integration with a Payment Service Provider and our seventh payment solution overall.

But we are not done yet, as another integration is on the horizon, which will enable OnlineFundraising to accept "Direct Debit" payments via bank in Iceland.

What's new

This release has primarily focused on minor fixes, with the following highlights.

What's changed

• Manual merge of Contacts via the interface now includes all personal information.

• Integration with QuickPay has been improved in terms of handling callbacks.

Bug fixes

• The interface for email history displayed timestamps incorrectly.

• The interface for Payment Method lacked a nuance regarding Betalingsservice with FI cards.

• The interface for Communications used less appropriate examples in tests.

What's Changed

The wait is over! The Export Module has undergone a thorough optimization. The result is a significant decrease in report processing time - making the wait for your data much shorter. Here are the technical details:

• We refactored the data queries for each report, resulting in a significant decrease in report processing time.
• Reports which generally require short processing time are now processed in parallel with slower reports. In other words users can get insight to their data without having to wait for an unreasonable amount of time.
• We improved logging and monitoring of performance of the Export Module, enabling us to handle bottlenecks before it impacts our users.

The first couple of users have already reported that it is faster than lightning!

What's new

• We added a duplicate check of recipients to SMS Outbound. If a recipient is listed more than once when sending af batch of text messages they will only receive one text message. This saves the OnlineFundraising user time (and money spent on sent texts!)

Bug fixes

• Email templates in Communications: The merge tag {{purposeName}} did not work in email preview/test send when used in the email topic. This has been fixed.

...but we're still releasing! This channel has been quiet for a little while but the developers are still at work to maintain and improve OnlineFundraising. Everything will be summarised in our release notes, so keep an eye out for the next update.

Best regards,

The Development Team

What's new

We introduced a new feature which allows the OnlineFundraising user to inspect and copy the raw json of a DataSet. This is useful for debugging and analysis of DataSets.

What's changed

We have made some changes in the Email Service which improves the loading speed of the frontend, giving the OnlineFundraising user a smoother experience when working with the Communications module.

Bug fixes

We fixed a bug which caused some buttons in Communications to go missing in the UI for smaller screens, for instance a 13" laptop screen.

What's new

• We added the option to copy a value with one click. This makes it easier for users to copy e.g. a transaction no. for use in a separate system.

• It is now possible to interact with x- and y-axes on the dashboard. Use this feature to zoom in on your data and get all the details.

What's changed

• We optimized the Email History, which suffered from long response times in the UI. This is an improvement of the user experience and should bring down the time spent navigating in the Email History.
• Payment Methods are now sorted by newest first. If a Contact has many Payment Methods, it is possible to expand and collapse the list.

Bug fixes

• We fixed the Drag and drop-functionality in the email editor which did not work as intended. This bug prevented OnlineFundraising users from creating and editing email templates in Communications. Existing emails are not affected.
• The field contactType is no longer missing when editing Contacts. The field was only missing in the UI, and any data collected from forms or similar is intact.
• We removed the option to edit Shared Agreements. This option is not available, but was temporarily available after our latest major release.
• Labels in dashboard graphs have been fixed so they are not cut off or missing in smaller screen sizes.
• We re-introduced the error review funcitonality in SMS Outbound batches. When an OnlineFundraising user uplaods a batch to SMS outbound they may be errors associated with specific rows of the batch, and the review error functionality allows the user to inspect each error in order to resolve them. This functionality was missing since our latest major release and is now working as usual.
• SMS Campaigns no longer disappear if a user tries to create it without resolving errors. A typical error is that a required field has not been filled out. Errors are now highlighted so the OnlineFundraising user can correct them before creating the SMS Campaign wothout losing their changes.

We have launched a major release to OnlineFundraising which includes a Dashboard, major updates to Communications, and new features for SMS:

1. Dashboard: We are very happy to announce that the Dashboard has arrived to OnlineFundraising! The Dashboard replaces the OnlineFundraising home page and gives the user an overview of the big picture of the donations flow in OnlineFundraising.
2. SMS: We added some quality of life features that help users plan and execute SMS batches while minimising costs.
3. Communications: Some of the feedback we often get about Communications is that it is difficult to maintain. Many organisations end up with long lists of Communications and a lack of overview of which templates are being used. This release addresses these difficulties head on with some major updates, including a new overview, improved editor experience, as well as a number of features that are helpful in terms of maintaining Communications.

Read along to learn more about the details of the release, and let us know what you think in the Ideas section of this platform.

1. Dashboard

The Dashboard replaces the home page of OnlineFundraising and provides insight to:

1. Total amount collected this year
2. Total amount of expected payments next month
3. Bar chart showing the amount of charged payments pr. week the last month. Drill down to amount per payment method by hovering your mouse over each bar or select which payments methods to view data for by clicking on the legend.
4. Graph of the amount of expected payment pr. month for the next year
5. View the timestamp of when the Dashboard was last updated. The Dashboard is updated every night.
6. Users with a keen eye will notice the new search bar; this allows users to search for payments, contacts, and subscriptions in one place using the usual keywords.

We expect to add more features, such as export of data, graphs of SMS inbound and Outbound, additional filtering options, and the likes - let us know what you would like to see first.

2. SMS

What's new in SMS Inbound and Outbound:

• The SMS Inbound and Outbound have been moved to the same space in the menu so everything SMS related is found in one space.

• Users can now add SMS keywords directly from the Campaign, making the configuration process much simpler.
• We added the total number of sent messages to the Batch overview. This feature helps users identify if a batch was used for test or the real deal.
• Minimise your costs by minimising the number of messages in an SMS. We added a feature which highlights if your SMS is turning into several messages due to use of unicode characters and the likes.

3. Communications

We really aren't kidding when we say that we have made major updates to Communications. Read along for the details - or watch this video to get a demo of Communications from none other than Stephan Viftrup, Director of OnlineFundraising (in Danish).

3.1. New Communications Overview

The Communications overview has been greatly improved with the following features:

• View created date of Communication. Old Communications may be in need of a review, or they need to be removed all together.
• Colorcoded overview of templates. When a custom template is created it is colorcoded according to its status - green for active, and yellow for work in progress. If the circle is empty the template is inherited from parent Communication

• Hover over a template to see where it is inherited from and quickly edit Communication name

• Expand/collapse parent Communications to get a better overview
• Search for Communications by name to quickly locate the Communication you would like to work on
• Get helpful information about your Communication with our new notifications system. The notifications let you know if 1) the sender email domain is not validated or 2) your template is setup using the old editor. Communications using the old editor are usually outdated and need to be reviewed or removed

• Get an overview of which email domains are in use across all Communications and what their validation status is. Select a specific domain to highlight which Communications it is used for. This allows for easy cleanup in case your organisation has a change in domain or campaign specific domains need to be removed
• Quickly access a Communication Template by clicking on the corresponding icon. This saves our users several clicks and a lot of scrolling

3.2. Editing Communications

New features in editing Communications:

• We added the ability to change Parent Communication. If a Communication is moved it will inherit its templates from the new parent.
• Delete a Communication. Once a Communication is created it is usually there to stay, but in some cases users need to delete a Communication. For instance, if the Communication was created by mistake, replaced or outdated.
• Optimised navigation in Communications:
• Expand/Collapse all templates
• Copy/Paste buttons have been moved so they are easier for the user to find
• Edit inherited templates: Instead of having to create a new template, users can now select to edit inherited templates directly, saving them several clicks.

• Colorcoded template icons allows the user to quickly decode which templates have been activated, and which are still a work in progress.

• Improved editor experience:
1. On screen HTML is now created using a WYSIWYG editor (instead of flat HTML)
2. The visual email editor now has actions undo/redo, as well as the option to add a pre-header to the email
3. We made it easier to add merge tags in the SMS editor

3.2. Convert templates from old to new editor without losing your content

We improved the process for converting email templates from the old editor to the new editor by introducing af draft stage. When an email template is converted from the old editor to the new visual editor, the user can now review af draft before saving and replacing the original template.

Steps to convert to the visual editor now consist of:

1. Edit email template
2. Click 'Switch to visual editor'
3. Review old email and design in the visual editor
4. Click 'Convert and save'

4. Other

What's new:

• Hover over a menu item to see sub-items

Bug fixes:

• Communication now supports using the mergetag {{nextDueDate}} in format YYYY-MM-DD

Deprecated

• Betalingsservice has chosen to sunset the Mandate API 3.0 as of June 2023. This means that end-users can no longer authenticate Betalingsservice agreements using the Betalingsservice App. In correspondance, we have deprecated the implementation of the API in OnlineFundraising and removed. Betalingsservice is otherwise unaffected, and OnlineFundraising customers do not need to take any action. None of our current customers are affected by this change.

What's new

• OnlineFundraising's Quickpay Engine now supports MOTO (Mail Order or Telephone Order). This is available for customers who have a Quickpay agreement approved for MOTO.

Bug fixes

• We fixed a timestamp formating issue for OnlineFundraising user's who are using Firefox. Timestamps are correct in all other aspects.
• We fixed a UI bug where the fields National Id and Business Code were not properly displayed in the Contact overview. The fields are only displayed if they contain data.