Luminate Online Version 24 Release Notes

Release 24.5

Release 24.4.1

Release 24.4

Release 24.3

Email support for one-click unsubscribe

Release 24.2.3

Release 24.1.1

Release 24.0.1

 

Version 24.5 Release notes

November 2024

The Luminate Online 24.5 release contains feature enhancements and resolved issues for the new checkout.

Product Updates

Coming soon: Embedded checkout experience - Action required before March 2025

With this release, the new checkout experience provides an embedded (inline) payment section using the new checkout experience so that you can offer your form including all standard fields, while still meeting PCI v4 requirements. Embed the new checkout element within your form.

Note: Support for checkout embedded (inline) for TeamRaiser registrations is coming in the January 25.1 release.

The 24.5 release also provides checkout support for:

• Event Manager Center

• TeamRaiser Participant Centers

• Offline payments

• New reporting options

Details for all of these features are coming soon.

 

Version 24.4.1 Release notes

November 2024

The Luminate Online 24.4.1 release adds additional form validation for the new checkout feature, updates the Application name sent to Blackbaud Merchant Services as Luminate, updates email handling, and resolves an internal setup issue.

Email updates

Hard bounce limit set to 1

When an email address is deemed undeliverable, often due to an incorrect or inactive email address, the issue is known as a hard bounce. Bounced emails have a negative impact on sender reputation and email deliverability.

To align with industry standards and ensure a positive reputation, we've changed the maximum hard bounce count to 1. After one hard bounce, an email address is marked as Bad (Hard Bounce) in Luminate Online, and automatically filtered out of email sends.

Soft bounce suppression update

When an email address is recognized as valid by the server, but is temporarily blocked from delivery, the issue is known as a soft bounce. Email servers retry delivery until a threshold is met. This repeated activity can ultimately cause issues, because bounced emails have a negative impact on sender reputation and email deliverability.

To ensure a positive reputation and protect deliverability, we've changed the criteria for when a soft bounce status changes to a hard bounce status. Luminate Online now converts an email address to a status of Bad (Hard Bounce) when three consecutive soft bounces occur for the following codes:

• 3001: mailbox full/over quota

• 3002: inactive/disabled account

For example, if a sent email results in an error code of mailbox full twice for an email address, then on the 3rd failed delivery, the status of that email address changes to Bad (Hard Bounce). However, if the third time is successful, the count is reset, and the status will not change until three more bounces occur.

A reduction of soft bounces is expected as abandoned emails filter out, as well as a temporary increase in hard bounce counts. To view bounce codes, run an Admin Bounce Detail Report.

 

Version 24.4 Release notes

October 2024

The Luminate Online 24.4 release contains security updates, feature enhancements, and resolved issues.

Product Updates

• Redirect security enhancement - Action required by Oct 30th for redirects to external sites

• New modal checkout experience - Action required before March 2025

• API support for Checkout - Action required for API-based forms before March 2025

• Authenticator app support for administrators

• Good Move App Sponsor Management

• Good Move App Support Permissions

• New columns available in Live Event Participant Report

• Support for Client APIs with third-party cookie blocking

• Enhancements to help documentation

 

Redirect security enhancement - Action required by Oct 30th for redirects to external sites

On October 30, 2024, Blackbaud will implement enhancements to protect your organization's Luminate site when a user is redirected from a Luminate Online page to an external domain.

Your organization may need to take action:

• If you do not redirect Luminate Online pages to an external site, then NO action is required.

• If you do redirect, or you are unsure, then before October 30, complete the steps in Knowledgebase article, How do I block external domains from being used in NEXTURL? to allow the redirect to continue to function properly by adding the external domain to an "allow" list.

 

New modal checkout experience - Action required before March 2025

A new checkout experience provides a dynamic, secure, and PCI v4-compliant payment transaction for your payment forms. The new checkout experience has plenty of advantages and upgrades, including end-to-end transaction management in Blackbaud Merchant Services (BBMS), more payment methods, such as Apple Pay and Google Pay, and an improved user experience.

To use the new checkout, you need a Blackbaud Payment Services (BBPS) account, and you must update your active forms before March 2025.

Warning: The new Payment Card Industry (PCI) standards effective March 2025 will be met using the new checkout experience. Your action is required to adopt the new checkout offering through making a payment configuration change and adding a new checkout element to your active forms before March 2025.

In this release, checkout is available as a modal experience. The next release, 24.5, will include the embedded, inline version of checkout.

Learn more in our Checkout FAQs.

For step-by-step guidance to get started after the 24.4 release, see Update your Checkout Experience.

The French Canadian locale is supported in the checkout modal.

Tip: Join us for workshops that walk through how to update your donation forms for checkout! Register at Payment Checkout for Blackbaud Luminate Online Workshops.

Tip: New eLearning is available to support preparing for the checkout experience. See Level Up with Luminate Online .

Note: Merchant accounts that support the Discover Card have been configured to support Diners Club as a credit card payment type as well. This will be more fully addressed in a future release.

 

API support for Checkout - Action required for API-based forms before March 2025

Before March 2025, update your active API-based forms to use the new checkout APIs. Although the previous transaction-handling Luminate Online APIs remain valid until March 2025 to ensure no impact to your existing donation forms during giving season, the new or updated PCI v4-compliant APIs are available in this release so you can begin testing.

Forms that use the previous APIs will continue to work until March 2025; however, make plans to identify your active (or soon-to-be-active) forms, then understand the methods you must change.

NOTICE: Before March 2025, update the following API methods in your forms. Again, both APIs will run concurrently until March 2025 at which time the previous method will be deprecated.

Note: If you use addGift for offline payments, you must update the method to addGiftCheckout.

PREVIOUS method	NEW method
donate	donateCheckout
offlineOrganizationGift	offlineOrganizationGiftCheckout
addGift	addGiftCheckout

New payment-handling API methods

The following new methods use transaction tokens to handle payment information.

• donateCheckout - Similar to the donate API, this method meets PCI v4 requirements for credit card and debit card transactions. This method is only compatible with transactions in the new checkout. See donateCheckout.

  Note: Replace donate with donateCheckout before March 2025.

• offlineOrganizationGiftCheckout - Similar to the offlineOrganizationGift API, this method meets PCI v4 requirements for credit card and debit card transactions. This method is only compatible with transactions in the new checkout. See offlineOrganizationGiftCheckout.

  Note: Replace offlineOrganizationGift with offlineOrganizationGiftCheckout before March 2025.

• addGiftCheckout - Similar to the addGift API, this method meets PCI v4 requirements for credit card and debit card transactions. This method is only compatible with transactions in the new checkout. See addGiftCheckout.

  If you use addGift for offline payments, update the method to addGiftCheckout.

  Note: Replace addGift with addGiftCheckout before March 2025.

New validation methods

The following new methods verify your form.

• validateDonateCheckout validates whether the payload passing in donateCheckout is valid or not.

• validateProcessRegistration validates whether the payload passing in processRegistration is valid or not.

• validateAddGiftCheckout validates whether the payload passing in AddGiftCheckout is valid or not.

• validateOfflineOrganizationGiftCheckout validates whether the payload passing in OfflineOrganizationGiftCheckout is valid or not.

Updated API methods

