Blackbaud NetCommunity New Features Guide

25 downloads 421 Views 5MB Size Report
Email Signup Form. 8. Upgraded HTML Editor in Email Messages and Templates. 11. Donation Form - Mini (Beta). 15. Set up
Blackbaud NetCommunity 7.1 SP1 New Features Guide

8/1/2017 Blackbaud NetCommunity 7.1 SP1 New Features UK

©2017 Blackbaud, Inc. This publication, or any part thereof, may not be reproduced or transmitted in any form or by any means, electronic, or mechanical, including photocopying, recording, storage in an information retrieval system, or otherwise, without the prior written permission of Blackbaud, Inc. The information in this manual has been carefully checked and is believed to be accurate. Blackbaud, Inc., assumes no responsibility for any inaccuracies, errors, or omissions in this manual. In no event will Blackbaud, Inc., be liable for direct, indirect, special, incidental, or consequential damages resulting from any defect or omission in this manual, even if advised of the possibility of damages. In the interest of continuing product development, Blackbaud, Inc., reserves the right to make improvements in this manual and the products it describes at any time, without notice or obligation. All Blackbaud product names appearing herein are trademarks or registered trademarks of Blackbaud, Inc. All other products and company names mentioned herein are trademarks of their respective holder.

NF-2017

Contents New Features

4

Event Registration Form - Attendee List Email Signup Form Upgraded HTML Editor in Email Messages and Templates Donation Form - Mini (Beta)

4 8 11 15

Design the Form

16

Use the Form

19

Set up Apple Pay for Blackbaud Checkout To get approved to use Apple Pay

Merge Fields in Email Subject Lines Directory Private Email Messaging for Anonymous Users Updated reCAPTCHA Gift Aid Configuration Updates Usability Enhancements for Developer Parts Changes in Upcoming Blackbaud NetCommunity Releases

22 22 22 24 26 27 29 31

iFrame Capability

31

Payment 1.0 Part

31

LinkedIn Group Join Part

32

eStore

32

Maintenance Changes

32

New Features Event Registration Form - Attendee List

4

Email Signup Form

8

Upgraded HTML Editor in Email Messages and Templates

11

Donation Form - Mini (Beta)

15

Set up Apple Pay for Blackbaud Checkout

22

Merge Fields in Email Subject Lines

22

Directory Private Email Messaging for Anonymous Users

24

Updated reCAPTCHA

26

Gift Aid Configuration Updates

27

Usability Enhancements for Developer Parts

29

Changes in Upcoming Blackbaud NetCommunity Releases

31

Maintenance Changes

32

This guide provides an overview of new features and enhancements for Blackbaud NetCommunity 7.1 SP1. For information about how to install or update to this version, see the Infinity Platform Installation and Upgrade Guide. Note: You must use The Raiser’s Edge 7.95 or higher to integrate with Blackbaud NetCommunity 7.1 SP1. For Customer Support assistance, visit Blackbaud's website.

Event Registration Form - Attendee List We've added the capability on our Event Registration Form part in Blackbaud NetCommunity to configure and enable an attendee list for events. This benefits organisations that often want to show a list of who has already registered for an event to encourage more people to register. Event registrants can see who's coming to an event and when registering, can choose to opt out of being included in the attendee list. The attendee list is implemented using the existing Directory functionality. You should set up one directory part with the desired fields, add it to a page, and then use that same directory page for all attendee lists across multiple event registration forms. Note: The attendee list functionality requires the Directory part. If your Blackbaud NetCommunity configuration doesn't include the Directory part feature, contact your account representative for more information.

On the Event Registration Form, you can include a link to the attendee list and an option for registrants to opt out of being in the list. Before configuring the Event Registration Form part, you need to specify the participant attribute in The Raiser's Edge to use for tracking attendee list opt-ins. This participant attribute must have a type of Yes/No and be marked as Allow only 1 per record. On the Settings tab in Administrator, Sites & settings, select Enable the attendee list for events and then select the desired participant attribute.

On the Event Registration Form part under Add events, select the Include Attendee List checkbox for each event that you want to provide an attendee list for. Then, under Attendee List options, you can specify whether registrants are opted in to the attendee lists by default, and select the directory page to use for the attendee lists. Once you've included the Event Registration Form part on a web page, you can click Copy Link to copy the attendee list URL and publish it elsewhere on your website.

