Essential!!

This is critical. Help us keep our data clean with this fix.

I've referred to NXT as the Wild West as it is VERY difficult to lockdown the level of detail that you need with the current security settings and business rules would help some of this. They help keep the integrity of the system to an acceptable level that eases routine maintenance.

This is so essential for data cleaning!!! I can't highlight enough what a timesaver this feature is, or the level of manual bloat (plus manual errors) it would create if Database view is sunsetted and we don't have this!

This is huge. We should not have to train every staff member on every possible variation of what to do with data (such as all the things to update after a constituent death), but we have also utilized business rules for special circumstances for record handling. For example, we have a constituent code for our board members and a business rule that notifies staff that all board members' gift acknowledgements should be hand-signed by our org president. Business rules MUST be carried over from DB view to web view.

So essential!!!! So critical to accurate data entry and donor relations.

Sunshine's list hit most of those we use. We have one for records soft-credited for pledge on another record, board/cmte member, check annotation on record before entering gift...

This is really important for us.

In addition to the list that Sunshine provided. Here are a few more:

• Ability to change the batch number that is auto generated

• Ability to configure a pop-up of a constituent meets certain criteria. Specific attribute, invalid address, anonymous, open pledge, open recurring gift, open registration just to name a few.

Custom gift entry business rules that I have used to maintain data integrity (found at Config-Business Rules-User defined rules-Constituent/Gift:

• Constituent that has an open opportunity/proposal (possibly link opportunity to this gift)

• Appeal and Package code for recently assigned appeal

• Constituent prefers email acknowledgement (from a solicit code)

• No letter (from a solicit code)

• Letter code: First gift

• Letter code: Second (third, fourth, etc.) Gift (the org had different letters for donors who gave multiple gifts throughout the year)

• Constituent is attending/attended recent event (to catch event registration payments or donations that weren't noted on the check or online gift)

• Soft credit other constituent for this gift (for special case soft credit)

• Do not add gift to this constituent, use this [other record name and id] (special cases)

• Constituent has no valid address or is inactive (important for letter coding and possible address update from return address on gift envelope)

• Deceased constituent

• Widow - double check addressee (also helps prevent incorrect record updates when widow continues to use joint checking and address labels with the late spouse's name)

• Do not acknowledge (for specific types of gifts/donors)

• Credit Jane Doe for this gift (when a fundraiser is assigned to a club or organization, but not their specific members/employees)

• Update prospect constituent code (when a prospect gives a gift)

• There are three different Susan Smith records, please check backup carefully

Canned gift entry business rules that are important for gift entry:

• Outstanding pledge balances (Config-Business Rules-Batch options)

• Outstanding recurring gifts (Config-Business Rules-Batch options)

• Outstanding registration fees (Config-Business Rules-Batch options)

Note that in database view, users can search for the pre-loaded constituents in a gift batch created through Online Express, allowing all applicable business rules to pop up.

🚨 If you voted for this idea, please include your specific use cases in comments here (even if they were stated by someone else).🚨

I noticed that business rules for gift entry were noted "not planned" in this blog post: https://community.blackbaud.com/discussion/85075/blackbaud-raiser-s-edge-nxt-grid-view-batch-town-hall-1-your-questions-answered

This is disappointing to say the least, especially since we were previously told this was going to happen before database view sunset.

Please bring this over! We use them all the time as reminders during gift entry to check for open proposals, which is critical to moves management. We use them to denote Board and VIP records, spouse vs. HOH records, deceased records, etc. Business rules are a core functionality.

We use Business Rules to prompt data entry staff to review recent actions/proposals/notes if the constituent meets certain criteria. Since there is no prompt to apply a gift to an active proposal, we must use Business Rules. If we don't have tools like this, we stand to weaken the integrity of our data and/or increase the amount of time data entry must read through the details of a constituent record during gift entry. Both make RE less efficient and less useful.

Coming here again specifically because of this town hall question response:

Will we be able to create or amend custom business rules?

Business rules are not currently planned. However, we welcome feedback on how you would like to use them within the new batch experience.

The ability to create business rules across the system means that you can build in reminders for gift entry for specific constituent situations. It aids in data integrity (see Sunshine's response), and makes it less likely that entry will happen incorrectly. I cannot believe that Blackbaud isn't even considering a highly used, very depended upon feature that has 896 votes in the Idea Bank. That is a mistake. There are ample examples from everyone who's commented here to make a case for retaining that functionality in webview.

Yes, I agree with the comments here. Having Business Rules to gently nudge users with a helpful message is good for data quality.

We use business rules to notify if the constituent is a monthly/recurring donor if marking them deceased or no valid address.

See also: https://renxt.ideas.aha.io/ideas/RENXT-I-8653

Specific need: The duplicate phone/email options business rule is important for data integrity.

Below are the options from database view-Config-Business Rules-Constituent options-Phone/email options:

When saving a record with duplicate phone types:

• ☐

  Do not allow record to be saved

• ☐

  Display naming

• ☐

  Save record anyway

When saving a record with duplicate email types:

• ☐

  Do not allow record to be saved

• ☐

  Display naming

• ☐

  Save record anyway

We use business rules for gift entry to keep reporting accurate and consistent. Such as only entering gifts on Head of Household constituents. In DBV, not matter if I am entering a single gift directly on a constituent record or in a batch, I get a pop up telling me they are not the HOH so I can swap to the correct constituent. Or to make sure I am not entering a gift in a batch for a deceased constituent.....easy to do as a Catholic school with multiple generations all with the same name. That pop up has saved me many times. Business rules are also not optional for us.

We relay on business rule popups for very important notifications which allows us to use annotate for more timely notifications. Business rules are NOT OPTIONAL for us. Core functionality like this is essential if web view is ever expected to be the primary UI for RE.

we rely on business rule popups, for example flagging if a constituent lives out of country, or if a recurring gift lives in an external system so that required actions are completed.