• Both processRegistration and refundTransaction were not replaced so as to minimize impact. However, changes were made to their logic and behavior. The new behavior reviews whether a transaction token is passed in the payload instead of card credentials.

  Until March 2025, if the transaction token is not passed in the payload, then these APIs revert to reviewing the card credentials passed within the payload and behave as the APIs do today.

  After March 2025, the APIs will only operate using transaction token data.

  The APIs were also updated to handle any transaction type supported in Luminate Online, including checkout transactions.

• In a future release, ProcessRegistration will handle PayPal payment methods (and other payment methods), so processRegistrationPaypal will no longer be needed.

• getTeamRaiserConfig no longer returns a transaction token or payment information.

See our Overview of Checkout API for information on the Luminate API updates.

See our Integration Guide for steps to connect Luminate Online forms with Blackbaud Merchant Services.

Note: startDonation is unchanged.

 

Authenticator app support for administrators

Administrators can now use an Authentication app, such as Microsoft Authenticator or Google Authenticator, for their multi-factor authentication (MFA) when they log in to Luminate Online. This Time-based One-Time Password (TOTP) option offers an alternative to SMS (text) as a second method of authentication.

When you enable TOTP, the previous SMS option can also remain available.

You will need to first enable the TOTP feature, then administrators must set up their authentication app to connect with their Luminate Online account as a one-time setup.

Currently, this feature prompts for an authentication app code upon each login, but support for 30-day authentication is coming in a future release.

Note: When the authenticator app feature is enabled for your site and administrators set up authentication with an app, be aware that if you later disable TOTP for your site, those administrators will no longer be able to log in.

See Multi-factor Authentication for Administrators.

 

Good Move App Sponsor Management

Coming soon, we'll release the ability to add and manage your own in-app sponsor placements through the Good Move App Setup configuration in TeamRaiser.

See Add In-app Sponsors to Good Move.

 

Good Move App Support Permissions

To grant administrative access to the Good Move Support functions, you can now update permissions for a new or existing user group.

From TeamRaiser Management, you can grant access to the Good Move Support tab for groups with the permission levels Register, Manage, and Email Participants and Manage Companies and above.

Users with this permission can access the Good Move Support tab to find events with Good Move, view participants, and manage activities in activity tracking–enabled events.

See Good Move Administrative Support Permissions.

 

New columns available in Live Event Participant Report

So that you can easily see additional participant data at a glance, you can now add four new columns to the Live Event Participant Report:

• Personalized Page URL

• Team Division

• Team Fundraising Goal

• Team Fundraising Total

See Live Event Participant Report.

 

Enhancements to help documentation

Coming soon: To make it easier for you to consume help resources, we’re updating the look and organization of our help documentation and adding additional support for assistive technology users. Examples of accessibility updates include:

• Screen reader labels on documentation feedback form inputs

• Help content styles

• Contrast between notes and tips

• Nested subheadings for scanning content

 

Support for Client APIs with third-party cookie blocking

To ensure your sites are not impacted in the event that a browser, such as Google Chrome, begins blocking third-party cookies, we made updates to ensure your URL page redirects from a logged-in Luminate Online page to another organizational site maintains the login and completes successfully.

To maintain a logged-in status from Luminate client APIs in the event of third-party cookie blocking, Luminate Online API administrators can use the S1112 S-Tag to append any URL with a nonce token to handle external redirects. The S-Tag ensures that the NONCE_TOKEN is included in a URL.

See the S1112 Nonce Token help documentation.

 

Resolved Issues

Issues were resolved in: Advocacy | Calendar Event | Content | Donations | eCommerce | Email | Reports | System | TeamRaiser

Advocacy

Bug	Description
2445721	The Find Representative tool lists a numerical ID instead of the district name When the Find Representative tool is included on a PageBuilder page, the constituent sees the name of the district instead of the district number in the selector.

Calendar Event

Bug	Description
3010769	On a Calendar Event, when the "Walk-Ins allowed" option is selected for RSVP events, users cannot register for ongoing events, because the page redirects the user to the event page For an RSVP Calendar Event, when the "Walk-Ins allowed" option is selected, users are able to register for an event that is ongoing.

Content

Bug	Description
2969951	When the "Page Not Found" page is renamed or unpublished in PageBuilder and a user tries to access a different unpublished page, a Technical Difficulties error occurs To prevent a Technical Difficulties errors when a site visitor attempts to view a page that was unpublished, administrators are now restricted from renaming, archiving or unpublishing the Page Not Found (page_not_found) PageBuilder page.
3058223	The Image Library does not upload images when the site locale default is French Canadian (site_default_locale fr_CA) The Image Library successfully uploads images when the site locale default is French Canadian (site_default_locale is fr_CA).

Donations

Bug	Description
2442541	When a credit card number follows a letter character, some donation form text fields allow the entry, causing data issues in reports Additional validation on a donation form now prevents the erroneous entry of a credit card number in a constituent information text field.
2938431	On a desktop, the embed a Donate button has display issues On a desktop, the Embed a Donate button brings up legacy Blackbaud Checkout without any display issues.
2966985	In the legacy Blackbaud Checkout modal, the default country ignores localization for Canada For a MultiLocale site, when using the legacy Blackbaud Checkout payment modal from the S1300 tag and the default country is set to Canada, the language in the modal now displays for Canadian English.
3018565	When making a Tribute/Honor donation, an email is sent to the donor and logged in Luminate Online even when the eCard option is not selected When a donation is made toward a Tribute or Honor fundraiser and the eCard option is not selected, an email is not sent, and we do not record the email in Luminate Online.
3053623	Wen recurring gifts are declined by California Assembly Bill 488 (CA AB 488), the decline code sets an end date based on retry settings, and uses a different donation type than other recurring gift declines Recurring gifts that are declined by CA AB 488 are identified with a new donation type decline code of "42." Donation type 42 does not set an end date, and the recurring gift failure settings are used for the next payment date.

eCommerce

Bug	Description
3032565	When creating an eCommerce product without an image, selecting the product link in the store displays a broken image icon due to an img src tag eCommerce products that do not have an image no longer show a broken image when the product is selected in the eCommerce store.

Email

Bug	Description
2499081	The task-built Do Not Send group allows constituents to receive email after the group rebuilds Members of a "Do Not Send" group do not receive email even after the group is rebuilt.
2501339	The email Powered By Blackbaud logo is fuzzy The "Powered By Blackbaud" logo on emails was updated to use a higher resolution image.
3010752	Email deliveries stuck in Pending status We've updated our email handling to prevent email deliveries from being left in a state of "Pending".

Reports

Bug	Description
2504365	The TeamRaiser Event Survey report in Report Writer has two filters, one for event selection and one for survey instance, in the Configure Filter step instead of just one filter for the event selection In the Configure Filter step of the TeamRaiser Event Survey report in Report Writer, you will now see only one filter option for the event. We have also added these privacy fields to this report: Global Privacy Control Opt-Out Profiling Opt-Out Sale of Personal Data Opt-Out Targeted Ads Opt-Out
3021519	Choosing to filter by Active donation forms when running the Donations by Form report in the Donations module includes forms that are "unpublished" when their expiration date is in the past Filtering by Active donation forms when running the Donations by Form report in the Donations module no longer includes unpublished forms.
3054972	After the Luminate Online 24.3 release, the Donations by Form report outputs multiple rows for a single Form ID The Donations by Form report now returns only one row per Form ID.

System