On the Language tab in the Registration category, you can edit the default text for the attendee list link and the opt-in option that displays on the event registration form. When there are multiple events, a corresponding attendee list link displays for each event. However, you can't customise the link name per event; the same text displays for all events.

The attendee list link displays on the Event Registration Form above each event.

When users click the link in the registration form, the attendee list for the event displays a list of registrants and their guests. If directory messaging is enabled on your site, it will also be available in the attendee list. Note that directory messaging is only allowed for main registrants (since they are linked to a constituent) and not for guests.

Registrants can select the attendee list opt-in option when they register for the event. The attendee list pulls information from the event's participant records in RE. Once the registration transaction has been processed in the BBNC plugin, attendees will then be added to the attendee list.

Email Signup Form The new Email Signup Form part allows website users to sign up to receive email from your organisation without requiring them to register or to create a user name and password. After users complete the form, the program creates sign-up requests in The Raiser's Edge so you can add their information to your constituent database. You use this part if your organisation sends recurring emails from Messages and you want to allow users to sign up to receive them, but not have to register for the website. When you configure the form, you include the constituent attributes from The Raiser's Edge that correspond to the lists you generate for recurring messages. Note: The email signups create database constituent records, not website user records. The program only creates website user records when users sign up through the User Login,

Personal Page Manager, or Fundraiser parts. It is possible for constituents to inadvertently complete the form multiple times, so we recommend you clear the Send a unique email to each constituent who shares the same email address checkbox in Sites & settings. When you clear the option, you prevent sending the same messages to duplicate constituents. For information about this option, see Email Settings on page 1. Use the Design tab to configure the form and customise it for your organisation. In the Fields section, select which fields to include on the form and whether they are required. The Last Name and Email Address fields are required and selected by default because they are the minimum required fields to subscribe a new constituent to emails in The Raiser's Edge. In The Raiser's Edge, the Email Address is marked as the primary email address in the constituent record, and the email type is mapped based on the email address setting in Sites & settings, Phone type mapping. You can change the order in which the fields display on the form by clicking the field's row and dragging up or down in the list.

Under Attributes, select which constituent attributes to Include on the form and whether they are Required fields. Typically, you display attributes when you have multiple options and you want users to subscribe to emails that match their preferences.

Note: All the constituent attributes you select in Sites & settings with a type of Yes/No are available, but we recommend you only include those your organisation uses for recurring emails sent from Messages. Optionally, you can select Enable reCAPTCHA login to display reCAPTCHA on the form or specify a Constituent Code to apply to users who sign up using the form. Under Navigation, select the web page to display to users when the form is completed. Click the binoculars to display the list of pages on your site to choose from. This field is required.

As a last step, configure the confirmation email to display after users complete signing up. Click New Signup Confirmation Email, then configure the email for your organisation. The Name of email, Subject, From address, and From name fields are required. You can edit the default text for the email message. Here's an example of how the Email Signup Form displays on your website:

In The Raiser's Edge, you can look at the transactions for Sign-up Requests to see who subscribed to emails from your organisation. In the Sign-up Requests Transactions window, use the new Email Sign up Transactions filter to view all transactions that originated from the email signup form. If there's no existing constituent, you can create a new constituent for linking, and then process the transaction. The constituent's information and any attributes entered on the email signup form are saved in the constituent record in The Raiser's Edge.

Upgraded HTML Editor in Email Messages and Templates Blackbaud NetCommunity provides a powerful HTML editor to allow you to format and lay out content. With the HTML editor, you can update content easily and safely while you maintain control over the design and content. In this release, we've upgraded the HTML editor used for creating email messages and email templates to the most recent version (TinyMCE version 4).

One of the most important benefits of this upgrade is that the editor now includes the HTML  tag that's necessary for creating responsive design. With responsive design, your emails display optimally on any device — desktop, tablet, or smartphone. The previous version of our HTML editor removed the tag from the source code, which prevented you from creating emails with a responsive design. This new version of the HTML editor automatically adds the tag in the HTML source code, where you can include elements such as scripts, styles, and meta information. Note: For this release, we've updated the HTML editor only for email templates and email messages. Upgrades to the HTML editor used in other parts of Blackbaud NetCommunity are planned to be phased in as part of our upcoming releases. Another difference between the upgraded HTML editor and the previous version is how the functionality is organised. In the previous version, there were separate tabs — Formatting, Insert, View, and Image — as shown below. There was also a Table tab that displayed when a table was selected in the editor.

