What's Recent

Previously, the Total gifts over time chart only displayed the first gift in a recurring gift. Now it displays all subsequent gifts in a recurring gift to more accurately display your received funds.

From Online Giving, under Total gifts over time, select Gift type, Recurring gifts. For more information, see Performance for All Forms.

To help you manage recurring gift plans in Contributions, from Recurring gift plans, select a plan. To place payments on hold indefinitely or to skip up to ten payments, select Pause plan. You can also edit the next payment date in the plan under Gift summary. For more information, see Recurring Gifts.

To improve your reconciliation process and verify a donor's card information when they ask for a refund, the following fields now automatically populate on gift records in Altru:

• Name on card

• Credit card (last four digits)

• Expires on

• Authorization code

To streamline OData connections, you can now use a proxy user to connect to your Altru database. Previously, proxy users were only supported for SOAP API endpoints.

As a reminder, Altru supports proxy users for the following:

• ~/ODataQuery.ashx

• ~/AppFxWebService.asmx

• ~/vpp/bizops

• ~/util/DataList.ashx

For more information, see Non-Interactive Proxy Users.

To provide your patrons with quicker response times when purchasing tickets online, this release includes performance improvements for program web forms. Also, to improve back-office sales functions and operations, a new business process now runs nightly to remove stale, pending sales orders that may cause slowness in other areas of Altru.

This release upgrades Tiny MCE to version 6.8.2. This improves usability and security for the HTML editor throughout Altru.

As part of ongoing security enhancements, we upgraded web forms to use version 1.13.2 of JQuery UI.

To help you identify recurring payments that fail due to missing reference tokens, you can now query on credit card tokens in ad-hoc queries. This enhancement is especially helpful for those of you who process payments through Blackbaud Payment Terminal™.

To protect sensitive payment info for recurring gifts and memberships, the Blackbaud Payment Service securely stores card details in its vault and replaces them with reference tokens in Altru. Payments that are missing reference tokens will fail to process.

To identify revenue records that are missing credit card tokens:

1. From Analysis, Information Library, add or edit an ad-hoc query.

2. Under Browse for fields in, select Revenue.

3. Under Select fields, expand the Credit card node and select Credit card token.

4. Add the field to your query criteria or results as needed.

For example, if recurring memberships were incorrectly purchased through a Payment Terminal device, create a query to identify and resolve them. For more information, see How can I find recurring memberships that were processed by an Altru Payment Terminal? or How do I identify recurring memberships that do not have a credit card token? in Knowledgebase.

We recently introduced the following enhancements to the Altru Help Center, your central location for help resources:

• The ability to search and quickly navigate to relevant topics.

• A featured highlights section for timely resources and upcoming events.

• Updated help topics that feature a streamlined display and easier navigation from the left side.

Also, the Help Center is now easily accessible from Altru:

• To access the help center homepage from Altru, open the help panel and select Search the Help Center from the bottom of any topic.

• To open a topic with a full-page view in a new browser window, from a help topic in Altru, select Open in browser.

• To access the Help Center when you're working outside of Altru, bookmark this URL.

To give you more flexibility when managing group reservations, you can now change the patron on a group sales order.

1. From a group sales record, under Tasks, select Change booked/sold to patron on order.

2. Search for and select the new patron.

3. Choose whether to also change the contact or itinerary leader.

4. When finished, select Save.

After you save, the sales order and all associated revenue are linked to the new patron.

To help your organization comply with data privacy laws, it's now easier to:

• Record and respect individual opt-out signals.

• Recognize and respect universal opt-out signals.

Record and respect individual opt outs

Pursuant to new US state laws, an individual has the right to opt out of the processing of their personal data for purposes of targeted advertising or the sale of personal data. Now when you add or edit an individual's record in Altru, you can indicate whether they opt out of sales or targeted ads.

Tip: These fields also appear in the Constituent Update Batch and in import processes (when the Constituent Update Batch template is selected).

To ensure you can easily respect these preferences, they appear on the individual's constituent record (under the Personal Info tab) and in ad-hoc queries (under the Constituent node).

Recognize and respect universal opt outs

Altru web forms now automatically recognize and record universal opt-out signals like the Global Privacy Control (GPC).

Note: Once an enabled GPC is recorded for a constituent it cannot be changed. Consult your legal counsel to find out how your organization should respond to enabled GPC signals.

How it works

