Luminate Online Version 20 Release Notes

Version 20.8.1 Release Notes

The Luminate Online 20.8.1 release contains the following resolved issues.

Resolved Issues

TeamRaiser

Bug Description

1615721

The Participant Center Address book importer fails when a contact from an email provider contains an invalid XML character

In TeamRaiser, the Participant Center address import from Gmail or Yahoo email now handles the presence of an invalid XML character so that Gmail or Yahoo contacts can successfully import to the Participant Center.

1626578

Coaching emails are missing in the Event Management Center

Event managers can once again access coaching emails in the Event Management Center.

 

Version 20.8 Release Notes

The Luminate Online 20.8 release contains the following product updates and resolved issues.

Product Updates

The 20.8 release contains the following enhancements, including suggestions from the Luminate Ideas Portal:

In Testing: New Fraud Management tool

Coming soon! Easily manage constituents created by fraudulent transactions in the new Fraud Management center.

When a fraudulent transaction creates a user record, the record is tagged as suspicious. You can remove or resolve them one by one, or in bulk.

See Fraud Management.

reCAPTCHA v3

Now Available!reCAPTCHA v3, the latest version of the Google service that protects you against abusive form submissions by spam bots, is now available in Luminate Online. reCAPTCHA v3 is available everywhere in Luminate Online that CAPTCHA exists today.

reCAPTCHA v3 is invisible to users. Users who fill out your form will no longer see the "I am not a robot" checkbox or picture selection of previous CAPTCHA versions. Instead, an analysis engine detects bot behavior to prevent malicious software from abusive activity.

To use reCAPTCHA v3:

  1. Contact Blackbaud Support to enable reCAPTCHA v3 in the SEC_CAPTCHA_VERSIONSite Option.

  2. Add CAPTCHA questions and fields to any of these Luminate Online forms: Survey, Donations, eCards, Tell-A-Friend, TeamRaiser Registration, TeamRaiser Personal Page Blogs, Personal Fundraising Guest Book, Advocacy Alerts, and Calendar Events.

Import address book to a TeamRaiser Participant Center

In TeamRaiser, participants can import their personal contacts from Google Gmail, Yahoo Mail, or a CSV file directly into a Participant Center. After import, participants can send mass emails or group contacts directly from their Personal Page.

To import contacts into a Participant Center, participants select Import Contacts in theContacts section, then choose to import from Gmail, Yahoo, or a CSV file.

Note: For Yahoo imports on sites that use a custom secure domain and custom Yahoo app, see Knowledgebase article 194853.

 

Inline TeamRaiser Personal, Team, and Company Page editing for existing events

On existing TeamRaiser events, participants can directly edit their Personal Page, Team Page, or Company Page when the inline layout is set on the default page. The 20.5 release offered this same feature for new events.

  1. Go to Fundraising, TeamRaiser, and open your TeamRaiser.

  2. In the Customize Pages step, click the link to either the Default Personal Page, Default Company Page, or Default Team Page.

  3. In the Layout option, choose Inline Page Editing from the drop-down options.

    Click Save or Finish. The pages now include options for direct edits to content.

 

Date clauses in Query for birthdays, anniversaries, and more

Engage with your supporters on important dates with new date clauses in Query.

You can query for the day or month of any date field in a constituent record to make a recurring birthday greeting, thank donors on the anniversary of their first gift, or more!

 

Automatically assign donors to a group from a donation form

Automatically group your supporters who've donated to a specific donation form. Add these donors to either a new group or an existing group.

To automatically assign donors to a new or existing group, choose Select on the Form Group option on the Identify Donation Form step. On the popup window, create a new group or select an existing group. Donation form supporters are assigned to the designated group.

Tip: Giving a refund does not remove the donor from the group.

This functionality does not impact existing functionality with campaign groups.

 

Delayed Self Pledge reports now include one-step (new-style) Delayed Self Pledge transactions

In Report Writer, theDelayed Self Pledge and Delayed Self Pledge Failures reports now include results from one-step (new-style) Delayed Self Pledge transactions in addition to the two-step (older-style) Delayed Self Pledge transactions.

The reports indicate whether a transaction is a gift or registration, and whether it is one-step (new-style) or two-step (older-style).

  • Participation Type Name

  • DSP Style

  • Include Registration Fee in Fundraising Totals

  • DSP Pledge Amount Due (confirmed gifts only)

  • DSP Pledge Amount Due (confirmed and unconfirmed gifts)

  • DSP Pledge Amount Due (confirmed and recurring gifts)

  • DSP Pledge Amount Due (confirmed, unconfirmed, and recurring gifts)

 

Adobe Flash removal

Adobe Flash was removed throughout Luminate Online and Luminate Online APIs due to the upcoming deprecation of Adobe Flash on December 31st, 2020.

 