In the upgraded version, the HTML editor functionality is now organised into three drop-down menus — Insert, View, and Table — and a toolbar.

The toolbar includes all the same functionality that was previously located on the Formatting tab. You can hover over each toolbar icon to see its description. The Insert, View, and Table menus include the functionality that was previously located on the Insert, View, and Table tabs. Note that the Table menu items are not enabled unless you have a table selected in the HTML editor. When you click anywhere in a table, a toolbar with commonly used table operations — Table properties, Delete table, Insert row before, Insert row after, Delete row, Insert column before, Insert column after, and Delete column — displays in the HTML editor adjacent to the table. These table operations, along with additional ones, are also included in the Table menu.

Functionality previously located on the Image tab is now accessed from the toolbar. Click Insert/Edit image to display the Insert/Edit Image window. Here you can select an image to add to your email message or template, and modify the image's appearance and properties.

You can include scripts, styles, and meta tags in your email message or template using the tag. On the View menu, click Source code, add your own code as needed in the tag, then click Ok to save.

You can also specify document properties — Title, Keywords, Description, Robots, and Author — that will be included in the tag as meta data. Click on the toolbar to display the Document Properties window. The data you enter in the document property fields is saved as meta data inside the tag.

While the document property fields may not be as important to email messages and email templates, they'll have more significance once the HTML editor is upgraded for other Blackbaud NetCommunity parts, such as the Formatted Text and Images part, the Donation Acknowledgment part, and the Event Acknowledgment part.

Donation Form - Mini (Beta) The Donation Form - Mini (Beta) part is our beta release of a new Blackbaud NetCommunity donation form that provides a new simplified checkout experience for campaign-based

donations. The form has a modern, responsive HTML design that automatically adjusts to the device size, such as a smart phone or tablet, on which the page is being viewed. This new form allows donors to make a quick, basic donation by selecting a predefined giving level or, if configured, to enter their own gift amount. Because the form uses PCI-compliant Blackbaud Checkout, customers can be assured that credit card and merchant account information is processed and stored on a Blackbaud-hosted secure server. Digital wallet options are available on the Donation Form - Mini (Beta) part for BBMS customers only. • Visa Checkout and Masterpass are automatically available to donors as secure checkout options. Both support the same currencies as BBMS: USD, CAD, GBP, and EUR. • Apple Pay is currently only available as a limited capacity Early Adopter Program (EAP) for BBMS customers in the U.S. Note: eReceipts are not supported with the Donation Form - Mini (Beta) part. Note: The Donation Form - Mini (Beta) part is considered a proof of concept and will transform into a full donation form in an upcoming Blackbaud NetCommunity release.

Design the Form Use the Design tab for the Donation Form - Mini (Beta) part to configure the form and customise it for your organisation. In the Donation form message section, you can use the HTML editor to create a custom message to display on the form or you can use the default message.

In the Designation section, select the designation that you want associated with donations made using this form. In the Appeal section, click Add appeal to search for and select the appeal that you want associated with the donations made using this form.

Note: The designation and appeal can be overridden by the URL used to access the donation form. You format this URL as https://www.yourdomain.org/donate-now?aid=Appeal system record ID&did=Designation system record ID. You can find the appeal and designation system record IDs to include in the URL by creating an ad-hoc query in The Raiser's Edge. In Analysis > Information Library, click Add an ad-hoc query on the Queries tab. In the Select a Source View window, select Appeal in Record type and in Source view, then click OK. In Select filter and output fields, select Appeal record and any other query criteria, and add to Results fields to display. Click the Preview results tab. For the desired appeal, copy the corresponding system record ID. This is what you'll use in the URL for the Appeal system record ID. To locate the Designation system record ID, create another ad-hoc query and follow the steps above, substituting Designation for Appeal. Under Giving levels, you can set up suggested giving levels to display on the donation form. By default, three best practices giving levels of £25, £100, and £500 are specified. You can change these amounts, and add or remove giving levels as desired. There must be a minimum of one giving level on the form. Optionally, you can include a name to display on the form for any of the giving levels, and specify a giving level as the Default so it's preselected on the donation form.

You can also allow users to specify another gift amount by selecting the Allow other amount option, then entering a Minimum gift amount that donors can contribute. For UK sites, you can optionally include the Gift Aid option on the donation form by selecting Allow Gift Aid capture under Donor options. Website users can select whether to allow your organisation to claim Gift Aid for the donation. You can customise the text displayed on the donation form for this option using the Language tab.