Bug	Description
2661253	Unable to delete queries by selecting all When selecting multiple queries for deletion, the system now deletes all selected queries at once.
2661274	When in the French locale, the English version, instead of the French version, shows for the text, "You are currently logged in as," and "a previous transaction for." When a site is configured for MultiLocale and the French language is selected, a user now sees the French version of "You are currently logged in as" and "a previous transaction for."
2732378	Unneccessary Console.Logs are included in product .js files We have removed Console.Logs when running the productized JS scripts.
2804200	When S120:dc:refundAmount is added to the "TeamRaiser Registration Full Refund" autoresponder, the value shows as "Refund Amount" instead of showing the amount being refunded When S120:dc:refundAmount is added to the "TeamRaiser Registration Full Refund" autoresponder, the amount being refunded is shown as the value in the autoresponder.
2953871	In MultiLocale, the country name, "Saint Pierre and Miquelon," does not appear in the Country list for the fr_CA locale For a MultiLocale site, when the language is set to French, a Country drop-down list now includes the country name, "Saint Pierre and Miquelon."
2965539 | 3080259	For some MultiLocale sites, the constituent profile does not display French locale labels when editing or viewing the profile On a MultiLocale site enabled for French, when a constituent visits their profile to view or edit the page and French is detected in their session, labels and fields show the French language.
2991051	Administrators in various countries cannot receive SMS (text) messages to authenticate into Luminate Online due to account settings, so need an alternative method With the increase in necessity of multifactor authentication (MFA), administrators can now use an authentication app to log in to Luminate Online as an alternative to the SMS option.
3052092	When editing labels in the Message Catalog, non-English characters do not properly save When editing labels in the Message Catalog and using non-English characters, such as French/Spanish accented characters, the characters save as expected and are rendered correctly to constituents.

TeamRaiser

Bug	Description
2623759	In some situations, TeamRaiser registration can cause duplicate constituent records An update was made to prevent duplicate records such as when there is a title difference or change in case in part of the address.
2659623	When creating a coaching email, some options cause the previous year's opt-out group to be included in the Do Not Email group When creating a coaching email, only this year's opt-out group is excluded from email sends.
2856868	When a participant's Gmail account has no records in the Contacts folder/category, but they do have autosaved records from received or sent emails, the email import for Gmail tool in the Participant Center shows a "No contacts to display" error The Import contacts for Gmail tool in the Participant Center now also searches for autosaved records from received or sent emails so that those can be imported into a Participant Center, even when the records are not part of the Contacts list.
2992761	The autoresponder for the First Good Move App Announcement email autoresponder is not being delivered after a participant registers for a TeamRaiser After a participant registers for a TeamRaiser that is enabled with Good Move, the First Good Move App Announcement email is now delivered automatically to their email address registered for that TeamRaiser event.
3028732	A participant's company association doesn't save when team formation is disabled on a TeamRaiser For TeamRaisers that do not have the team formation option enabled, participants can choose to associate with a company and the information is saved.
3052126	Sometimes when aTeamRaiser is archived, they do not stay in an archived state after certain dates are set and the TeamRaiser Campaign Status Updater task runs After a TeamRaiser is set in the Archived state, the event stays archived even when dates are set or the TeamRaiser Campaign Status Updater task runs.

 

Version 24.3 Release notes

August 2024

The Luminate Online 24.3 release contains security and encryption updates, feature enhancements, and resolved issues.

 

Product Updates

Good Move Support Portal in TeamRaiser

With the TeamRaiser Good Move support portal, you can manage participants associated with your Good Move–enabled TeamRaisers. You can search for and view events and participants; for participants of activity tracking–enabled events, you can add, edit, or remove activities and points on their behalf.

For more information, see Good Move Administrative Support Tools.

 

Good Move Support Portal for Blackbaud Support

Blackbaud Support staff now has access to a Good Move Support Portal to assist your organization with participant management in your Good Move–enabled TeamRaisers. Blackbaud Support staff can search for and view events and participants; for participants of activity tracking–enabled events, Blackbaud Support staff can add, edit, or remove activities and points on their behalf.

 

Good Move App Translation

Your supporters can now access English, French, French-CA, and Spanish language preferences in the Good Move App.

For more information, see Accessibility in the Good Move: Example Responses to Support Your Participants guide.

 

Configure Live Participant Report permissions for event managers

As an enhancement to the TeamRaiser Live Participant Report, you can now allow event managers to access the report in the Event Management Center.

 

From Event Manager Permissions, select whether to allow event managers access to view the Live Participant Report. You can optionally choose whether event managers should also have access to download the report or to use the Email Contact action for participants.

 

For more information, see the Live Event Participant Report help documentation.

 

New columns in the Donations by Form report

More data has been added to the Donations by Form report so you can monitor and compare success across forms and campaigns. Success of a form is measured in total funds, number of transactions, and percent of campaign transactions. With this release, the report now also compares the transactions coming from standard forms verses transactions from custom API forms. We also added the form status so you can see your published, unpublished, or archived forms.

Note: Transactional data comparing custom API forms to standard forms reflects donations made after the 24.3 release. Donations made prior to the release are not included in this data at this time.

For more information, see the Donations by Form help documentation.

 

Email Express guidance for secure links

To ensure that all links used in Email Express content are secure links, the content editor now displays a pop-up to guide you in updating the URL address from http to https.

 

Raiser's Edge Integration handles lengthy field values

To ensure a successful sync of constituent field values from Raiser's Edge into Luminate Online using Raiser's Edge Luminate Online Integration (RELO), constituent field values with character lengths that exceed the Luminate Online restriction are now truncated to the maximum length allowed by Luminate Online.

If you wish to avoid truncation, ensure that constituent field values do not exceed the character length restrictions in Luminate Online.

Luminate Online constituent field character restrictions

The Luminate Online default character restrictions for constituent fields are listed below.

Salutation (50)

SalutationCasual (50)

SalutationFormal (50)

FirstName (50)

MiddleName (50)

LastName (50)

MaidenName (50)

NickName (50)

Suffix (50)

WorkTitle (64)

ProfessionalSuffix (50)

Gender (20)

MaritalStatus (20)

Ethnicity (64)

Religion (64)

HomeCity (64)

HomeState (30)

HomeCountry (64)

HomeCounty (100)

SpouseTitle (50)

SpouseFirstName (50)

SpouseMiddleName (50)

SpoouseLastName (50)

SpouseSuffix (50)

EmployerCity (64)

EmployerState (30)

EmployerPostalCode (40)

EmployerCountry (64)

EmployerState (30)

EmployerPostalCode (40)

EmployerCountry (64)

 

Resolved Issues

Issues were resolved in: API | Calendar Events | Constituent360 | Donations| Email | Event Management Center | Events | Raiser's Edge Integration (RELO) | Reports| System | TeamRaiser

API

Bug	Description
2817270	In a private browsing session on Mozilla Firefox, users cannot log into their member center via the CRConsAPI and causes the error, "Error: ORA-02291: integrity constraint (SHORTNAME.OPT_OUT_CONS_ID_FK) violated - parent key not found" Users can now log into their member center in a private browsing session on Mozilla Firefox.
2876609	When the amount_confirmed parameter has a large value, the getCompaniesbyInfo API call can fail The getCompaniesbyInfo API call no longer fails when there is a large amount_confirmed value.

Calendar Events

Bug	Description
2473278	When a $0 ticket is purchased from a Calendar event, the administrator notification email does not send Calendar events configured to include a Ticket Purchase Notification for a $0 ticket now send the administrator notification email to the email entered in configuration.

Constituent360