Universal opt-out signals are sent from individual browser accounts when an add-on or plugin, like the GPC, is enabled. The signal is included in header data with every HTTP call made from that browser account. The signal is either enabled or not enabled — there is no specification or configuration beyond that.

When an Altru web form detects a universal opt-out signal from the constituent, it automatically updates their record to indicate they have opted out of sales and targeted ads.

[add screenshot]

Also, the Global Privacy Control (GPC) field now appears under the constituent node in ad-hoc queries.

Note: While privacy laws and best practices are ever-changing, Blackbaud's goal is to provide you with solutions you can use to manage your data with privacy in mind. For more information about privacy laws and compliance, visit Blackbaud's Privacy Resource Center.

To extend the functionality of Altru and do more with your constituents and fundraising efforts, Altru now supports the use of SKY API endpoints. SKY APIs are modern, open, industry-standard application programming interfaces (APIs) that can be used to develop robust applications and extensions.

Your organization can use applications created by Blackbaud, providers in the Blackbaud Marketplace, someone at your organization, or other approved external developers.

Browse and connect to apps

The Blackbaud Marketplace features applications by Blackbaud and Blackbaud partners that enable you to extend the functionality of your Blackbaud solutions. Visit the Marketplace to:

• Search for offerings that are compatible with your Blackbaud solutions.

• Directly request follow-up from trusted providers.

• Find new technology that works with the Blackbaud solutions you use every day.

From the Marketplace, you can view details about each application added, including the application publisher. You can also filter the list of apps by Blackbaud solution. To use an application, from its details page, select Connect.

Note: Only environment admins in Blackbaud environments can connect applications. To learn how to become an environment admin, see the Permissions to connect applications in the Marketplace Help.

Build a new app

Want to develop an application using SKY API? See the SKY API Getting Started page for a step-by-step guide.

For more information, visit SKY API for Blackbaud Altru resources and the SKY Developer Community.

Note: Currently, Altru does not support SKY Add-ins or the Microsoft Power Platform.

To further improve the experience for web form users, now when a user sets or resets their password, the form:

• Indicates whether the password meets the requirements.

• Indicates whether the Password and Confirm password values match.

• Lets users temporarily reveal their password to see what characters they enter.

To better track your solicitation efforts, you can now apply appeals to donations made through online sales. The latest release enables you to:

• Configure donation forms to automatically add appeals to donations.

• Display multiple appeals on a donation form to let your donors choose.

• Create custom donation form URLs to use in digital marketing efforts.

• Manually add appeals to existing online donations.

Configure donation forms

From a donation form's settings, you can now use sources to link donations to specified appeals. Add and display multiple sources to let your donors choose, or add a single, default source to automatically apply the same appeal to all donations given through the form.

1. From Web, Manage donation forms, expand a form's row.

2. Select Options.

3. Under Sources, select Add source.

4. Enter a display name and choose which appeal to add to donations.

   Tip: If you plan to display the source on your donation form, use patron-friendly language.

5. Select whether the source is the form's default. If a donor gives through your form and doesn't choose a source, the form automatically adds the default appeal to the donation.

6. Select whether to display the source on your donation form.

7. To require donors to choose a source, select Source is a required field.

   Note: If you choose this setting, at least one source must be set to display.

8. Continue adding sources as necessary. When finished, select Save.

On the donation form, sources you set to display appear in a new field, "What prompted you to give?"

When donors give, the appeal displays under the donation's payment record details.

Track donations through custom URLs

Now when you share your Altru donation form online — such as through a website, social media post, or email — you can include a custom URL to automatically add an appeal to donations you receive.

To create the URL, first configure the donation form's sources as outlined above. Then, add a source tag to the form's URL:

1. From Web, Manage donation forms, expand a form's row.

