Service pack 38

Constituent Batch now uses the new code table based gender field that was introduced in service pack 36 .

If your organization uses Constituent Batch, follow the same instructions you used to update Revenue Update Batch(RUB) and Constituent Update Batch (CUB) to likewise update Constituent Batch.

For full details about

• new - GENDERCODEID

• old - GENDERCODE

review service pack 36 .

Review and update batches

Tip: Before you upgrade to service pack 38 (or any service pack) we strongly recommend you commit all uncommitted batches (especially any that were created from imports).

With this update, all new batches use the new Gender field (GENDERCODEID), including new batch templates and new uncommitted batches.

Five existing import templates also use the new Gender field:

• Constituent Batch (CB) - New as of service pack 38,

• Constituent Update Batch (CUB) - New as of service pack 36,

• Revenue Update Batch (RUB) - New as of service pack 36,

• Enhanced Revenue Batch (ERB) - New as of service pack 36,

• and Membership Dues Batch (MDB) - New as of service pack 36.

Other existing batches and templates continue to use the older, hard-coded Genderfield (GENDERCODE). We recommend you edit them to use the new field instead. Then use the updated templates when you commit batches after deploying service pack 38.

Warning: New uncommitted batches created as the result of old legacy imports, where the old import still use the hard-coded Gender field (GENDERCODE) are handled as existing batches. You'll need to edit them to use the new code table version instead.

When you edit a batch template that was created before the upgrade and the batch template previously had the Gender field selected, you'll notice that the field will no longer appears under Selected fields. This is because the hard-coded field (GENDERCODE) was selected. Re-add the Gender field under Selected fields. This will be the new code table Gender field (GENDERCODEID ) instead.

Not sure whether your batch template is using the new Gender field versus the old Gender field? Create a new batch using the template and then review the options available in the Gender field's drop down menu. If you see:

• Blank (Null) and any of the user-defined options your organization added to the code table, then it is updated to use the new field.

  You'll also see options for Female, Male, Other, and Unknown.

• only 4 options (Female, Male, Other, and Unknown), then your batch template has not been updated.

  You can use a global change process to update the new Gender value based on the old Gender value in your uncommitted batch or in the constituent record after you’ve committed the batch.

Additional endpoints are now supported for proxy user and PAT (personal access token) authentication.

Tip: Proxy user and PAT (personal access token) authentication was initially released with service pack 32.

If you currently call any of the following additional endpoints with an existing integration or customization, and use authentication other than PAT, you can now modify the integrations to use this preferred and more secure method of authentication.

1. "~/ODataQuery.ashx"

2. "~/AppFxWebService.asmx"

3. "~/vpp/bizops"

4. "~/util/DataList.ashx"

5. "~/rssfeed.ashx"

6. "~/kpidashboard.aspx"

7. "~/ping/dynamic.aspx"

8. "~/KpiEndpoint.ashx"

9. "~/diagnostics/processStats.ashx"

10. "~/diagnostics/processStats.asmx"

11. "~/ping/static.htm"

12. "~/olap"

13. "~/util"

14. "~/dashboards/GetFlashDashData.ashx"

15. "~/Upload/FileUpload.ashx"

16. "~/Upload/CreditCardFileUpload.ashx"

17. "~/Download"

18. "~/catalog.ashx"

19. "~/ShellFind.ashx"

20. "~/KpiDashboardLanding.aspx"

21. "~/HeartbeatManager.ashx"

22. "~/formimage.ashx"

23. "~/AdHocQuery.ashx"

24. "~/webui"

25. "~/uimodel"

26. "~/additional_services"

This update includes enhancements to both pro-actively improve security strength and to also remediate potential security concerns.

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

All new transaction parts must use Blackbaud Checkout as their payment method. Other merchant accounts are not supported as payment methods for new parts.

If you create a new transaction part, page, or template by copying an existing one, then it must also use Blackbaud Checkout. If it doesn't use Blackbaud Checkout, then it can't be copied to make a new version.

This includes parts in these modules:

• Donation Form (Classic)

• Advanced Donation Form

• Event Registration Form (Classic)

• Event Registration Form (New)

• eCard

• Payment 2.0 for Membership, Sponsorship, Donation Form (Classic), Advanced Donation Form, eCard, and Event Registration Form (Classic)

• Transaction Manager

• Sponsorship Status

• Personal Page Manager

Likewise, to copy a site, all of the site's transactional parts must also use Blackbaud Checkout.

Existing transaction parts must also use Blackbaud Checkout.

To upgrade to future service pack 38, you must use only Blackbaud Checkout. Therefore, we recommend you update existing parts, pages, and templates or else replace them with new ones that use Blackbaud Checkout.

Existing parts that use merchant accounts which don't support Blackbaud Checkout are not affected by this update and their functionality remains unchanged.

This update helps ensure complacence with PCI 4.0.

Blackbaud Payment Service (BBPS) is deprecating support for the following payment processing gateways:

• Authorize.net

  For details, see the Blackbaud Knowledgebase article regarding Authorize.net.

• Bambora (IPPayments)

  For details, see the Blackbaud Knowledgebase article regarding Bambora.

• IATS (US)

  For details, see the Blackbaud Knowledgebase article regarding IATS.

• Payflow Pro

  For details, see the Blackbaud Knowledgebase article regarding Payflow Pro.

• Cybersource for the following currencies:

  • Australian dollars (AUD),

  • British pounds (GBP),

  • Canadian dollars (CAD),

  • Euros (EUR),

  • New Zealand dollars (NZD),

  • US dollars (USD).

  Payments made using these currencies will be rejected.

  Other currencies continue to be supported for Cybersource.

  For details, see the Blackbaud Knowledgebase article regarding Cybersource.

If your organization processes through the Blackbaud Payment Services (BBPS) with one of the payment gateways mentioned above, you must update your Blackbaud solution to process through Blackbaud Merchant Services (BBMS) as soon as possible.

Tip: Blackbaud Merchant Services is Blackbaud’s end-to-end payment processing solution designed specifically for nonprofits. For more information, see Getting Started with Blackbaud Merchant Services.

This update includes enhancements to both pro-actively improve security strength and to also remediate potential security concerns.

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

With Online Giving, you can improve your fundraising efforts using Optimized and Standard Donation Forms.

• Optimized Forms require minimal set up and encourage donors to complete transactions because of a streamlined design that captures payments before collecting contact information. To make data-driven decisions to optimize donor experiences and help you raise more, we conduct A/B testing.

• Standard Forms give you the most control and use a drag-and-drop designer to help you create a customized form.

After you connect your Blackbaud CRM solution to Online Giving, gifts from donation forms flow to Contributions in Online Giving and your CRM. From Contributions, you can:

• View one-time and recurring gift payments

• Retry failed recurring gift payments

• Pause, resume, or end a recurring gift plan.

To learn more about these capabilities, see Online Giving. To get started, see the tutorials.

Note: If you also use Blackbaud Donation Forms (Online Giving), you'll need to be on the most recent service pack of Blackbaud CRM in order to receive features from Blackbaud Donation Forms (Online Giving).