Agreed we have several custom business rules that create popups such as if a donor has a child, grandchild or other family member who was dismissed or withdrew from our school.
We need to be able to push messages to our fundraising team when, for example, a donor has recently made their first gift, or someone is one of our top 15 donors, or someone has recently been engaged by a patient liaison, etc. This is a database view feature that needs to be replicated in web view, please!!
Adding a comment to this one as I was quite disappointed with the response that the mention of business rules were met with in a recent Connect for Success session. Developers seemed to think that business rules= "pop ups for pledge reminders", when there are so many other situations that they are used for.
The most important feature of business rules is the ability to set them ourselves, based of queries of changing information that we deem important and necessary within our database and workflows. Replacing business rules with some generic popups for more "common" situations (as defined by developers, not database managers- and which differ between organizations anyways) is simply not enough- the ability to customize based off of the unique database of the client is critical to workflows.
First of all, can we please consolidate a few ideas into this one, so that this has more votes and more comments in one place? When they are separated, they dilute the level of importance, and users are clearly interested in this functionality:
Business rules are best used for data that frequently changes – things like the giving level for a donor, board membership (often a constituent code), a record with no valid address, possibly a solicit code that needs to be raised in importance lest it go unnoticed, etc. These are important to all staff, but to fundraisers in particular. They do not want to – nor should they – need to poke around on various tabs to see important information surfaced.
In the meantime, webview was designed for fundraisers. So a key tool that will help them do their jobs better is not available.
The result of this missing functionality is that database managers end up hard-coding something on a constituent record – often a constituent code – in a way that makes this key information “more visible in webview”. Adding codes to a record to represent data that frequently changes is a losing battle. The database manager will never be able to keep up with this information and it is ridiculous to force them to do so. If they have no choice because management insists, it will constantly be out of date, they will be working harder and detracting from other important work. The trust in the data, the database, and potentially in colleagues will continue to erode.
This is forcing people to work harder, not smarter. It collides with the goals you state in PUBs.
How is this still not a thing? My development staff primarily use webview, and I'm just starting to get them to use opportunities instead of excel spreadsheets to track their interactions and goals. I set up rules to alert them when they were in a record of someone with an open opportunity or if they were going to add an action to remind them to link it to the proposal, but those alerts only show up in DB view. I don't need the reminder, they do! How is this utilized on one side and not the other? PLEASE make this functional.
This seems like an obvious feature that should be included in web view! Big oversight, especially since BB is trying to drive users to make more and more updates through web view instead of db view. If that's the direction they want this to go, these types of alerts need to be available in both systems.
This would be a much needed addition to NXT. Not having this option really defeats the purpose of the way we use Business Rules as 99% of my colleagues ONLY use the web based view not the Database view.
We used business rules to notify staff about specific aspects of constituents. Please make this available so our fundraisers can have all the information they need in the web view of RE NXT.
In addition to helpful end-user business rules like alerting an end user that a constituent is deceased or shouldn't be contacted, we have a number of business rules pertaining to legal actions that prompt users to not provide certain information or to contact certain constituents. It would be helpful if this was available in web view.
If business rules don't function in NXT what is the point of setting them? This should not be just an "idea", it is a problem and Blackbaud should treat it as a problem.
I just stumble on business rules not working in NXT. In database view we used to warned user not to create mulltiple emails under the 'email' type and use types 'email1', 'email2' and so on.. The warning popsup in database view but not in NXT. We discovered that when our queries started to output duplicates (multiple emails under 'email' type). And no warning for our users. I am new to BlackBaud but even if there should be a new design on business rules in NXT, we should have in the mean time the same pop-up in NXT than database view. It should be fairly easy to create for your developers.
This would be very helpful to have as an available option in NXT. We don't have a lot of 'pop-up alerts', but the ones we have would be very useful to be able to also see in NXT.
Please merge with this idea. https://renxt.ideas.aha.io/ideas/RENXT-I-2261
Agreed we have several custom business rules that create popups such as if a donor has a child, grandchild or other family member who was dismissed or withdrew from our school.
We need to be able to push messages to our fundraising team when, for example, a donor has recently made their first gift, or someone is one of our top 15 donors, or someone has recently been engaged by a patient liaison, etc. This is a database view feature that needs to be replicated in web view, please!!
This would be extremely useful.
Adding a comment to this one as I was quite disappointed with the response that the mention of business rules were met with in a recent Connect for Success session. Developers seemed to think that business rules= "pop ups for pledge reminders", when there are so many other situations that they are used for.
The most important feature of business rules is the ability to set them ourselves, based of queries of changing information that we deem important and necessary within our database and workflows. Replacing business rules with some generic popups for more "common" situations (as defined by developers, not database managers- and which differ between organizations anyways) is simply not enough- the ability to customize based off of the unique database of the client is critical to workflows.
Hard to believe this idea has existed for 8 years, has over 500 votes, and still has not been implemented. This would be such an easy win.
This would be extremely useful.
First of all, can we please consolidate a few ideas into this one, so that this has more votes and more comments in one place? When they are separated, they dilute the level of importance, and users are clearly interested in this functionality:
https://renxt.ideas.aha.io/ideas/RENXT-I-5045
https://renxt.ideas.aha.io/ideas/RE7-I-6112
https://renxt.ideas.aha.io/ideas/RENXT-I-1261
https://renxt.ideas.aha.io/ideas/RE7-I-1612
https://renxt.ideas.aha.io/ideas/RENXT-I-1650
https://renxt.ideas.aha.io/ideas/NETCOM-I-348
https://renxt.ideas.aha.io/ideas/RENXT-I-3091
As for my comments….
Business rules are best used for data that frequently changes – things like the giving level for a donor, board membership (often a constituent code), a record with no valid address, possibly a solicit code that needs to be raised in importance lest it go unnoticed, etc. These are important to all staff, but to fundraisers in particular. They do not want to – nor should they – need to poke around on various tabs to see important information surfaced.
In the meantime, webview was designed for fundraisers. So a key tool that will help them do their jobs better is not available.
The result of this missing functionality is that database managers end up hard-coding something on a constituent record – often a constituent code – in a way that makes this key information “more visible in webview”. Adding codes to a record to represent data that frequently changes is a losing battle. The database manager will never be able to keep up with this information and it is ridiculous to force them to do so. If they have no choice because management insists, it will constantly be out of date, they will be working harder and detracting from other important work. The trust in the data, the database, and potentially in colleagues will continue to erode.
This is forcing people to work harder, not smarter. It collides with the goals you state in PUBs.
It is an essential tool for Web-view users and has to be available in RE-NXT.
How is this still not a thing? My development staff primarily use webview, and I'm just starting to get them to use opportunities instead of excel spreadsheets to track their interactions and goals. I set up rules to alert them when they were in a record of someone with an open opportunity or if they were going to add an action to remind them to link it to the proposal, but those alerts only show up in DB view. I don't need the reminder, they do! How is this utilized on one side and not the other? PLEASE make this functional.
This seems like an obvious feature that should be included in web view! Big oversight, especially since BB is trying to drive users to make more and more updates through web view instead of db view. If that's the direction they want this to go, these types of alerts need to be available in both systems.
This would be a much needed addition to NXT. Not having this option really defeats the purpose of the way we use Business Rules as 99% of my colleagues ONLY use the web based view not the Database view.
We have popups like this also, so this would be very helpful to me.
Please fix ASAP. It looks to me like lots of your database users need this function including ourselves. Thank you
We used business rules to notify staff about specific aspects of constituents. Please make this available so our fundraisers can have all the information they need in the web view of RE NXT.
In addition to helpful end-user business rules like alerting an end user that a constituent is deceased or shouldn't be contacted, we have a number of business rules pertaining to legal actions that prompt users to not provide certain information or to contact certain constituents. It would be helpful if this was available in web view.
If business rules don't function in NXT what is the point of setting them? This should not be just an "idea", it is a problem and Blackbaud should treat it as a problem.
Hi All,
I just stumble on business rules not working in NXT. In database view we used to warned user not to create mulltiple emails under the 'email' type and use types 'email1', 'email2' and so on.. The warning popsup in database view but not in NXT. We discovered that when our queries started to output duplicates (multiple emails under 'email' type). And no warning for our users. I am new to BlackBaud but even if there should be a new design on business rules in NXT, we should have in the mean time the same pop-up in NXT than database view. It should be fairly easy to create for your developers.
This would be very helpful to have as an available option in NXT. We don't have a lot of 'pop-up alerts', but the ones we have would be very useful to be able to also see in NXT.
Could someone from Blackbaud respond as to the status of this idea????