In Payment Setup, select the merchant account to use to process donation transactions. Note: All merchant accounts support the Donation Form Mini - (Beta) part except for iATS and IP Payments. iATS and IP Payments display as disabled in the Merchant account list.

The default confirmation message that displays to donors after their payment is made shows under Confirmation Screen. You can customise this content according to your organisation's needs. Note that Amount, Designation, and Appeal are the only merge fields that can be displayed on the confirmation screen.

Optionally, under Additional payment fields, you can select to display a reCAPTCHA checkbox on your Blackbaud Secure Payments form below the credit card payment fields. Users who are not logged in to your site must select the reCAPTCHA checkbox and perform the reCAPTCHA challenge before they can submit the form.

Use the Form On your website, the Donation Form - Mini (Beta) part displays as shown in the example below. Note: Due to the donation form's responsive design, it automatically adjusts to the device size on which it is viewed and may look different than this example.

Donors can select their donation amount or enter a different amount in Other, then click Donate Now. They can then enter their billing address information in the checkout window. Note: Donors using a digital wallet, such as Apple Pay, do not need to enter billing information.

Warning: Your code tables in The Raiser's Edge for countries and their subdivisions, such as Countys and provinces, must follow the International Organisation for Standardisation’s ISO 3166 standards. The secure payment page uses ISO 3166-1 for countries and ISO 3166-2 for

subdivisions such as counties. If your code tables do not match these standards, Blackbaud Checkout changes selections to the closest abbreviation when it processes transactions, and this can lead to incorrect address information. For example, if your countries table includes “United Kingdom,” The secure payment page changes this to the United States abbreviation “US” because it is the closest abbreviation to “Un.” In ISO 3166-1, the abbreviation for the United Kingdom is “GB,” and your code table must match this. For information about how to edit your code tables in The Raiser's Edge for countries and their subdivisions, see the Configuration and Security Guide. After donors click Continue to payment, they can enter their payment information.

The name entered in the Name on card field is used to match to an existing constituent record or to create a new constituent record. Note: The fields on the secure billing and payment screens display as shown and cannot be customised. When donors click Complete payment, the confirmation screen displays.

Set up Apple Pay for Blackbaud Checkout With the Donation Form - Mini (Beta) part, you can now accept payments through Apple Pay when you use Blackbaud Merchant Services (BBMS) to process one-time credit card donations. This new payment option allows your constituents on Apple devices to make donations without having to enter as much information on the donation form, because data such as their credit card number and billing address are already stored in their Apple Pay wallet. Apple Pay is currently only available as a limited capacity Early Adopter Program (EAP) for BBMS customers in the U.S. If you are interested in joining the EAP, follow the instructions below. Participation is limited to a first-come, first-served basis.

To get approved to use Apple Pay •

Complete the request for information form on Blackbaud's website. A Blackbaud representative will contact you to confirm we have completed enablement of Apple Pay for use with your Blackbaud Merchant Services account. If you do not yet have a Blackbaud Merchant Services account, a representative can assist in setting up an account for you.

Note: Please be aware that the onboarding process for setting up Apple Pay may take several weeks. In the meantime, your organisation doesn't have to wait to start using the Donation Form - Mini (Beta). You can still configure the form and use it for taking donations using credit cards, Visa Checkout, and Masterpass. Once the onboarding process is completed, Apple Pay will automatically display as an additional payment option on the checkout screen for donors who are using an Apple Payenabled environment. All transactions are processed via BBMS. Note: Ensure you select your BBMS merchant account in the Merchant account field on the Donation Form - Mini (Beta) part. Note: Refer to Apple's Terms and Conditions in the Blackbaud Checkout FAQs.

Merge Fields in Email Subject Lines We've added a new capability in Blackbaud NetCommunity that allows you to personalise subject lines in emails. Personalisation increases the likelihood for higher open rates of your emails and allows you to better target your messages. Note: This functionality is only applicable to email Messages and Templates. It is not supported for Campaigns or Newsletters. You now have the ability to select merge fields (such as First Name, Last Name, and Title) to include in your email message subject line. If no merge fields exist for a constituent in The Raiser's Edge, an alternate subject line that you specify is used instead.

You can include merge fields in the subject line of new or existing email messages and templates. When you use a constituent template for an email message, or select the Constituents data source for an email template, the Insert merge fields icon displays to the right of the Subject field.