Bug	Description
2849915	When trying to add an organization gift in the Transaction tab of a constituent record in Constituent360, an "Internal server error" occurs When organizations are supported, you can once again add an organization gift in the Transaction tab of a constituent record.
2890377	In a user's profile, field values show as "null" when selections are made for Date and Amount User profiles no longer show fields with a "null" value.

Donations

Bug	Description
2854163	Accessing a donation form with invalid parameters generates a NullPointerException and Technical Difficulties page When a donor accesses a donation form with invalid or missing required parameters in the URL, the page now directs to the site homepage instead of showing a Technical Difficulties page.
2874672	Recurring gifts created between 9/13-3/12 have sender_email set on subsequent recurring gift payments Recurring gifts that are not Tributes no longer have a value set in Sender_email.
2894519	When a custom data element is created before Multi Locale is enabled, the data element does not allow French Canadian (fr_CA) donations to go through A custom donation form element that was created prior to enabling Multi Locale now processes French Locale transactions as expected.
2697138	Blackbaud Checkout direct debit recurring gift payments fail on subsequent recurring gift payments Direct debit recurring gift payments made through Blackbaud Checkout no longer fail on subsequent payments.
2933274	When adding custom source and subsource codes to the URL of a Blackbaud Checkout page, "SecurePayAPI" shows in the reporting When setting a custom source or subsource code in the URL of a Blackbaud Checkout page, the defined sources now display in reports.
2937085	A new custom data element on a donation form requires the a user-entered value option You can now successfully save a custom data element on a donation form without selecting the option, "Yes, also let donors enter their own value."

Email

Bug	Description
2157114	In the new email experience, the styling options are not consistent between the configuration settings When adding styling to text in the new email experience, the multiple styling options now use consistent language and configuration options.
2842168	In the new email experience, if the group summary is not up to date, calculating an audience will show an incorrect calculation When selecting groups in the new email experience, the audience group members are correctly calculated.
2868331, 2661636	Email campaigns sometimes show a "Content Error" in the email summary and generate a duplicate email jobID An update was made to prevent duplicate email jobIDs for Email Campaign messages.
2911634	Email messages continues to try to send repeatedly when a particular error occurs, causing constituents to receive duplicate emails Email messages that encounter a specific error while attempting to send will now pause the send until the error is resolved.
2965664	In email classic, sent emails cannot be returned to Draft status Sent classic emails can once again be returned to Draft status using the Return to Draft option.

Event Management Center

Bug	Description
2901784	When approving a message in the Event Manager Center, the following error appears: "There was an error approving this message" In the Event Manager Center, approving a message no longer causes an error to display.

Events

Bug	Description
2887353	Event ticket purchase notifications are sent to administrators for a declined transaction Administrators only get notification of an event ticket purchase when a constituent's registration successfully completes.

Raiser's Edge Integration (RELO)

Bug	Description
2774800	Unable to sync new organization donation contacts with the error, "UniversalFieldMapperException - Unhandled Online value for field 'Origin': 110" Constituents created from organization gifts now sync successfully to Raiser's Edge from Luminate Online.
2774800	Following the Luminate Online 24.2.1 release, old Queue Problem Management (QPM) errors appear that cannot be rebuilt Old errors no longer display in Queue Problem Management (QPM).

Reports

Bug	Description
2841559	Certain filter choices cause the Email Opt-In Status Report to encounter an ORA-00904 error causing it to return incorrect data or no data In Data Management, Reports, Reports Classic, the Email Opt-In Status Report displays correct results based on any filter selected.
2880314	The Email Performance Report by Group report fails on large sites when adding the Donation Response Rate (%) column Adding the Donation Response Rate (%) column to the Email Performance Report on a large site no longer causes the report to fail.

System

Bug	Description
2826324	When trying to run a Mail Merge that uses the Any Registered User group, the merge gets Aborted In Data Management, Mail Merges, creating a new mail merge and selecting the Any Registered User group now successfully performs the mail merge.
2949885	Last Login History does not display on the View Profile page The Luminate Online 24.2.1 release added a timestamp of the last login date to the screen for administrators and to profile pages for constituents. In this release, more profile screens were added so that constituents can view their last login timestamp.
2961712	When a recently added Site Option is set to FALSE, Luminate Online does not enforce a minimum password length for user passwords All user passwords must follow the minimum character requirement of 12 characters.
2994895	Last Login information text should not be visible without Cons login Constituents are not able to view their last login date and time details until they are logged in.

TeamRaiser

Bug	Description
2476928	On a Personal Page, YouTube Shorts do not embed properly and shows an error when trying to play it On a TeamRaiser Personal Page, YouTube shorts now embed properly and play without error.
2835628	In the subject line of the "Thank you for Registering" TeamRaiser autoresponder email, S-Tags and conditionals do not work S-Tags and conditionals now work correctly in the subject line of the "Thank You for Registering" TeamRaiser autoresponder email.
2852566	Update the language describing Good Move in the Participant Center We've updated the language in the Participant Center that explains Good Move.
2853471	In Participant Center 3, the Previous and Next buttons do not update to use the selected locale language When a TeamRaiser participant has a preferred locale, Participant Center 3 shows the Previous and Next buttons in the specified language.
2908315, 2950537	When a TeamRaiser has more than 1000 participants, the Live Participant Report shows the error, "An unexpected error occurred" In TeamRaiser, the Live Participant Report now supports an unlimited number of participants in the event.
2950161	After a duplicate constituent record merge, Good Move activity progress can sometimes not render or show as "null" After a duplicate constituent record merge, TeamRaiser Good Move activity progress displays as expected on constituent pages.
2965535	TeamRaiser Blueprint notifications can sometimes send to extra events if the notification is not fully deleted Deleted notifications no longer send occasionally to TeamRaiser Blueprint events.
2969205	When editing new forms or copied forms on the TeamRaiser Payments Page, a Technical Difficulties error occurs You can now successfully save changes to new and copied forms when made on the TeamRaiser > Edit > Customize Pages > Payments Page.

 

Email support for one-click unsubscribe

July 17, 2024

Luminate Online bulk emails now fully comply with one-click unsubscribe requirements from all email providers, including Google Gmail. Powered by Blackbaud Communications Services (BBCS), all bulk emails now feature a "list-unsubscribe" header. This ensures that your Luminate Online emails remain compliant with any future enforcement of this requirement by email providers, safeguarding your email deliverability ratings. This update is already in effect, and no action is required on your part to meet the one-click unsubscribe requirement.

 

Version 24.2.3 Release notes

May 2024

The Luminate Online 24.2.3 release contains security updates, feature enhancements, and resolved issues.

 

Product Updates

• Good Move Blueprint updates in Notification Manager

• Good Move Blueprint date and time lock

• Live Participant Report enhancements

• Account Lockout Recovery

• Last Login Date

Note: Link Manager is undergoing further enhancements to improve its functionality and will be released at a later date.

Good Move and Blueprint TeamRaiser Events

Good Move Blueprint updates in Notification Manager

If you use Blueprint TeamRaisers, you can now set your event communication strategy up for success by creating draft push notifications at the Blueprint level that you can copy down to all of your child TeamRaisers.

For example, if you have 20 child events based on a single Blueprint TeamRaiser, you can create one notification in your Blueprint that you can push as a draft to all 20 of your child events.

How do I create a Blueprint Good Move notification for all child events?

1. In Fundraising, TeamRaiser, select the Good Move Notification Manager tab.

2. Select the Blueprints tab and locate your Blueprint TeamRaiser.