Security updates

  • File type enforcement for Document Library uploads: The Document Library no longer allows the upload of file types: .swf, .exe, and .bin.

    Note: Previously-uploaded file types of .swf, .exe, or .bin will continue to work.

  • Cross Site Request Forgery (CSRF) Protection Enhancements:CSRF protection enhancements were implemented across Luminate Online.

Resolved Issues

API

Bug Description

1488127

In a multi-locale site, calling the getParticipationTypes method with a non-English locale specified returns registration question information in English (LO-6369)

On multi-locale site, when the getParticipationTypes API method includes the s_locale parameter to specify a non-English language, the API returns all information in the specified locale.

1488212

In email donations, SecurePayAPI overwrites the source type and source code for transactions processed using Blackbaud Checkout (LO-6500)

For Luminate Online email donations processed using Blackbaud Checkout, the source type and source code are no longer overwritten with the generic “SecurePayAPI” value.

Email

Bug Description

1488251

In Email Express, choosing Calculate Audience Size always calculates a size of 0, even though intended recipients do receive emails (LO-6943)

Audience calculation in Email Express now correctly shows the number of recipients.

This issue only occurred for the number displayed. Targeted recipients did receive emails.

Events

Bug Description

1540760

Survey Captcha question response should not be visible in modern Calendar ticketed event

CAPTCHA responses no longer display on any processing pages for a ticketed event.

Integration

Receipts

Bug Description

1532790

After the 20.5 release receipt updates, the "Regenerate Receipt" option to create a new receipt with a new tax receipt number is not longer available

In addition to the 20.5 enhancements that allow you to resend an original receipt without creating a new tax receipt number, you can now once again choose the Regenerate Receipt option when you want to void the original receipt and create a new tax receipt number.

In summary, receipt options now include:

  • View/Resend Receipt - resends the original receipt retaining the tax receipt ID number

  • Regenerate Receipt - voids the original receipt and creates a new receipt with a new tax receipt ID number

You'll see the options in Receipt Manager or on the Transactions tab of a constituent record in Constituent360.

Reports

Bug Description

1487840

In Report Writer, the Transaction Details Report doesn't show eCommerce transaction source codes

Report Writer's Transaction Details Report now includes eCommerce transactions source codes so that you no longer need to run a separate report in the eCommerce module to get the transaction data.

To include eCommerce source codes in the Transaction Details Report:

  1. Create and publish an eCommerce store.

  2. When adding the link to your eCommerce store on your website, either use the default source codes for eCommerce, or set s_src= variable to a source code of your choosing as described in Source Codes.

  3. Go to Reports, Report Writer, Create a New Report, Transactions, Transaction Details report.

  4. Under Miscellaneous Information, Interaction Source column options, choose Source Code Text and Source Code Type.

1488205

