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.

We use business rules on the backend on a daily basis for gift entry (e.g. a business rule flagging when a gift is being entered on a constituent that has an opportunity, is marked inactive or deceased, no valid address, etc). These are based on queries that cannot be replicated with a specific one of use of annotations or notes- the full functionality of business rules is critical.

In addition to the comments from other folks, which I whole-heartedly agree with, many organizations have such long-standing business rules that they are functionally invisible. This means it will take even savvy users a while to realize that they're not operating and need to be managed differently in web view. But as everyone else has said, business rules allow lean teams to standardize data entry and enforce operational rules without needing a team constantly monitoring 15 different data entry points. This is a critical feature for functional system use.

Business rules are NOT OPTIONAL for us. They make everyday data entry go smoothly and accurately. Now using Omatic Cloud and seeing that business rules are not available, all our data is going down the drain. Why in the world would any company take features away when updating their system? Business rules is not a "cute addition that's fun"; it is a crucial mandatory necessity to our organization. Please, consider this for all your users!

Need database view business rules to apply in web view. Getting multiple emails and phones of the same type.

I rely on business rules in db view and feel they are a key feature needed in webview!

I am looking for a similar idea in the gift section, but it appears that an idea there was merged with this one (https://renxt.ideas.aha.io/ideas/RE7-I-6112). When adding gifts to a batch, there are important gift and constituent business rules that need to be shown. Please address this before removing batch from database view.

I have created a business rule in DB and it does not push through to Web View.  Please can you let me know how to do this

You can already create an Alert in NXT that shows up as a pop up in DB side - So just set up business rule pop up in DB to push through to NXT side as an Alert.

Utilizing a business rule query group this way removes unnecessary time spent on individual manual entry into NXT. 

In our organisations we have a business rule that each constituent should have a constituency code. Database view does not allow you to save a record without, NXT does. This is creating so many issues with data integrity!