3. To the left of the Blueprint TeamRaiser name, select the ellipses (. . .) menu.

4. Select Manage notifications.

   

5. Select New notification.

6. Enter the Title, Body, and optional Call-To-Action URL and button labels. When done, the notification saves as a draft.

   

7. When you’re ready to copy the Blueprint notification to your child TeamRaisers, select Push Changes.

   

8. A confirmation message displays the number of notifications that will push and how many child events will receive the notifications.

Tip: Blueprint notifications push down to child TeamRaisers in draft mode. You or your event managers can review the notification, choose a delivery method, and decide when to send the notification to participants.

For more information, see Blueprint TeamRaisers: Manage Good Move App Configuration and Push Notifications for Child Events.

 

Good Move Blueprint date and time lock

For Blueprint TeamRaiser events that use Good Move activity tracking, you can now lock date and time selections separately from the entire section.

When a Blueprint event locks the entire Activity Tracking section, but unlocks the date and time option, child events can edit the date and time, while other activity tracking settings remain locked.

For more information, see Blueprint TeamRaisers: Manage Good Move App Configuration and Push Notifications for Child Events.

Live Participant Report enhancements

In April, we released the TeamRaiser Live Participant Report. With this release, we've added the following enhancements.

Note: Currently, only administrators with the Design and Configure TeamRaiser and Register and Manage Participants permission levels can access the Live Participant Report.

Live Participant Page view

On the Live Participant Page view, the Top Donation information is now included. You'll see the top donor name and gift amount for the participant whose record page you are viewing, and a link that goes to the top donor's constituent record.

For more information, see TeamRaiser Live Participant Report.

 

Account Lockout Recovery

You can now unlock an administrator or user account in Constituent360.

After an excessive number of unsuccessful attempts at log in, an account is placed in a locked state for protection. Starting with this release, we now send an autoresponder email to the email address associated with the locked account, and we've added an Unlock Account option so you can manually unlock an account.

When an account is locked, the autoresponder email that is sent to the email address associated with the account states:

"Your account is locked due to an excessive number of failed login attempts. Please either try again later, contact the organization, or follow the "Forgot Password" steps to reset your password."

In Constituent360, a locked account record displays the following language:

"This account is locked due to excessive failed login attempts."

Locked accounts can be recovered in one of three ways:

• Follow the Forgot Password option to reset password and access the account

• Wait for a set time until the account is unlocked by the system

• Unlock the account in Constituent360 using this new Unlock Account feature

How do I unlock an administrator account?

1. To unlock an administrator account, go to Constituent360 and search for the profile.

2. Open the profile and select Unlock Account.

   

3. Select Unlock Account.

   

4. The account is now unlocked.

 

Last Login Date

Administrators and constituents can now view the date and time of their last successful login to their account. Viewing the last login date can help to clarify activity and allow for the catch of suspicious logins.

Administrators can see this date in the upper right of Luminate Online. Users can see this on their profile.

 

Resolved Issues

Issues were resolved in: API | Constituent360| Donations | Good Move | MultiLocale | Payments| System | TeamRaiser

API

Bug	Description
2865646	The AddGift API call does not respect Honoree fields Honoree/Tribute data is now created and captured in the donor_recognition_log when included in the AddGift API call.

Constituent360

Bug	Description
2646854	In a Constituent profile, the Transaction Information fields can be set incorrectly after certain refunds or transaction type changes After a change in a transaction, such as an update, refund, or deletion, Constituent Transaction Info fields are set correctly.

Donations

Bug	Description
2770156	Unable to confirm National/Cross Event Company gifts You can now confirm National Gifts by going to the Cross-Event Companies tab, then the National Companies tab, then on the Gifts page, select Confirm for the gift.
2805343	Donation form fields that are required to comply with California Assembly Bill 488 can be removed from the Transaction Summary data element Certain fields in the Transaction Summary data element can no longer be removed to ensure compliance with California Assembly Bill 488. The required fields include billing name, address, and email. When trying to remove the fields from the element, a message explains that they are required.

Good Move

Bug	Description
2803757	When participants receive the First Good Move App Announcement email autoresponder, the button to download the app does not appear when viewing the email from a mobile device Participants who receive and view the First Good Move App Announcement email autoresponder on a mobile device now see the button to get to the app in the app store.

MultiLocale

Bug	Description
2774651	Offline gift autoresponders do not send in the preferred locale Autoresponder emails for offline gifts are now sent in the language that is specified in the preferred locale setting.

Payments

Bug	Description
2816445	Blackbaud Merchant Services ACH transactions that fail with "The customer's bank account could not be located" are not being reversed in Luminate Online in some or all situations. When an ACH transaction is reversed in Blackbaud Merchant Services, the Luminate Online transaction is removed to keep the systems aligned.

System

Bug	Description
2080987	The Group Summary is not updated when all members are removed In 24.1, an update was made so that after removing all members of a group, the Group Summary now updates to reflect the correct number of members in the group. In this release, we've ensured the same behavior works after enhancements were made in query handling.
2755638	When performing a duplicate constituent record merge, a time out error occurs Merging two duplicate constituent records into one record now saves successfully.

TeamRaiser

