Service pack 39 expands on gender code enhancements which were originally introduced with service pack 36.

Relationship types

With this release, Relationship types are now displayed based on gender values supported by the new Gender (GENDERCODEID) field.

The original Male, Female, Unknown, and Other values were converted to the new Gender (GENDERCODEID) field.

With this conversion, the Relationship type settings you originally configured for Relationship types continue to be supported and the default functionality is preserved. You don't need to take any action.

Specifically, for Relationship settings, when a Relationship type is set to the gender:

• Female, then the Relationship type will appear as an option in the Relationship dropdown menu when the linked constituent's GENDERCODEID is Female, Unknown, or Blank (Null). It won't appear if the GENDERCODEID is Other or a new value from the code table.

• Male, then the Relationship type will appear as an option in the Relationship dropdown menu when the linked constituent's GENDERCODEID is Male, Unknown, or Blank (Null). It won't appear if the GENDERCODEID is Other or a new value from the code table.

• Any, then the Relationship type will appear as an option in the Relationship dropdown menu regardless of the linked constituent's GENDERCODEID field value.

Additionally, with this release, you can now also choose to set all Relationship types to Any gender. You don't need to manually reconfigure each type.

1. Start from Constituents. Then, under Configuration, select Relationship settings.

2. Under Tasks (left panel), select Set all relationship types to "any" gender.

   This configures all Relationship types to default to Any gender. This can't be undone. Users must have a feature permission set via their System role to enable them to make this permanent change.

To learn more about the new Gender (GENDERCODEID) field, see service pack 36.

Title codes

Service pack 36 also included updates for Title codes and service pack 39 provides additional enhancements.

You can now also choose to set all Title codes to Any gender. You don't need to manually reconfigure each type.

1. Start from Constituents. Then, under Configuration, select Title codes.

2. Under Tasks (left panel), select Set all title codes to "any" gender

   This configures all Title codes to default to Any gender. This can't be undone. Users must have a feature permission set via their System role to enable them to make this permanent change.

Life changes

You can now specify what happens when your constituents marry. Do this from the Marriage options under Life changes.

Consider specifying new familial relationships to create for married constituents. For example, enable "step-" and "-in-law" relationships.

You can choose to base these new relationships on gender. When you create new individual relationships, the new GENDERCODEID is supported for existing Male and Female gender options.

Marketing and communications

This area now uses the new gender values from the user-defined code table.

Reporting

The following reports now use the new gender values from the user-defined code table.

• Constituent profile

• Research group prospect & spouse details

• Prospect research additional & spouse details

Blackbaud Data Warehouse (BBDW)

This area now uses the new gender values from the user-defined code table.

As you upgrade to service pack 39, the following component upgrades will be installed, in order, on your application's web servers. You don't need to take specific action to install these.

1. Microsoft Structured Query Language (SQL) Common Language Runtime (CLR) 2014

2. Microsoft Report Viewer 2015 Runtime

However, as a security best practice, if your Blackbaud CRM environment's web server is on-premise, remember to uninstall the following older components after you upgrade to service pack 39.

• Microsoft Structured Query Language (SQL) Common Language Runtime (CLR) 2012

• Microsoft Report Viewer 2010 Runtime

This release includes a number of updates for this connector.

• The connector includes default mapping to support new types of tender and credit cards for Luminate Online (LO). They now include:

  • PAYPAL,

  • APPLE_PAY,

  • GOOGLE_PAY,

  • and VENMO.

• The Constituent Group Export now includes an option to use Luminate Web Services instead of a REST API to send data to Luminate Online (LO). This enables the service to handle record updates faster.

• You can now configure Advocate interaction category and Tributes revenue note type using global settings. Previously, these were hard coded. By default, they're set to their previously hard coded values.

Refer to the LO-CRM Connector user guide for details.

This update fixes multiple defects and issues. For details, review the patch notes for service pack 39.

Organizations hosted by Blackbaud Cloud Operations can use our new service to directly request database backups and access relevant information.

Benefits:

• Saves time and increases autonomy. The new self-service tool reduces the need to file customer support tickets.

• Enables you to specify a date and time (from the previous seven days) for your backup.

• Improves security.

• View a history of backups and requests in progress.

• Copy the SAS URI and download your TDE certificate bundle.

Organization administrators can access the tool now. To grant access to other users, enable permission with the Backup requests – Backup Administrators permissions role.

To find the tool, go to Blackbaud CRM's Cloud Portal and select Backups.

For instructions, see Request a backup. This service is not dependent on a service pack. You can use it even if you aren't yet on the most recent service pack.

Blackbaud Internet Solutions has upgraded TinyMCE for:

• email templates,

• email messages,

• layouts,

• discussion groups,

• formatted text and image parts.

Blackbaud Internet Solutions now requires Blackbaud Checkout as payment method for all existing payment transactional parts. This is the only accepted payment method.

Direct to payment (Blackbaud Secure Payments, BBSP) is now retired.

The following message now appears to admin users at login and in the merchant account gallery.

• "IMPORTANT! With the release of Service Pack 39, payment workflows that do not use Checkout have been discontinued. If any of your forms are configured to use a Merchant Account that is not compatible with Checkout, or use the Direct to Payment option, they will no longer function."

Transactional parts and pages configures with unsupported merchant accounts may still show Direct Debit and Bill me later options for payment, but the credit card option will be hidden. Admin users should edit the transactional part to include a merchant account that supports Blackbaud Checkout and save the changes. This ensures that a credit card option will appear for payment on these pages.

Unsupported merchant accounts will not appear in existing or new transactional parts.

Additionally, the user interface text to label the tab was updated to "Use checkout" instead of "Proceed directly to payment” in payment setup.

With this release, users can reorder the position of the Default Batch in Blackbaud CRM Donation Web Batch Assignment. This enables users to place it in the bottom or lowest position. Previously, it couldn't be reordered.

The version number for Blackbaud Internet Solutions is now 7.2.3.4539. This update includes notable updates to payments.

This update fixes multiple defects and issues. For details, review the patch notes for service pack 39.

If you also use Blackbaud Donation Forms, see What's new in help center for Online Giving to stay informed about the latest new features and enhancements.

Remember, you need to be on the most recent service pack of Blackbaud CRM in order to receive these features from Blackbaud Donation Forms (Online Giving).