2. Copy the donation form URL (such as https://1234.blackbaudhosting.com/1234/OnlineGiving).

3. At the end of the URL, add ?source= followed by the appeal name (such as ?source=SPRING2023EMAIL).

   Tip: If your appeal name contains spaces, replace each space with %20 — for example, GIVING TUESDAY becomes ?source=GIVING%20TUESDAY.

Examples:

When donors give through your custom URL, Altru automatically adds the appeal to their donations.

Tip: Always test your custom URL before sharing it with supporters.

Note: A source added at the donation form level overrides any source from the referring URL. If you plan to track donations via a referring URL, we recommend you don't mark any sources as default.

Add an appeal from a donation record

From its payment record, you can manually add an appeal to an existing donation made through online sales.

1. From Revenue, Transaction search, use search criteria to find the donation.

2. From the search results, select the payment to open its record.

3. Under Tasks, select Manage appeal.

4. Select an appeal, then Save.

The appeal displays under the donation's payment record details.

Reminders and best practices

• To automatically add the same appeal to all donations given through a form, configure only one source and mark it as default.

  

• To use a source tag to create a custom URL, the source must first be configured from the donation form's settings.

• If you plan to use custom URLs, don't mark any sources as default. A source added at the form level overrides any source from the referring URL.

• Always test a custom URL before sharing it with your supporters.

• When you configure sources, keep in mind your organization's appeal structure and how donations will appear in your appeal reports.

• In Altru, the appeal displays under the donation's payment record details.

For more information about appeals, see Appeals.

For more information about donation forms, see Donation Forms.

In this release, we made the following enhancements to unresolved online sales orders:

• To help prevent unresolved orders that occur because of failed payments, the checkout form now warns users if they attempt to leave the page while a payment is in progress.

• To help you quickly resolve unresolved orders, you can now subscribe to email alerts and receive notice as soon as they happen.

Payment form warning

Unresolved online sales orders can occur if the checkout form fails to complete a payment. For example, if a website user accidentally closes the page while a payment is in progress, the form may not have captured all required info.

To help prevent these instances, users now receive a warning if they attempt to leave the page.

Note: The form displays the default prompt for the user's web browser. The exact message may vary.

Email alerts for unresolved online sales orders

Email alerts help you track activity on your web forms. Now, you can choose to receive notice when an unresolved online sales order occurs.

To subscribe to email alerts, from Web or Sales, under Configuration, select Email alerts for online sales. Enter your email address, select Unresolved online sales orders, then Save.

When an unresolved order occurs, you receive an email with the subject line: Altru Alert - New online sales order: Unresolved.

For more information, see Unresolved Online Sales Orders.

To make it easier for web form users to create or reset their passwords, web forms now display password requirements. Previously, forms only displayed requirements after a user entered an invalid password.

Passwords must be at least 12 characters long and include at least one number, one special character, and one lowercase or uppercase letter. Passwords cannot contain a user's name, username (email address), or organization name.

For those of you who use custom applications that integrate with Altru, this release includes an important security update. As part of this update, all API requests must now include an Altru database name.

Recommended actions:

• Partners and developers — We recommend you review existing integrations and customizations to verify that an Altru database name is included in your requests. To see a code sample that includes a database name, see the Authentication and Authorization developer guide on our Altru API for Partners resource site.

• Altru customers with custom apps and integrations — It’s possible that no action is needed. However, if your API integration no longer connects after the upgrade, notify your integration partner and reference this update.

For more information about the change, visit Knowledgebase.

Your organization can use applications created by Blackbaud, providers in the Blackbaud Marketplace, someone at your organization, or other approved external developers.

To save time and resources, you can now email tickets from daily sales. Previously, this option was only available for online and advance Sales.

Enable eTickets for daily sales

Note: To enable eTickets, you must have at least one delivery method — such as eTicket — configured to email tickets upon completion of order. If you sells tickets through web forms, it's likely this is already configured. Otherwise, you can add a new delivery method. For more information, see Delivery Methods.

1. From Tickets, select Sales methods, then select Daily Sales.

2. Under Delivery methods, select Add.

3. Select the eTicket delivery method (or any delivery method configured to email tickets). If your organization plans to send a majority of tickets via email, you can set it as the default.

4. Choose a receipt default, then Save.

Email tickets from a daily sales order

Similar to advance sales, the delivery method now appears on the daily sales order screen.

Note: This won't appear on patrons' receipts.

Recipient information automatically defaults to the patron's primary email address. To add or select a different address, select the delivery method, then select Edit. For anonymous orders (those without a patron), you must add recipient information.

When you complete the sale, an email is sent to the patron with a link to the eTickets page. Settings for the email and eTickets page are shared between daily, advance, and online sales. To manage page settings, from Web, select eTickets. For more information, see Design eTickets Page.

The sign in form now displays fields to enter and confirm a user's new password. Previously, users had to select Forgot your password? and follow prompts to reset via email.

This release includes two enhancements to ad hoc queries:

• To speed up data entry, you can now paste a list of values when you use One of or Not one of criteria in query. Previously, you needed to paste values one at a time.

  Tip: Paste list appears for text and number fields when you select One of or Not one of criteria. For example, you can copy and paste a list of Lookup IDs from a column in a .csv file.

• You can now filter on remaining program event capacity or view it in your query output. From Analysis, Information library, add or edit a program query. From the editor, select Program Events, then select Remaining capacity. To query on remaining capacity, add it to Include records where. To view remaining capacity in your query output, add it to Results to display.

To provide an easier, more secure way for non-interactive users to authenticate, you can now create proxy users to integrate your Altru database with other systems — such as a custom application or automated processing task. Proxy users differ from traditional Altru users in that they require programmatic access to your database, but don't need to sign in and perform tasks within the Altru application itself.

In this release, you can now create proxy users for non-interactive accounts. Proxy users:

• only need to authenticate every 365 days.

• authenticate via personal access tokens (PATs) instead of passwords.

• don't require an email address.

• inherit the same system roles as the linked Blackbaud ID.

For more information, see Non-Interactive Proxy Users.

To provide your patrons with quicker response times when purchasing tickets online, web forms now cache data for page loads, program event calendars, and time selectors. As part of these improvements, Altru now limits scheduling program events to no more than 365 days in the future.

For additional security, you can now enable multi-factor authentication (MFA) for web form users.

MFA is an authentication method that provides an extra layer of security during the sign in process. It requires a user provide a unique security code in addition to their email and password.

How it works

1. To sign in to your web forms, a user enters their email and password and selects Sign in.

   

2. Next, the user is asked to verify their identify. To receive a security code, they select Send Code.

   

   Note: If necessary, the user can select This is not my email to update their email address during this step. This option is only available during the initial sign in — to change the email address at a later date, they must contact your organization.

3. The user receives the security code through email and enters the code on the sign in screen.

   

4. The user selects Verify and the sign in process is complete.

After a user signs in with multi-factor authentication, on their constituent record under Online Info, their email status shows as verified.

Enable MFA

Warning: After you enable MFA, it can't be disabled.

After the upgrade, MFA is disabled by default. To enable it, from Web, select User registration settings under Configuration. Under Multifactor authentication setup, select Enable MFA.

You should customize the default content for email messages that are sent related to MFA:

• MFA code email — the message a user receives that contains their unique MFA security code. To customize, select Set up MFA code email.

• Address change email — the confirmation message a user receives when they change the email address for their account. To customize, select Set up address change email.

For example, add your organization's from address and from name so users can easily recognize the sender. You should also add contact info to each message so users know how to reach you for assistance.

To increase security for web forms users, web forms now require stronger passwords and automatically expire after 365 days. The new password policy requires passwords to be at least 12 characters in length with a combination of at least one number, one special character, and one lowercase or uppercase letter.

This release includes an upgraded menu that is more consistent with other Blackbaud solutions and resources.

Blackbaud's EMV-Certified Payment Terminal solution is now available in Altru to all organizations who process payments through Blackbaud Merchant Services. With Payment Terminal, you can:

• Accept contactless payments via credit cards with embedded chips, as well as “tap to pay” technologies like Apple Pay® and Google Pay™.

• Process payments three times faster than with a magnetic swipe device.

• Protect constituents and your organization from credit card fraud with EMV-certified card readers that offer end-to-end encryption.

• Conveniently reconcile Payment Terminal transactions with any other transactions made via Blackbaud Merchant Services.

Visit Payment Terminal resources to get started today!

To ensure quality performance for your instance of Blackbaud Altru, we automatically removed output files that were previously generated by ad-hoc query export processes.

Note: While old output files have been deleted, your export processes remain unchanged.

To prevent unneeded output files from accumulating again, we recommend you periodically remove these. Your organization can set up a global change process that automatically runs and deletes business process output on a regular basis.

To create a global change process that deletes business process output:

1. From Administration, Global changes, select Add.

2. Under Business Process, select Business process output delete.

3. Enter a name and set parameters as needed.

4. When finished, select OK.

To create a job schedule that runs the process automatically:

1. From the global change record, under Tasks, select Create job schedule.

2. Enter a job name.

3. Under Schedule type, choose how often the process should run. If needed, set additional details such as a certain day or time.

4. When finished, select Save.

For more information, see Delete business process outputs globally.

For more information on best practices to keep your database clean, check out our webinars available on demand: 10 Tips for Altru Database Cleanup Part 1 and 10 Tips for Altru Database Cleanup Part 2.