Bug	Description
2653542	After managing Security Categories of a Regional Company, subsequent Regional Companies managed in the same session show the same Security Categories When managing Regional Companies, the Security Categories for that specific regional company are the only Security Categories that display.
2816779	In Reports Classic, the TeamRaiser Participant Summary Report gives a blank screen when you select the "Show All Donors to Participants" and "Donor Information for Direct Donations" options The Reports Classic report, TeamRaiser Participant Summary Report, now works as expected when the options are selected to Show All Donors to Participants and Include Donor Information for Direct Donations.
2831741	Recording offline gifts for National Companies does not increase the status indicator or company donations tally When manually adding a gift to a National Company in Luminate Online, the gift is now reflected in the gift total and number of gifts.
2836940	Facebook gifts toward a donation form that is archived or inaccessible in Luminate Online are not recorded in Luminate Online Luminate Online now captures and updates totals for Facebook gifts that are made to donation forms that are in an archived or inaccessible state in Luminate Online. If you should want to prevent Facebook gifts from being captured for donation forms that are archived or inaccessible, set the new Site Option, FACEBOOK_IGNORE_FORM_PERMISSIONS, to FALSE.
2853020	The TeamRaiser Team Summary Report in Report Classic returns a blank screen when the option "Show all team members as well as team summary" is selected The TeamRaiser Team Summary Report under Report Classic, TeamRaiser Report no longer returns a blank screen when the "Show all team members as well as team summary" option is selected.
2840157	The Live Participant Report page and Excel file don’t show all responses for questions with multiple choices and multiple responses The Live Participant Report and Excel file now display all questions and responses.
2859254	After the 24.1.1 release, the S42 tag returned the value for the dollars parameter when an invalid parameter, such as fr_id instead of fr-id, was used If an invalid parameter is used with the S42 S-Tag, the value is now returned as an empty string instead of the value of the dollars parameter. Note: When using the S42 S-Tag to get the TeamRaiser ID, be sure to use the correct parameter of fr-id (not fr_id).
2860297	In some cases, the secondary registration count is set incorrectly causing lists and status indicators to be incorrect Secondary registrations are now correctly counted for each constituent in lists and status indicators.
2867883	In an site with regional companies enabled, an error occurs when trying to associate a security category with a regional company You can now successfully associate a security category with a regional company.
2874941	Issues are seen in the TeamRaiser Participant Summary Report and Company Gifts Report Updates were made to resolve issues in the TeamRaiser Participant Summary Report and Company Gifts Report.
2879505	When a participant receives a Facebook gift, the gift is synced to Luminate Online under the donation campaign's security category which can be different than the TeamRaiser security category Facebook gifts are now recorded and associated to the same security category that is set for their TeamRaiser event to match the non-Facebook donation behavior.
2882850	Facebook donations can sync in duplicate to TeamRaiser when gifts have the same Facebook donation ID We've updated customer data to resolve a unique situation that caused duplicate TeamRaiser gift data. Each Facebook donation now has a unique donation ID.
2883815	Transaction reports don't always identify the donor-provided first and last name for a Facebook Fundraising gift To match transaction data in constituent profiles, Transaction reports now display a Facebook donor's first and last name when that data is provided, instead of "Facebook Fundraiser."
2885665	In the Live Participant Report, the Fundraising Total column does not always match the total reported and confirmed amounts The Fundraising Total column now matches the total confirmed and reported amounts in the TeamRaiser Live Participant Report.
2882822	In the Participant Record Page of the Live Participant Report, some issues related to team member tag, personal actual, and donor count fields exist In the Participant Record Page of the Live Participant Report, the following updates were made: The Team Member tag now only displays when the participant is a member of a team. The Email button only appears when the participant has a registered email address. Personal actual shows the sum of all gifts. Donor count is the number of people that made gifts (excluding duplications).
2887048	The QR code to download Good Move does not display on Thank You pages on a desktop browser When using a desktop browser view, the Thank You page now displays the QR code to download the Good Move app.
2891083	Facebook donors receive a "thank you" autoresponder email from Luminate Online, but they already get a "thank you" email from PayPal Giving Fund/Facebook You can now choose to prevent the Luminate Online thank you autoresponder from sending to Facebook donors, since they will receive an email from PayPal Giving Fund/Facebook when a donation is made to a Facebook Fundraiser and they include their email address. To prevent the Offline Gift Thank You autoresponder email from sending to Facebook donors: Go to Setup, Site Options. Search for FACEBOOK_SEND_AUTORESPONDER_FOR_FB_GIFTS. Set the value to FALSE, then Save.
2895517	In the Custom Questions tab of the Live Participant Report, there are duplicate questions and answers The Custom Questions tab now shows all custom questions and answers with no duplicated records.
2898496	The Live Participant Report is displaying total amounts across all events instead of the one event being reported on The Live Participant Report now shows totals for the selected TeamRaiser event instead of all events. If a participant is registered in multiple events, the report shows the participant's total for the selected event only.

 

Version 24.1.1 Release notes

March 2024t

The Luminate Online 24.1.1 release contains security updates, feature enhancements, and resolved issues. The updates are available to all customers without the need to contact Blackbaud to enable.

Product Updates

• TeamRaiser Live Event Participant Report

• Good Move Admin Tools

• Blackbaud Checkout Locale Support

• TeamRaiser Integration with Facebook Fundraising

• Administrator Help Documentation Update

 

TeamRaiser Live Event Participant Report

A new participant report provides statistics so you can see the progress of your TeamRaiser event participants in real time, including before, during, and after your event. The Live Event Participant Report provides a modern, configurable, actionable report view for your in-person event participants.

Note: Currently, only administrators with the Design and Configure TeamRaiser and Register and Manage Participants permission levels can access the Live Participant Report.

Select a participant name to open a full-page view of a participant from the live report. View fundraising details, and easily email or locate the phone number of the participant using quick links.

 

How do I view the Live Participant Report?

InFundraising, TeamRaiser, find your event and select Manage. Select the Live Participant Report tab to see the real-time status updates of your event participants.

Filter, search, or download the participant status results to quickly find the information you need.

How do I filter report data in the Live Participant Report?

To filter report data, select Columns. Select what you want to view, then select Apply changes.

See Live Event Participant Report to learn more about this configurable, actionable report view for your in-person event participants and the Live Participant Records that are also available!

 

Good Move Admin Tools

Good Move Support for Blueprint TeamRaisers

You can now enable Good Move activity tracking at the Blueprint TeamRaiser level so that all child events automatically include this option. Changes made to the Good Move App Setup section at the Blueprint level push to all child events.

When you configure Good Move on a Blueprint, you can lock or unlock sections of the Good Move options so that they cannot be changed in the child events.

How do I enable Good Move in a Blueprint TeamRaiser?

To enable Good Move on the parent Blueprint, in the Identify Blueprint TeamRaiser step, go to the Mobile App step and select Enable Mobile App.

How do I lock Good Move options in child events?

While setting up Good Move App Setup options during Blueprint configuration, use Lock toggles to lock or unlock each section to either prevent or allow edits on child events.

In child events, locked sections are visible but can't be edited, while unlocked sections are visible and editable.

Choose whether to lock or unlock the App Description, App Branding, Message Templates, and Activity-Tracking.

See Blueprint TeamRaisers: Manage Good Move App Configuration and Push Notifications for Child Events for more information.

 

Quick Start Activity Tracking with Rule Collections

Get a jump start on activity tracking rules by selecting a Rule Collection to auto-fill your event rules.

Rules define how participants earn activity points for your event. Rule Collections offer preset scoring rules to quickly get started. For example, you can choose a walking challenge where each mile is one point, or a distance challenge where each mile walked or run is one point, and every three miles biked is one point.

Rule Collections also include a Partial Credit and Individual Daily Point Limit for your event.

What Rule Collections are available?

The following collections offer a preset collection of scoring rules designed for popular event types:

• Steps Challenge

• Run, Walk, Ride (Miles)

• Run, Walk, Ride (Kilometers)

• Endurance - Marathon/Half Marathon (Miles)

• Endurance - Marathon/Half Marathon (Kilometers)

• Endurance - Cycling (Miles)

• Endurance - Cycling (Kilometers)

• Distance - All Inclusive (Miles)

• Distance - All Inclusive (Kilometers)

• Duration - All Inclusive

• Mental Health

How do I select a Rule Collection?

While editing your TeamRaiser, go to the Good Move App Setup step. In the Activity Tracking section, select Enable activity tracking. Select Rule Collection, then choose a collection.

After you select a collection, a message explains the tracking in the collection. If you decide to assign the rules to your event, the rules display in the activity rules table.

You can modify, add, or remove rules to customize your event's activity tracking. You can also reset the collection back to a default state.

See Add Activity Tracking Rules for more information.

 

Brand thumbnail and header preview in the app

In the App Branding section of the Good Move App Setup, you can now view a static preview of where the Event Header and Thumbnail images will appear in the app. This allows administrators to understand where the uploaded images appear to users in the app.

Note: The example preview does not show the actual uploaded image.

 

Good Move Notification Manager enhancements

You can now copy notifications in the Good Move Notification Manager. When copied, the date and time are not included, but the teams originally targeted continue to be targeted in the copied version.

You can also now view all details of a notification that was sent in the past.

View details and copy notifications using the icons to the right of each notification.

Learn more at Good Move Notification Manager: Create and Manage Push Notifications.

 

Blackbaud Checkout Locale Support

Blackbaud Checkout now respects Multiple Locale settings in Luminate Online for the following locales:

• en_US (English US)

• en_AU (English Australia)

• fr_CA (French Canada)

Previously, Blackbaud Checkout determined locales based on a payer’s browser settings. For more information, see Multiple Locale Support in Luminate Online Help.