Click the icon to display the list of available merge fields, then select the ones you want to include in the subject line. As you make your selections, the merge fields display in the Subject field. In addition, you are required to specify default text for the alternate subject line. If any of the merge fields are blank for a particular constituent, Blackbaud NetCommunity uses the alternate subject text in the subject line for that constituent. When you use the email template to create a new email message, the merge fields you specified are automatically included in the Subject field of the message. If desired, you can click the Insert merge fields icon to include additional merge fields, remove existing merge fields, or edit the default subject line text for this email message.

Directory Private Email Messaging for Anonymous Users We've enhanced the Directory Private Email Messaging functionality so that anonymous users can send private messages. Alumni and other users now have the ability to send messages to others in the directory without having to log in to Blackbaud NetCommunity. Before you configure a directory part to allow anonymous users to send messages, make sure that reCAPTCHA is enabled on your site in Administrator > Sites & settings. See reCAPTCHA settings for information on configuring reCAPTCHA. On the Design tab of a Directory part, select Allow users who are not logged in to send messages under Messaging Fields to enable anonymous messaging. This option is available only when Allow messaging between users is selected.

Note: Be aware that it is possible to configure directory messaging with an Email Preferences part that does not allow for opt-outs. For example, you could include a link in the Configure Opt-out message to a page with an Email Preferences part. If the Include opt-out for directory messages option is not selected in the Email Preferences part, recipients will not have the ability to opt-out of directory messaging. When messaging is enabled, the Send a message icon displays in the directory's Messaging column for people who have a valid email address in The Raiser's Edge and have not opted out of messaging. Anonymous users can click the icon to display the default email message, which can be edited as desired. The Default subject, First Name, Last Name, and From email

address fields are required. The From email address is the default Reply to address when the recipient replies to the message. Note: An anonymous user can send a maximum of 10 messages per hour. When this limit is reached, a message displays telling them to try again later. When the user clicks Send message, the email is sent via the organisation to the recipient, and the recipient's email address is not visible to the sender. A confirmation message displays when the email is successfully sent.

Updated reCAPTCHA When you enable reCAPTCHA in Administration, Blackbaud NetCommunity displays a completely automated public Turing test to tell computers and humans apart (CAPTCHA). With CAPTCHA functionality, the program can ensure a user is not an automated program to generate spam or phish for payment information. Previously, the program displayed distorted text that users were required to type into a box. To simplify the experience, the program now displays a checkbox labeled "I'm not a robot." Users can select the checkbox to proceed.

Note: In cases where the program cannot confidently predict whether a user is a human or an abusive agent, it will display an additional test to confirm the user is valid. For example, the CAPTCHA may display multiple images and ask the user to identify which images match a particular description. The reCAPTCHA options you select in Administration control all parts in Blackbaud NetCommunity except the Event Registration Form, and Payment 2.0 parts that use the Blackbaud Secure Payments form. Those parts now include an Additional payment fields section on the Design tab where you can select to include reCAPTCHA.

When you include this option, a reCAPTCHA checkbox displays below credit card payment fields on your Blackbaud Secure Payments form. Users must select the reCAPTCHA checkbox before they can submit the form.

Note: If your reCAPTCHA keys no longer work with the updated version, the site administrator can go to http://www.google.com/recaptcha to obtain new public and private keys, and to register the site domains.

Gift Aid Configuration Updates The Event Registration Form part and the Membership Form part include new configuration options for capturing Gift Aid for UK customers. You now have the ability to include the Gift Aid option on the Event Registration Form part when additional donations are enabled. In addition, we've enhanced the Membership Form part so you can now configure the Gift Aid text from within the part editor. Previously, you could add the Gift Aid checkbox to a membership form but weren't able to edit the corresponding text. On the Design tab of an Event Registration Form part, under Options, select Allow additional donations and then select Allow Gift Aid capture to display the Gift Aid option on the Event Registration Form.

Note: When you enable Gift Aid, ensure that you select a different fund for the additional donation than the one used for the event registration fee. Otherwise, the gift will include the full amount of the event registration fee plus the additional donation. Since event registration fees are exempt from Gift Aid, your organisation won't be able to claim any Gift Aid for the donations. On the Language tab, the default text for the Gift Aid option is shown. You can edit this text if desired.

