Luminate Online Version 24 Release Notes
Tip: See also our Good Move App Changelog and Participant Center Changelog
Version 24.2.1 Release notes
May 2024
The Luminate Online 24.2.1 release contains security updates, feature enhancements, and resolved issues.
Product Updates
Link Manager - Planned for May 23
Shortly following the 24.2.1 release, you'll gain access to Link Manager, a new feature that enables you to review and manage all links in your Luminate Online site.
Being aware of all links in your Luminate Online site is useful for various reasons, especially to identify those that use
http://instead ofhttps://. The new Link Manager easily scans your entire site and organizes your links by application, object, link tag, and more.Select Library, Link Manager, then select Run Link Manager Task. The Link Manager returns a list of all internal and external links from your site, including web pages, images, videos, and CSS files. From the list, select View to see the application and object where the link is located. Select Edit to update the link.
To filter results, choose from Application Name, Link Tag, or Protocol options, then select Filter.
When you select the Run Link Manager Task button, the button becomes inactive until the task completes.
For full details, see Link Manager.
Note: Although all application links display, you must have permission rights to an application to Edit the link.
Note: MultiCenter sites must use the All Centers view to see and edit links.
This feature is planned to be enabled on May 23rd, at no additional cost, for all customers.
Good Move Activity Tracking
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?
In Fundraising, TeamRaiser, select the Good Move Notification Manager tab.
Select the Blueprints tab and locate your Blueprint TeamRaiser.
To the left of the Blueprint TeamRaiser name, select the ellipses (. . .) menu.
Select Manage notifications.
Select New notification.
Enter the Title, Body, and optional Call-To-Action URL and button labels. When done, the notification saves as a draft.
When you’re ready to copy the Blueprint notification to your child TeamRaisers, select Push Changes.
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.
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.
Live Participant Report enhancements
In April, we released the TeamRaiser Live Participant Report. With this release, we've added the following enhancements.
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.
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
To unlock an administrator account, go to Constituent360 and search for the profile.
Open the profile and select Unlock Account.
Select Unlock Account.
The account is now unlocked.
Resolved Issues
Issues were resolved in: API | Constituent360| Donations | Email | Good Move | MultiLocale | Payments| System | TeamRaiser
Bug Description 2865646
The AddGift API call does not respect Honoree fields
Honoree/Tribute data is now created and captured in the
donor_recognition_logwhen included in the AddGift API call.
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.
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.
Bug Description 2868331, 2661636 Email campaigns sometimes show a "Content Error" in the email summary and generate a duplicate email
jobIDAn update was made to prevent duplicate email
jobIDsfor Email Campaign messages.
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.
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.
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.
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.
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.
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.
2859254
After the 24.1.1 release, the S42 tag returned the value for the
dollarsparameter when an invalid parameter, such asfr_idinstead offr-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
dollarsparameter.Note: When using the S42 S-Tag to get the TeamRaiser ID, be sure to use the correct parameter of
fr-id(notfr_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.
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 or Participant Center on a desktop browser
When using a desktop browser view, the Thank You page or Participant Center now display 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.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 (Now available!)
TeamRaiser Live Event Participant Report
Available now!
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.
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.
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.
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.
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.
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.
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
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.
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
Bug Description 1731789
The
getGroupMembersAPI method returns only 1000 members and does not support pagination to retrieve the remaining constituentsThe
getGroupMembersAPI 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
getGroupMemberssupport pagination:list_page_size,list_page_offset, andlist_record_offset.See the getGroupMembers API documentation.
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.
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.
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.
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.
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.
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
mergeConstituentsAPI, 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.
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
When Rich Text Editor Available for Content is enabled for Suggested Messages, the setting to prevent participants from adding links or images into the Suggested Messages is once again respected.
When disabled, participants can no longer add images, web page links, or documents to Suggested Messages. You can find these settings when you edit a TeamRaiser, Identify TeamRaiser, Select Event Options, Related Actions, Edit Advanced Options, Define Misc Options, then clear these two options: Yes, allow participants to paste links from other web pages and Microsoft Word documents into the RTE content area and Yes, allow participants to drag and drop images from other web pages into the RTE content area.
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
2767was 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
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.
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.
On the Luminate Online administrator login screen, enter your username and password.
Select Login.
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.
Select Verify. This sends a code to the number provided and also stores the number to the administrator's profile record.
Enter the confirmation code that was sent to your phone via SMS (text) and select Log In.
To change the phone number used to receive confirmation codes upon login, update the number in the administrator's profile record.
In Luminate Online, go to Constituent360, then search for and open the administrator's record.
On the administrator's record, select Change MFA Phone.
Enter a new mobile phone number. Select a country from the drop-down to add the country code.
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.
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.