Show me how locale is used in Blackbaud Checkout

 

TeamRaiser Integration with Facebook Fundraising

Following Meta's change to move from Blackbaud Merchant Services to Meta Pay, and Meta Pay to PayPal Giving Fund, we continue enhance the new integration.

Gifts made to a TeamRaiser-linked Facebook Fundraiser will now show the donation date as the day the gift was made, instead of the date of the data sync. This update will allow for easier reconciliation of reports between the systems.

Administrator Help Documentation Update

Luminate Online administrator help documentation now uses the standard Blackbaud documentation style and includes a feedback option on each page. Feedback is monitored and addressed monthly.

Please update bookmarks to use this new site.

Luminate Online administrator documentation

We will deprecate the previous administrator documentation later this year and use redirects to the link above.

 

Resolved Issues

Issues were resolved in: API | Constituent360 | Donations | Email | Good Move| Reports | System | TeamRaiser

API

Bug

Description

1731789

The getGroupMembers API method returns only 1000 members and does not support pagination to retrieve the remaining constituents The getGroupMembers API now supports pagination so that you can page through the list of constituent records to retrieve all group members. The following parameters are now supported in getGroupMembers support pagination: list_page_size, list_page_offset, and list_record_offset. See the getGroupMembers API documentation.

Constituent360

Bug	Description
1692821	On a constituent record, the postal code/zip code, state and county fields are not deleted on the first attempt In Constituent360, a constituent record is updated immediately after deleting postal/zip code, state, or country values and saving the update.
1980013	After searching for an organization with an ampersand (&) in the name, search results include unexpected organization names In Constituent360, Organizations, searching for an organization with an ampersand (&) in the name now produces expected search results.

Donations

Bug	Description
2609359	The Service Center tab is missing from a constituent's profile When the Donor Gift Self-Service Center is enabled, the Service Center tab is now visible from a constituent profile.
2704938	Donations that have no Tribute or Honor information capture a sender email in the donor_recognition_log causing issues with integrations Only donations that have an associated Tribute or Honor name will capture the sender email in the donor recognition log.
2714691	A custom constituent import can remove records that have active sustaining gifts which causes the payments to not be recorded in Luminate Online During a custom constituent import, records that have active sustaining gifts are no longer removed so that payments are recorded.
2731217, 2741845	Blackbaud Checkout in Luminate Online defaults to the locale of US to show English instead of defaulting to use the site and donation form locale Blackbaud Checkout now uses localization to respect the language of the default country for the site and donation form.
2745221	In rare situations, Blackbaud Checkout can create duplicate transactions in Luminate Online when there is only one transaction in the merchant account Blackbaud Checkout only creates one transaction after processing the gift in the merchant account.

Email

Bug	Description
2146242	Bulk emails that have invalid content because they use the S47/E47 S-Tags don't log errors properly Because the S47/E47 S-Tags are not allowed in email content, an update was made to handle errors that occur when a bulk email message contains unsupported S-Tags.
2536338	Database connections used by the BBCS Bounce Processor need to be modified for the future Updates were made to ensure continuous, reliable email processing and delivery.
2781051	In rare cases, emails do not send and return the error, "The sending of this email encountered an issue. Please re-send your message" Email Campaign messages send as expected.

Good Move

Bug	Description
2697531	The URL to download Good Move is broken in the First Good Move App Announcement Email autoresponder The First Good Move App Announcement Email autoresponder now has a working URL for the QR code: https://il3tw.app.link/8cMFdBjiQxb.
2787654	When the Download Good Move component is on the Thank You page, custom content is erased 30 minutes after it is added When the Download Good Move component is on the Thank You page, any added content or HTML continues to persist after saving.

Reports

Bug	Description
2635972	When you run the Email Performance Report by Group Report and filter with a group created from Query, the report fails with an error In Data Management, Reports, Report Writer, you can now successfully run the Email Performance Report by Group Report and filter with a group created from Query.
2717916	After the Luminate Online 23.5 release, the Total External Confirmed Gifts($) column in the Performance by Team report generated errors Although this was immediately resolved for all sites following the Luminate Online 23.5 release, an update was made in this release to permanently resolve this issue so that the Total External Confirmed Gifts($) value in the Performance by Team report generates as expected.

System

Bug	Description
2080987	Group Summary is not updated when all members are removed After removing all members of a group, the Group Summary now updates to reflect the correct number of members in the group.
2515141	BBCRM LO Integration that uses the SRForceAPI mergeConstituents does not move survey data to the master constituent records resulting in errors in BBCRM integration When the BBCRM-LO Connector merges two Luminate Online constituents using the mergeConstituents API, the USER_ID field on the SURVEY_LOG record in Luminate Online is updated to the new constituent ID.
2655516	Autoresponders that include an image are not tracked as opened unless a link is clicked in the autoresponder Autoresponders are now tracked as opened when an email is opened and images load.
2720916	Links in autoresponder emails that use a prefix of "tel:" in the URL are identified as relative links and rewritten with the domain/path causing the link to break When an autoresponder is edited to contain a link with a destination of "tel:1-513-XXX-XXXX", the link maintains the intended destination.
2784995	In MultiCenter, the Center Opt In recurring task can result in Oracle error, "ORA-01722: invalid number" In MultiCenter, the Center Opt In recurring task completes without error.

TeamRaiser