On your website, the Gift Aid option displays beneath Make an additional donation on the Event Registration Form.

On the Design tab of a Membership Form part, under Additional fields, click Allow additional donations and then select Allow Gift Aid capture. We've added new fields here — Gift Aid checkbox label, Gift Aid checkbox text, and Gift Aid confirmation label— with default text to display to users on the Membership Form. You can edit the text in these fields if desired.

Usability Enhancements for Developer Parts We've enhanced the code entry sections of several parts — Style Sheets, Unformatted Text, and Custom Content — to make the development process easier. We've improved the code editor functionality so it's easier to create and edit code directly in these Blackbaud NetCommunity parts. Previously, many users had to write and troubleshoot the code in a different application, and then copy the code back into the Blackbaud NetCommunity parts, which made the process time-consuming. One of the enhancements we made was to add line numbers to the code entry display. This enables you to locate code more easily.

We also included four new buttons — Undo, Repeat, Go to, and Maximise — to enable you to perform common editing actions.

In addition, we added an Apply button on the Unformatted Text editor. This enables you to save your work and continue editing without having to close the part and reopen it.

Changes in Upcoming Blackbaud NetCommunity Releases At Blackbaud, we are committed to providing you with tools that leverage the latest market trends and technology. As part of the ongoing functionality review process, the following functionality and parts will no longer be supported as of the specified upcoming releases.

iFrame Capability In a previous release, we removed the ability to use iFrames in Blackbaud NetCommunity, but provided a workaround for certain customers. In our upcoming 7.1 SP2 release, we are removing the workaround, which will permanently disable all iFrame capabilities. This means that you will no longer be able to use iFrame to embed Blackbaud NetCommunity pages into a third-party site.

Payment 1.0 Part In 2011, we released Payment 2.0, the next iteration of our Payment part. In addition to all the functionality offered by the Payment part, Payment 2.0 captures payment information on secure payment pages to help you comply with the Payment Card Industry Data Security Standard (PCI DSS). Therefore, the Payment 1.0 part will be disabled in our 7.1 SP2 release.

LinkedIn Group Join Part In 2015, LinkedIn changed their APIs which caused the LinkedIn Group Join part to no longer work. After reviewing the functionality, we determined that this part will no longer be supported. This part will be disabled in our 7.1 SP2 release.

eStore Blackbaud will no longer sell the eStore part of Blackbaud NetCommunity to new clients. While eStore will continue to be available to Blackbaud NetCommunityclients that already own eStore, starting in Q1 of 2018, Blackbaud will no longer develop eStore beyond critical security maintenance. Clients that are interested in exploring alternative solutions to address their eStore needs should contact their account executives for more information.

Maintenance Changes Blackbaud NetCommunity version 7.1 SP1 also includes these changes. l

l

l

l

l

l

l

This fix addresses an issue where corrupted parts and pages could not be deleted. Previously, an error occurred when attempting to delete these pages and parts from the site. Now, this issue has been resolved. (Work Item 604207) This fix addresses an issue where privacy settings could not be specified so user address information would not show in the user profile or directory. Now, this issue has been resolved. (Work Item 634430) This fix addresses an issue where BBNC was using an HTTP header for an unsupported version of Internet Explorer. Previously, user content pages and administrator pages in BBNC included the HTTP header X-UA-Compatible: IE=9, which was forcing Internet Explorer 9 compatibility mode. This was causing design and compatibility issues with current versions of Internet Explorer. Now, this header has been removed from all pages in BBNC. (Work Item 640582) This fix addresses an issue with deleting file folders. Previously, when you attempted to delete a file folder in Site Explorer > Files, a message displayed that the folder was in use by a Documents part that no longer existed on the site, and the folder would not be deleted. Now, this issue has been resolved. (Work Item 656551) This fix addresses an issue where an error occurred when making a selection in the category dropdown on the Language tab on the User Login part. Now, this issue has been resolved. (Work Item 672676) This fix addresses an issue with the Language tab for the Donation Form, User Login Form, and Event Registration Form. Previously, when you updated and saved the dropdown field text on the Language tab in the Donation Information category (on the Donation Form), the Registration category (on the Event Registration Form), or the Registration Form category (on the User Login form), the text wasn't populating the drop-down fields as expected. Now, this issue has been resolved. (Work Item 680101) This fix addresses an issue where changes to the Reasons table in Raiser's Edge were not