Sustaining gifts that process through Blackbaud MobilePay or Blackbaud Checkout stop displaying in the Donations by Transaction report on sites that use Blackbaud Credit Card Updater (LO-6279

Sustaining gifts that process through Blackbaud MobilePay or Blackbaud Checkout now always display in the Donations by Transaction report for sites that use Blackbaud Credit Card Updater.

TeamRaiser

Bug Description

1488416

In Participant Center, after an initial successful import of Gmail contacts, subsequent attempts to reimport Gmail contacts causes an error (LO-6784)

In Participant Center, you can now use the Google Contact import to successfully reimport Gmail contacts more than once.

1497692

Following the 20.5 release, participant's information edits don't save when Company is not included

You can once again edit a participant's information without error even when Company is not included.

1497707

The Fundraising Goal is set even when fundraising is disabled on the Participation Type (LO-6351)

In TeamRaiser, when Fundraising is disabled on the Participation Type, the fundraising goal and milestones no longer display to registrants and donors.

1512940

In Participant Center 3, date format registration question responses truncate the list of questions

In Participant Center 3, date question responses no longer cause a truncation or omission to the following questions.

1533680

Following the 20.5 release, changing a participant's registration type causes a Technical Difficulties error

You can once again update a participant's registration type without error.

 

Version 20.5 Release Notes

The Luminate Online 20.5 release contains the following Product Updates and Resolved Issues.

Product Updates

Advocacy update

To prevent constituent data from being unintentionally overwritten, newly-created Advocacy Action Alerts no longer include multiple responses by default. When multiple responses are allowed, contact fields or custom questions that a respondent enters overwrites previous entries on the constituent profile.

Existing alerts are not impacted.

You'll see this change when creating new alerts under Advocacy, Action Alerts, Advanced Options, step 7, Multiple Response: Yes, allow multiple responses. By default, the option is no longer selected.

API update: Get notified of large additional gifts for TeamRaiser registrations

When processing free TeamRaiser registrations ($0 participation type), you can now send notifications to designated recipients of registrants who add a large additional gift that meets the "campaign large gift" amount.

This enhancement is available through the processRegistration API method and applies to both the direct use of the API method and the administrator TeamRaiser configuration.

To send large additional gift notifications, configure the recipients and large gift threshold in either TeamRaiser or Site Options:

  • Enable in TeamRaiser: In Fundraising, Donation Management, click Edit next to the Donation Campaign. In step 3. Specify Groups and Notifications, check the box for Yes, gifts greater than or equal to the amount specified below are to be treated uniquely. Enter a value in the Large Gift Amount field and email addresses in the Large Gift Notification List field. Save the changes.

    --OR--

  • Enable in Site Options: Go to Site Options and set the gift amount and email addresses in the DON_NOTIF_LARGE_GIFT_ADDRESSES and DON_NOTIF_LARGE_GIFT_AMT fields, then Save.

API update: Secondary API Key

Administrators can now have two, valid API keys to enable API rotations to occur without breaking existing functionality. A secondary key is helpful if you want to allow a third-party to access your APIs. You can revoke the API access at any time without disruption to your primary key.

The secondary key is optional, and both API keys are accepted as valid.

  1. Go to Setup, Site Options and click the Open API Configuration tab.

  2. Next to Configure API Keys, click Edit API Keys.

  3. In the Secondary API Key field, enter any value. The field accepts the same values as the primary Luminate Online API Key.

  4. Click Save.

Beta: New Luminate REST API documentation site

We're excited to announce the initial publication of our new Luminate Online REST API documentation site, which is currently in Beta.

https://developer.blackbaud.com/lo-api/

We're continually updating the site. Additional information, including SOAP API information for Luminate Web Services, is coming soon.

Custom interactions populate Engagement Factors

Custom Interaction Types can now populate and give weight to Engagement Factors. This is useful when you want to calculate field values based on interactions that aren't automatically included with Luminate Online.

You'll see the new option to select a custom Interaction Type when creating a Web Site Engagement Segmentation Task.

Increased fraud protection through enhanced Digital Resolve integration

We've enhanced our external fraud protection to prevent carding runs through our integration with Digital Resolve by sending additional information for CVV and donation type values.

Increased fraud protection through enhanced velocity

For increased fraud protection, the Luminate Online velocity-based fraud (carding) prevention system now detects and blocks billing address patterns to block fraudulent transactions before they pass through a payment gateway.

Easily view links to images and documents in Library

Direct links to images and documents in the Image Library and Document Library are now easy to copy and view.

To find the URL, in Library, go to Image Library or Document Library. Locate your image or document, and click Copy Image URL or Copy Document URL.

Improved locale support in the Message Catalog

Constituent-facing field titles and descriptions that are customized in the Message Catalog in a supported non-English language now display in the locale specified in the user's browser for Multiple Locale and Multiple Domain sites.

Resend original PDF gift receipts

As requested in the Luminate Ideas portal, site administrators and Event Coordinators can now easily resend a receipt without regenerating a new tax receipt number.

You'll see this option in either Fundraising, Transactions, or on the Transactions tab of a constituent profile. Choose View/Send Receipt.

Note: If you do not see this update, contact Blackbaud Support.

When you click View/Send Receipt, you'll either:

  • View/Download the PDF receipt to download to email the receipt as an attachment in any email program

    --OR--

  • Send By Email to use the built-in email process to email the receipt to the email address of the record of the constituent. When sending, you can type a note in the field.

Note: Administrators and event coordinators must have permissions to manage transactions to use View/Send Receipt.

Newly-created PageBuilder pages default to secure

Beginning with this release, new PageBuilder pages are secure by default.

You'll see this update when you go to Content, PageBuilder, click Create a New Page, and scroll to the Page Properties step.

Inline TeamRaiser Personal, Team, and Company Page editing

For all new TeamRaiser events, participants can directly edit their Personal Page, Team Page, or Company Page when the inline layout is configured for the default page.

  1. Go to Fundraising, TeamRaiser, and click Create a TeamRaiser.

  2. In the Customize Pages step, click the link to either the Default Personal Page, Default Company Page, or Default Team Page.

  3. In the Layout option, choose Inline Page Editing from the drop-down options.

    Continue creating the default page, then click Save or Finish. The pages will include the edit options for direct edits to content.

Resolved Issues

Advocacy

Bug Description

LO-2132

In Vote Center, asterisks that indicate when an official is "Ineligible to vote" display next to officials who are eligible to vote

In Vote Center, the Vote Info and Legislator Scorecard pages display the "ineligible to vote" asterisks next to officials only when officials are ineligible to vote.

Note: In some cases, such as when a representative is promoted in the middle of the legislative year, asterisks display next to the official's name because no previous votes are registered for the official in that new role.

Calendar Events

Bug Description

LO-6281

When purchasing a paid ticket for a ticketed calendar event, the final question is missing

When purchasing a paid ticket for a ticketed calendar event, the final question in the list is included on the ticketing page and summary.

Content Editor (WYSIWYG)

Bug Description

LO-6219

On Microsoft Internet Explorer version 11, using the Content Editor (WYSIWYG) does not display content for pop-ups

On Microsoft Internet Explorer, version 11, the Content Editor (WYSIWYG) now:

  • Displays an image upload properly in a pop-up so you can add an image to the editor

  • Displays content when adding a component, conditional or other that opens a pop-up

  • Displays content in fields that lead to pop-ups

LO-6368

When editing email content, the Content Editor (WYSIWIG) adds extra paragraph tags and spacing

In Email, the Content Editor (WYSIWYG) no longer adds extra paragraph tags while editing.

LO-7149

"Insert as plain text" button on the Content Editor (WYSIWYG) toolbar is turning itself off after each use

In the Content Editor (WYSIWYG) toolbar, the plain text button remains available after use.

eCommerce

Bug Description

LO-6071

Sometimes, constituents who are not logged in and are trying to purchase $0 eCommerce product see a Technical Difficulties error

Constituents who are not logged in can now successfully purchase a $0 eCommerce product without seeing a Technical Difficulties error.

Email

Bug Description

LO-3966

Email filter summary description is incorrect

When on the email delivery schedule summary page, the delivery option and delivery filter explanations for removing invalid recipients were updated.

Delivery filter

Before

Do not have the Accept email box unchecked or Deceased recorded in their profile, prior email hard bounces, an inactive contact record, or other problems with their contact record information (such as an invalid email address)

After

Do not have the Accept email box selected, a profile marked Deceased, previous hard-bounced emails, or a contact record that is inactive or has other problems (such as invalid email address)

 

Delivery Options

Before

After applying the selected delivery options, this message will be sent

After

After applying the selected delivery options, this message will not be sent

Reports

Bug Description

LO-2884

Including the "Staff Name" field in the TeamRaiser Registration report causes the report to fail occasionally with the error, "There was an error retrieving the results"

Including the Staff Name field in the TeamRaiser Registration report no longer causes an error during report generation.

Surveys

Bug Description

LO-4693

When managing the Survey Question Response group in Surveys, clicking the View Filters link displays the error, "Error: javascript:void(0) when attempting to View Filter for survey response group"

When working in Surveys and managing the Survey Question Response group, the View Filters link displays the group filter parameters as expected.

System

Bug Description

LO-1940

On Multiple Locale sites, after customizing the Constituent Profile (User Update), a constituent who views that page in another locale only sees username and email address in that locale

On Multiple Locale-enabled sites, after customizing the Constituent Profile (User Update), a constituent who views that page in another locale now sees all fields in the correct locale.

LO-5504

After updating field labels and text in the Message Catalog, registrants do not see the updated text

Custom field text that is entered in the Message Catalog for event registration fields now displays to event registrants.

LO-6224

When using a mobile phone or tablet to complete a form, users have issues passing CAPTCHA because the device automatically capitalizes the first letter

When filling out a form on a mobile device, the device's auto-correct, auto-captialize, and spellcheck no longer alter a user's input to a CAPTCHA challenge.

LO-6633

Admin gets TD error when trying to login after lockout period has expired

After becoming locked out of Luminate Online due to an excess of incorrect login attempts, administrators no longer see an error when attempting to log in after the lockout duration expires.

TeamRaiser

Bug Description

LO-3085

On a National Company page, the Top Events list displays inconsistent results

On the national company page, the Top Events list now displays consistent results of events that contain teams or participants that are associated with the national company.

LO-3197

When updating participant registration information in the administrator interface, Team Captain questions display on an offline TeamRaiser registration form for non-Team Captain registrants

On offline registration forms, Team Captain questions only display when the Make the participant the captain of a new team or Make the participant the captain of the returning team options are selected.

LO-6272

In the Participant Center, participants see suggested messages that were intended for Team Captains

In a Participant Center's Email, Recruiting section, only Team Captains see messages that are marked with the Suggested Message Type of Recruit Team Members.

LO-6374

Duplicate local companies are created when there is a participant in the system and the registration information is edited to make the participant the company coordinator

When editing a participant registration to designate the participant as a company coordinator, a duplicate local company is no longer created.

LO-6852

In Participant Center 3, adding an offline gift and then selecting the "Yes, display amount of this gift" option, the offline gift doesn't display on the Personal Page

When adding an offline gift in the Participant Center, selecting the Yes, display amount of this gift option now displays the gift on the personal page as expected.

LO-6872

When Participant Center 3 isn't embedded in a PageBuilder page, and the event name contains an ampersand (&) or other restricted HTML character (such as ', ", <, or >), the special characters display as HTML code

Ampersands and restricted HTML characters (such as ', ", <, or >) now display properly in a TeamRaiser event name for a Participant Center that is not embedded in a PageBuilder page.

LO-6873

In Participant Center 3, the "Edit Team Name" button also submits the "Team Captain Message" form, and when the updated Team Name contains a special character, the following characters are ignored

  • When a team captain updates the Team Name, the Team Captain Message no longer automatically submits automatically as well, but only submits when selecting Save after a message update.

  • When a team captain updates the Team Name to include special characters such as "&" or spaces, the special characters display properly and the remaining characters are no longer ignored.

Version 20.3.2 Release Notes

Product Updates

Security improvements

We've added additional security enhancements.

Resolved Issues

eCommerce

Bug Description

LO-6726

Previewing or viewing an eCard generates a "You are not currently logged in" or "Page Not Found" error

eCards can now be previewed or viewed in a browser without error.

Participant Center

Bug Description

LO-6659

Team search results in Participant Center 3 can go below the footer making those results inaccessible in a PageBuilder page

When Participant Center 3 is embedded in a PageBuilder page that has a Page Wrapper, users who search Teams are now able to see all Team search results within the iFrame.

 

Version 20.3 Release Notes

Product Updates

Available now! Participant Center 3

A new and fully-redesigned Participant Center 3.x, also called PC3, offers many new enhancements, including responsive behavior to mobile phone and tablet views! Participant Center 3 makes it easy for you and your participants to create a customized page.

See Participant Center 3.

Available now! Offer direct debit payments with Blackbaud Merchant Services

Donors can now pay for one-time or recurring gifts with direct debit on donation forms that use a Blackbaud Merchant Services (BBMS) gateway. Direct debit (ACH) payments are currently available in the United States.

See our help documentation to get started to accept direct debit payments through BBMS.

Blackbaud Checkout Update

We've updated Blackbaud Checkout to the latest version to provide improved performance and readiness to support additional wallet types.

Security improvements

  • Surveys - Newly created surveys are now set to secure by default.

API improvements

  • In Constituent API, the Gender field for the listUserFields and listUserFieldChoices methods changed from ENUMERATION to STRING type to accommodate other possible gender options. Custom Gender values returned by the listUserFields and listUserFieldChoices methods are now accepted when using the create, createOrUpdate, and update methods of the Constituent API.

    The following Constituent API methods accept or supply the updated gender field provided listUserFieldsand listUserFieldChoicesAPI calls:

    • create

    • createOrUpdate

    • update

    • getUser

  • In TeamRaiser API, the getCompanyPageInfo method was updated to request an optional company_id parameter instead of the cons_id. This is helpful for companies that might not have a company coordinator and is similar to the getCompanyPhoto method.

Resolved Issues

Issues were resolved in: API | Calendar Events | Constituents | Documentation | Donations | eCommerce | S-Tags | System | TeamRaiser

API

Bug Description

LO-4845

The TeamRaiser API method, ValidateDiscount, works correctly for initial registration but returns a generic error, such as "Unable to process request" after visiting another registration page, such as secondary registration

After applying a discount code on an initial registration, the TeamRaiser API method, ValidateDiscount, no longer displays an error when visiting another registration page such as a secondary registration.

LO-5350

The offlineOrganizationGift API method is not documented

The offlineOrganizationGift API method is now published.

LO-5889

The TeamRaiser API previewMessage method renders the powered_by_convio.gif link on a non-secure server that causes a browser warning when the Participant Center renders on the secure server

When previewing an email in the Participant Center, the Powered by Convio image link is now served from a secure server so that a mixed-content warning no longer displays in the browser.

LO-6077

The CRConsAPI.create method creates a constituent with "accepts_email=true" when no "accepts_email" flag is included in the API call

When using the CRConsAPI.create API method to add a constituent, Luminate Online now checks whether the request call includes the email.accepts_email parameter. If the parameter is not included, the "accepts email" flag is set to FALSE so as not to opt in the new constituent without express approval.

Tip: You can retrieve the full list of CRConsAPI.create parameters by calling the CRConsAPI.listUserFields service. Because database fields can vary by site, access the current list of available fields and parameters through the API call.

LO-6215

When making a getParticipants call that includes the "event_type" parameter, the "amountRaised" response is always null

Making a getParticipants call that includes the event_type parameter returns an accurate amountRaised result.

LO-6353

In eCards, post calls allow account creation

Spam prevention improvements no longer allow the creation of accounts through the eCard module.

Calendar Events

Bug Description

LO-6352

In Calendar Events, clicking Register redirects to the Event Calendar Page

When creating a Multi-Part Calendar Event, the Register button on the right of the screen now opens the Registration page instead of the Event Calendar Page.

Constituents

Bug Description

LO-6330

Affiliate administrators get a Technical Difficulties error when trying to access a constituent record in Constituent360

Affiliate administrators in Multi-Affiliate sites that have the CONS_CATEGORIZATION_ENABLEDSite Option set to FORCED can now access applicable constituent records.

Documentation

Bug Description

LO-5268

Luminate Online documentation does not explain the TeamRaiser gift upload matching logic

A new help topic describes the logic used to match constituent records during a batch upload of TeamRaiser gifts:

TeamRaiser Batch Gift Matching Logic

LO-6214

Clarify the priority of default source code, vs URL source code

The following update was added to the Source Code help topic:

Which source code is used when a form has a default source code and the donor URL also contains a source code?

When a Luminate Online form uses a default source code but a donor URL also contains a source code, the URL source code is used.

So, when a constituent already has a source code stored in their session from some other part of your site, that source code is taken as the source code for the form instead of the form source code. Default source codes are used only when the user session doesn't already have a source code.

To enforce the use of a specific source code on a form, build the source code into the URL. For example, "donate2020" is the enforced source code in the URL below.

Example: http://my.blackbaud.site.org/site/Donation2?df_id=1035&mfc_pref=T&1035.donation=form1&s_src=donate2020

Donations

Bug Description

LO-5993

Blackbaud Checkout allows the selection of Visa Checkout for recurring gifts even though wallet types only support one-time gifts

Visa Checkout, the wallet solution from Visa, no longer supports recurring gifts. Blackbaud Checkout was updated so Visa Checkout no longer displays as an option for recurring gifts.

LO-6320

When a user saves credit card information in their Microsoft Edge or Google Chrome browser, the CVV field on a donation form autofills with the saved "First Name"

Google Chrome and Microsoft Edge browser users with saved credit card information (including a first name) in their browser no longer have the CVV field auto-populated with the saved first name.

eCommerce

Bug Description

LO-6097

When checking out of an eCommerce store on a site that has the ENFORCE_UNIQUE_EMAIL Site Option set to TRUE, a shipping address entered during checkout is overwritten by the address on the matching constituent record

When a constituent goes through the eCommerce checkout and inputs an address that is different from a matched constituent record, the system now handles the address values in the following ways:

  • Any address entered during checkout is no longer overwritten by a previous address from a matched constituent record

  • A new address can overwrite the address on a matched constituent record when the ECOMMERCE_UPDATE_CONS_ADDRESS_WHEN_LOGGED_IN or ECOMMERCE_UPDATE_CONS_ADDRESS_WHEN_NOT_LOGGED_INSite Options are set to TRUE.

  • When ECOMMERCE_UPDATE_CONS_ADDRESS_WHEN_LOGGED_IN is set to TRUE, logged-in users see their existing address from their constituent record.

  • When ECOMMERCE_UPDATE_CONS_ADDRESS_WHEN_NOT_LOGGED_IN is set to TRUE, logged-in users see their existing address from their constituent record.

  • Address updates occur only after a transaction successfully completes.

  • Both the ECOMMERCE_UPDATE_CONS_ADDRESS_WHEN_LOGGED_IN or ECOMMERCE_UPDATE_CONS_ADDRESS_WHEN_NOT_LOGGED_INSite Options default to FALSE. Contact Blackbaud to set the values to TRUE.

S-Tags

Bug Description

LO-6140

On a national company page, a Top Events list created by the S345 S-Tag can display inconsistent results, such as listing companies that aren't associated with the TeamRaiser ID

The S345 S-Tag now only displays companies that are associated with the TeamRaiser ID that is pulled in by the S-tag and events that are associated with the company.

LO-6355

On a Thank You page associated with a TeamRaiser event, the [[S120:dc:sponsoreeName]] tag displays the TeamRaiser name even if the gift was to a participant or team

On a donation form's Thank You page that is associated with a TeamRaiser event, the S120:dc:sponsoreeName S-Tag now renders the participant name when the gift is credited to a participant, the team name when the gift is credited towards a team, and the event name when the gift is credited toward an event.

System

Bug Description

LO-6122

Email cleaning prevents valid domains from being usable

On sites with email cleaning enabled (Site Option CONS_EMAIL_CLEANING_ENABLED), domains such as ms.com and cs.com no longer change from autocorrect and are recognized as valid domains.

TeamRaiser

Bug Description

LO-4843

Delayed Self-Pledge registrations display on the Delayed Self-Pledge tab for the wrong event

TeamRaiser events that do not offer Delayed Self-Pledge participation types no longer display Delayed Self-Pledges from other TeamRaiser events that do offer Delayed Self-Pledge.

In addition, the Process all button at the top of the Delayed Self-Pledge page now reflects an accurate count and amount for the Delayed Self-Pledge amounts shown in the list.

LO-5171

Returning a team and assigning the team to a company creates a duplicate organization

Returning a TeamRaiser team and assigning the team to a company no longer creates a duplicate organization.

LO-5354

The S36 S-Tag 'top_gifts_list' parameter doesn't order results by the amount or list size limitations when set to do so

The S36 S-Tag top_gifts_list parameter type now lists size limitations and orders returned results by the amount when set to do so.

LO-6660

Updating a TeamRaiser event end date does not update the Facebook Fundraiser end date

Now, when a TeamRaiser event date is updated, the Facebook Fundraiser end date automatically updates as well.

Version 20.1.2 Release Notes

Product Update

To address Google Chrome cookie changes, the loginTest method was updated to support new Chrome cookie handling when called from JavaScript via HTTPS. Due to Chrome cookie changes, calling loginTest from JavaScript via HTTP on a chromium-based browser, such as Chrome, no longer works.

Action required for API developers: API developers should update their loginTest request to point to a secure channel.

Resolved Issue

Bug Description

LO-6296

After the Luminate Online 20.1 release, some email deliveries are getting stuck and do not deliver

We've resolved the issue causing email deliveries to not send. Email deliveries now deliver as expected.

Version 20.1 Release Notes

Tip: Have you heard about the new integration of Blackbaud Luminate Online with Phone2Action? Check out what it can do to help take your advocacy mission to the next level!

Product Updates

In Delayed Self-Pledge, remove registration fee from fundraising total

In TeamRaiser, the Delayed Self-Pledge Participant Type now offers the option to include or exclude registration fees in a participant's fundraising total. You'll select this option when you Create or Edit a Participation Type for a TeamRaiser Event.

By default, when Delayed Self-Pledge is selected for a participation type, the registration fees are included in the fundraising goal. Update this option if you want to separate registration fees from the fundraising total.

Note: Do not change this setting after a TeamRaiser event has registrants since it can change the amount the participant owes.

Learn more about Delayed Self-Pledge in the TeamRaiser Delayed Self-Pledge documentation.

Search Donation Forms, TeamRaisers, and Groups by ID

Search for your Donation Form, TeamRaiser, or Group by ID. Simply type the ID number in the search box to quickly locate the Donation Form, TeamRaiser, or Group in the list.

Live URL links in the Administrator interface

As a Luminate Online administrator, you can now click the URL of the starting page instead of copying and pasting it into the browser. You'll see these links when you finish creating a TeamRaiser, Advocacy Alert, Survey, PageBuilder page, Donation Form, Calendar Event, eCommerce store, or Personal Fundraising fund.

Content Editor (WYSIWYG) updates

In this release, we've updated all Content Editors (WYSIWYG) to ensure browser compatibility and to provide you a consistent experience. Luminate Online Content Editors now use the same, updated version in Administrator pages, Email Express, TeamRaiser Event Management Center, and on the user side of Participant Center 2.

Security improvements

  • We've added additional security enhancements.

"Powered by Blackbaud" image update in emails

The "Powered by Blackbaud" image that displays in some emails sent by Luminate Online now opens to Blackbaud.com.

Administrator password requirement updates

Administrator passwords must meet new requirements on their next reset. The new guidelines require 8 characters or more, including 3 of either a capital letter, lowercase letter, number or valid special character. When guidelines are not met, a message displays. See Administrator Passwords.

Coming soon! Participant Center 3

A new and fully-redesigned Participant Center 3.x, also called PC3, offers many new enhancements, including responsive behavior to mobile phone and tablet views! Participant Center 3 makes it easy for you and your participants to create a customized page.

See Participant Center 3.

Coming soon!Offer direct debit payments on donation forms

Donors can now pay for one-time or recurring gifts with direct debit on donation forms that use a Blackbaud Merchant Services (BBMS) gateway. Direct debit (ACH) payments are currently available in the United States.

To offer direct debit payment on your donation forms:

  1. Set the Bank ACH Account to your Blackbaud Merchant Services gateway.

    1. Go to Setup, Payment Capabilities.

      Note: Access to Setup, Payment Capabilities is available to administrators who use BBMS and have the Merchant Account Self Provisioning permission. If you don't see this option and feel you should, contact Blackbaud Support. See Payment Capabilities for more information.

    2. On the Merchant Accounts page, Edit your merchant account.

    3. In the Bank (ACH) Account option, select your Blackbaud Merchant Services gateway.

    4. Click Finish.

  2. Set the Blackbaud Merchant Services gateway on the donation campaign.

    1. Go to Fundraising, Donation Management.

    2. Edit the donation campaign.

    3. On the Choose Financial Options page, select your Blackbaud Merchant Services gateway in the Merchant Account option.

    Donation forms associated with the donation campaign now display the Checking Account option in the payment section.

Resolved Issues

Issues were resolved in: API | Calendar Events | Email | Payments | Raiser's Edge Integration | Reports | System | TeamRaiser

API

Bug Description

LO-5890

The Address Book API "addAddressBookContact" allows duplicate contacts with same email address but different names

The Address Book API addAddressBookContact method now checks existing contact records to identify matching email addresses. When a match is found, a message about the existing record displays.

LO-5892

In Participant Center 3, the TeamRaiser API "updateShortcut" method silently strips out HTML tags and fails to validate minimum length of the URL

In Participant Center 3, participants can use HTML tags when creating a URL Shortcut to their personal page and have the minimum length requirements validated.

LO-5921

The TeamRaiser API "addDraft" method documentation does not include "prepend_salutation" parameter

The prepend_salutation parameter is now included in the addDraft API documentation. Use this parameter to personalize salutations in Tell-A-Friend emails from Participant Center.

LO-5936

The TeamRaiser API "updateTeamraiserAddressBookContact" method returns a success response instead of an error when required fields are blank

When a required email address is blank when adding a new Address Book contact, the TeamRaiser API updateTeamraiserAddressBookContact now returns an error message.

The email address field now includes an asterisk to indicate that it is a required field.

The method does not require first and last name.

LO-5940

The TeamRaiser API "getSuggestedMessage" method does not return the "prependsalutation" parameter

When retrieving a suggested message, such as a participant-saved template, the prependsalutation parameter is now included in the response of the TeamRaiser API getSuggestedMessage method.

This parameter corresponds to the "Include a personalized greeting?" option that a participant chooses before saving a template as a draft using the TeamRaiser API addDraft method.

LO-5968

TeamRaiser API "getSuggestedMessage" method does not return the setting for whether the Subject and Message is editable

The TeamRaiser API getSuggestedMessage method now has two new parameters: subjectReadOnly and messageBodyReadOnly.

Administrators creating suggested messages in TeamRaiser events can use these parameters to specify that the Subject and Message content of a suggested message should be read-only (not editable by the participant).

LO-5996

The TeamRaiser API "getTeamRoster" method does not return the totalNumberResults parameter results in the response

The TeamRaiser API getTeamRoster method now returns the value for totalNumberResults in the call response.

Because the getTeamRoster method allows pagination parameters, viewing the totalNumberResults response is useful to determine whether to display pagination or whether all results were retrieved when pagination is used.

Calendar Events

Bug Description

LO-6001

Survey Questions in French render in English on Billing Page for Calendar Events

On a multilocale site, the Calendar Event's Billing Page and page autoresponders reflect the language specified for that locale.

Email

Bug Description

LO-1550, 2753

When viewing the Delivery Statistics, the Initial Group Count is exactly double the Target Group Total

In email delivery statistics, the Initial Group Count number no longer doubles certain metrics gathered pre-delivery.

Note: The prior calculation for this metric did not impact email delivery.

LO-5375

The email delivery summary can display an incorrect "Group overlaps" number

In the Audience Calculations section of email delivery statistics, the Group Overlaps number no longer combines metrics gathered pre-delivery with metrics gathered during the audience calculation step. Now, the metric is reset and incremented only during delivery to determine the correct overlap number.

Note: The prior calculation for this metric did not impact email delivery.

Payments

Bug Description

LO-6213

Blackbaud Checkout displays a message for one-time gifts that suggests the gift is recurring

When using Blackbaud Checkout with Luminate Online, donors making a one-time gift no longer see the following message:

"By completing this step, you authorize the storing of this card account for future, agreed upon payments."

Recurring gift donors will continue to see this message.

Raiser's Edge Integration

Bug Description

LO-1979

Multiple contact record entries are created when a constituent opts out of email. Entries show the message, "Cannot find transaction for id=0"

The Raiser's Edge - Luminate Online Integration no longer creates repeating entries on a contact record after a constituent opts out of email.

Reports

Bug Description

LO-5618

When running a syndicated report from one center, non-TeamRaiser gifts are excluded from the results when the "Public Event Name" column is included in the report

By default, syndicated reports that are run from one center and include the Public Event Name column will continue to only display TeamRaiser transaction types.

To provide the option to include non-TeamRaiser transaction types in syndicated reports, a new Site Option, SDP_SYNDICATED_REPORT_VIEW_ENABLED, is available. Set this Site Option to TRUE to return all transaction types in the report.

The new Site Option that is now available is:

SDP_SYNDICATED_REPORT_VIEW_ENABLED - When TRUE, syndicated report results run and viewed within a particular center display TeamRaiser transactions for all centers as well as all transactions that are not processed and associated with a center. When set to FALSE, syndicated report results viewed and run in a center display TeamRaiser transactions from that center and will filter out any non-TeamRaiser transactions. By default, this is FALSE.

System

Bug Description

LO-3976

Inactivity timeouts for Luminate Online administrators sometimes do not occur

Luminate Online administrators are logged out after 15 minutes of inactivity.

TeamRaiser

Bug Description

LO-1799

TeamRaiser returns an unfriendly error when registering for an event if the required Country field is left blank

When registering for a TeamRaiser event, the following message now displays in the appropriate language when a required Country field is left blank:

"Country is a required field"