Bug	Description
2553579	TeamRaiser Participant Center settings that disable the option for participants to add links in the Rich Text Editor for Suggested Messages are not respected In TeamRaiser configuration settings, we've removed the options to enable the Rich Text Editor in a Participant Center, because content editors are enabled by default and cannot be disabled.
2561056	After a TeamRaiser registration refund, the TeamRaiser Registration Full Refund autoresponder does not display data from the S120 S-Tag When the TeamRaiser Registration Full Refund autoresponder is edited to include data pulled in via the S120 S-Tag, the expected values now display in emails sent after a full registration refund.
2645105	TeamRaiser ACH reversal/refunds are not properly removed after a system automated payment refund/delete Refunds (reversals) for an ACH payment made on a donation form that is associated with a TeamRaiser event properly update TeamRaiser gift records to correctly reflect totals.
2652575	When merging constituents with active TeamRaiser registrations, the remaining constituent is not updated for Milestones they may meet due to the merge When constituents with active TeamRaiser registrations are merged, the remaining constituent record's Milestones reflect combined accomplishments.
2652595	The National Company Team List page displays the Organization name instead of the Company name The National Company Team List page now displays the Company name instead of the Organization name.
2679144	If a session is invalidated during transaction processing, duplicate TeamRaiser Gifts with the same Transaction ID are sometimes created TeamRaiser gifts are no longer duplicated when a session is invalidated during processing.
2698252	Facebook gifts are not soft-credited to a participant, and the Transaction tab's Source column shows Blackbaud SAS Integration instead of the participant name. Attempting to soft-credit to the correct participant leads to an error Facebook gifts are soft credited to the correct participant, and the participant's name displays in the Source column in the Transaction tab.
2704072	Facebook donors have an incorrect name in the participant address book that does not match the actual donor name For Facebook donations, the donor name in the participant address book now matches the actual donor name.
2713807	Using the S42 S-Tag with invalid parameters causes system errors and returns a null (empty) response The S42 S-Tag now returns a dollar amount when an invalid or unrecognized parameter is used.
2716028	Gifts made to a Facebook Fundraiser that is integrated with TeamRaiser may not be correctly coded in Luminate Online reports, causing the creation method to show as "Offline," "Online," or "Sustaining" instead of "3" Gifts that are collected from a Facebook Fundraiser donation now show as a value of "3" to distinguish the creation method in the Transaction Details Report and other reports that include this value.
2716939	When configuring a TeamRaiser, the word, 'null,' appears at the top of the Identify TeamRaiser step The Identify TeamRaiser step of TeamRaiser configuration no longer has the word, "null," on the page.
2718383	In a TeamRaiser registration record, selecting Sort by Payment Type takes you to a Technical Difficulties page and if you select back, all gifts disappear On a TeamRaiser registration record, you can once again sort a registration record by Payment Type.
2720984	Gifts made to a Facebook Fundraiser that is integrated with TeamRaiser as well as other external donations are not capturing data for constituent milestones Although this issue was temporarily resolved for all sites, this release includes a permanent update to ensure that all external donations count toward a constituent's Milestone progress.
2730566	In Participant Center, participants are able to create a second Facebook Fundraiser while the first Facebook Fundraiser is still active causing incorrect data syncs and totals Participants are not able to have more than one active Facebook Fundraiser at a time. If a participant tries to create a second Facebook Fundraiser from the Participant Center, the following error displays in the Participant Center: "You already have an active Facebook Fundraiser. End and delete your current Facebook Fundraiser to create a new one." As a part of this update, the error code of 2767 was added to the TeamRaiser API error code reference documentation.
2754583	Gifts made to a Facebook Fundraiser that is integrated with TeamRaiser do not trigger the "Someone Made a Donation on Your Behalf" autoresponder email for participants Donations made to a Facebook Fundraiser that is integrated with TeamRaiser now trigger the "Someone Made a Donation on Your Behalf" autoresponder email to the participant.
2762306	Gifts made to a Facebook Fundraiser that is integrated with TeamRaiser do not show on National Company Events Lists National Company event list pages now show totals of all donations, including gifts made to a Facebook Fundraiser that is integrated with TeamRaiser.
2793855	Extra TeamRaiser events are created when using the Blueprint upload of a CSV that has commas in columns When using an uploaded CSV file to create TeamRaisers as Blueprint events, Luminate Online now handles commas in the DONATION_ASK_MESSAGE_TEMPLATE or EVENT_RECRUITMENT_MESSAGE_TEMPLATE columns so that the same number of events that are in the CSV file are created and message templates match exactly.
2814058	Add donation_date parameter support in facebookDonate FBDOR When using an uploaded CSV file to create TeamRaisers as Blueprint events, Luminate Online now handles commas in the DONATION_ASK_MESSAGE_TEMPLATE or EVENT_RECRUITMENT_MESSAGE_TEMPLATE columns so that the same number of events that are in the CSV file are created and message templates match exactly.

 

Version 24.0.1 Release notes

January 2024

The Luminate Online 24.0.1 release contains security updates and compliance enhancements. The updates are available to all customers without the need to contact Blackbaud to enable.

 

Product Updates

• Administrator Multi-factor Authentication (MFA) Via SMS

• California Assembly Bill 488 Compliance

 

Administrator Multi-factor Authentication (MFA) Via SMS

With this release, Luminate Online administrators will now authenticate with a verified phone number for login. This update replaces the one-time codes that were sent to administrators via email.

 

The frequency of authentication remains the same as the previous two-factor authentication email code. When the This connection is private option is selected, SMS authentication is not needed again for 30 days.

Tip: Admins on a private connection who previously authenticated location within the past 30 days may not be sent or prompted for a code after entering their phone number until the current authentication expires.

In MultiCenter environments, center admins can use the same phone number for different centers. SMS authentication is configured for each administrator for each site.

Note: This update applies only to administrators logging in to Luminate Online. The login experience for Event Managers, Company Coordinators, participants, and supporters does not change. API login behavior also does not change.

What is Multi-factor Authentication (MFA)?

Multi-factor Authentication (MFA) is an authentication method that requires you to identify yourself with two or more factors (pieces of evidence) to sign in. Main types of factors are:

• Knowledge — Something you know, such as such as a password.

• Possession — Something you have, such as a code sent to a personal device.

• Inherence — Something you are, such as facial recognition.

How do I log in to Luminate Online with MFA using SMS?

1. On the Luminate Online administrator login screen, enter your username and password.

2. Select Login.

3. Select a country from the drop-down to add the country code, then enter a mobile phone number that can receive your verification code. The number is saved to the administrator's profile record.

   

4. Select Verify. This sends a code to the number provided and also stores the number to the administrator's profile record.

5. Enter the confirmation code that was sent to your phone via SMS (text) and select Log In.

   

How do I change the phone number used for MFA?

To change the phone number used to receive confirmation codes upon login, update the number in the administrator's profile record.

1. In Luminate Online, go to Constituent360, then search for and open the administrator's record.

2. On the administrator's record, select Change MFA Phone.

   

3. Enter a new mobile phone number. Select a country from the drop-down to add the country code.

   

4. Select Update.

 

California Assembly Bill 488 Compliance

The State of California recently enacted legislation, California Assembly Bill 488 (CA AB488), which regulates online charitable fundraising in the state. The law prohibits charitable fundraising platforms, like Blackbaud, from assisting organizations not in “good standing” in California with making charitable solicitations to and receiving funds from California residents.

Note: Any U.S. registered charitable organization that operates or solicits donations in California is subject to this law. It does not impact organizations registered outside of the United States.

California aggregates data from three lists to determine whether charitable organizations are in good standing. For details of these lists, and what to do if your organization is on the list, see California Assembly Bill 488: Impact to Charitable Organizations.

Consistent with our legal obligation, beginning January 1, 2024, transactions made through Blackbaud solutions by California donors to organizations that are not in “good standing” will no longer be accepted. To comply, Luminate Online now enforces the following updates.

 

Recipient Charitable Organization Due Diligence (Part 4)

Luminate Online now prevents any transaction from a California address toward an organization that is active on one of the lists described in California Assembly Bill 488: Impact to Charitable Organizations. The restriction includes all transactions and all transaction types, including recurring, direct debit donations.

California donors, identified by zip code, are notified on the transaction page with the following message:

"California state law prohibits this transaction. Contact the organization to donate."

If a donor doesn't provide a zip code, the transaction is assumed to be from California and is prevented.

How do I identify transactions that fail so that I can take action?

If you would like to identify these failed transactions, run the Transactions Details report with Error Code selected as a report column. See the Knowledgebase article, Why did a transaction decline?

The failed transactions display with the error code, "Declined due to non-compliance with California law."

Example:

 

Information Delivery Requirements (Part 7) ​

Luminate Online now requires that donors be provided proof of a donation through a tax donation receipt. To comply, the Transaction Summary component in Donation Management was updated and is now enforced on the Thank You page.

The Transaction Summary component now includes the recipient organization name. For MultiCenter, the center name is used. Following a successful transaction, the on-screen transaction summary displays to the donor which allows them to review and print it out, if desired.

By default, every Thank You page contains a Transaction Summary. If removed, you cannot save the Thank You page until the Transaction Summary component is included. To allow for easy insert onto the page, the component is now available in the list of components that can be inserted in donor screens.

For previously-designed pages, if the Transaction Summary is not included on the donation form's Thank You page, it is automatically inserted at the bottom when the page renders.

 

Resolved Issues

No resolved issues were included in the 24.0 release.