automatically updating the Membership Form part in BBNC. Previously, when you made updates to entries in the Reasons table, the changes were not reflected in the Join Reasons drop-down on the Membership Form as expected. Now, this issue has been resolved. (Work Item 681387) l

l

l

l

l

l

l

l

l

This fix addresses an issue where the Transaction ID on the Raiser's Edge/BBNC record for event transactions was not being passed to BBMS. Previously, when tranactions were submitted from Payment 2.0 or Event Registration 2.0 forms, the BBSP ID was being saved. Now, this issue is fixed and the Transaction ID on the Raiser's Edge/BBNC record correctly matches the BBMS Transaction ID as expected. (Work Item 681680) This fix addresses an issue where transaction date/time stamps were respecting the time zone of the BBNC server and not the time zone of the actual client. Previously, transactions that were coming in after 9pm PST were posting on the following day. Now, this issue has been resolved. (Work Item 683169) This fix addresses an issue where duplicate addresses were being added to a constituent record when processing profile updates. Previously, when profile updates included a constituent’s address and a phone number or email address, if the address information was rejected, the phone or email address was added to the record, but a duplicate address was also added. Now, this issue has been resolved and a duplicate address is no longer added to the record. (Work Item 687759) This fix addresses an issue where the title field was not being added to Raiser's Edge Event Participant records for guests registered on the BBNC Event Registration form. Previously, when a user registered for an event with more than one guest, the title field was only being added to the registrant's record. Now, the title field is also being added to the guest records as expected. (Work Item 689462) This fix addresses an issue with filters being reset on the Event Calendar. Previously, if you selected to filter categories on the Event Calendar and then changed the month on the calendar, the filters were being reset. Now, the filters are no longer being reset when a different month is selected on the calendar. (Work Item 693338) This fix addresses an issue where an error occurred when you attempted to view an email recipient list for an email message. Previously, when you selected the report icon in Email > Messages, and then clicked the recipients link, the following error displayed: "The server encountered an error processing the request. Please refresh the page, if the issue persists kindly contact the support team for assistance." Now, this issue has been fixed and error no longer occurs. (Work Item 693705) This fix addresses an issue with creating a new user when purchasing items through BBNC when using the eStore options. Previously, the user was not able to register and successfully make the purchase. Now, this issue has been resolved. (Work Item 694616) This fix addresses an issue where invalid recurring pay-cash records were being generated in Raiser’s Edge when donors made a recurring gift and chose direct debit as a payment option. Now, this issue has been resolved and a valid pay-cash record is generated as expected. (Work Item 695065) This fix addresses an issue where attempts to send email messages to invalid accounts increased significantly. Previously, BBNC would make over 1000 attempts to send the message to an invalid account. Now, this issue is resolved and only one or two attempts

are made as expected. (Work Item 696676) l

l

l

l

l

l

l

This fix addresses an issue where email addresses were not being pulled over to BBNC records when using a Raiser's Edge query for a BBNC email list. Previously, for those records where the phone type value was set but the phone number value was blank, the email address was not being pulled over to the record in BBNC. Now, email addresses for such records are also being pulled into BBNC as expected. (Work Item 705022) This fix addresses an issue where the sent email report was showing no results for Bounced emails. Now, bounce information is being shown as expected in email reports. (Work Item 710350) This fix addresses an issue where sent email reports in BBNC were incorrectly showing bounced emails as being received. Now, the bounced email report is showing the correct results as expected. (Work Item 710352) This fix addresses an issue where bounced emails were not displaying as such in the email reports. Now, this issue has been resolved, and bounce count and bounce details (soft bounce/hard bounce) are shown correctly on the email message report. (Work Item 710353) This fix addresses an issue with newly added workflows not being available in Email Notifications. Previously, if you added a new workflow in Administration > Workflows, the workflow was not displaying in Email Notifications, since only 25 workflows were being displayed. Now, newly added workflows are displaying in Email Notifications as expected, regardless of the number of workflows. (Work Item 712665) This fix addresses an issue where the user import functionality did not provide the password in the new user registration email, and there was not a password reset link in the new user registration email. Now, this issue has been resolved and the password reset link is included in the new user registration email. (Work Item 714134) This fix addresses an issue where emails were being sent to the incorrect address. Previously, emails were being sent to the email address listed on a constituent's organisation relationship record instead of the email address specified on the Bio1 tab of the constituent record. Now, this issue has been resolved. (Work Item 730373)