How Are You Using Business Events Beyond Notifications?

Business events can be used to automate almost anything in Acumatica.

Import scenarios into processing screens

This is situationally a good idea. This does not work well with high volume processing screens. The idea of this is to fill in the gaps where stock processing screens fail. One example that we have deployed an automation on a processing screen is creating purchase orders by sales order. Acumatica creates purchase orders grouped by vendors by default, but not by sales order. So, if this is a requirement, you can solve by creating a business event to run various parameters in the processing screen to get the desired result.

Another example is closing production orders through the Close Production orders screen based on conditions about the production order. Say you need the actual production order costs to be within a certain percentage of the planned cost - You can do that through a BE automation.

Creating GI processing screens. 

This is my favorite. I have one GI automation that assigns various flags to the orders to handle order exceptions. Say if the order is shipping to a certain region, the order is above a certain weight, or if a specific item is on the order which sends the order into a different workflow, then you can create a GI processing screen to ID those attributes about the order and send the orders into different workflows. 

This is really strong for shipment creation. We have deployed this solution many times around shipment creation. 

Another area where this has been useful is printer routing. Based on specific conditions about the shipment/order you can send the order to different printers. We solved this through a hybrid between a customization and a BE.

Printing based on specific sorting conditions.

We have one customer that prints batches of documents twice a day and they needed those documents to be printed based on 3 sorting conditions. Building a GI to define what needs to be printed in that specific sorting and then building a BE to run an import scenario to run the printing action can solve that. 

Creating activities/cases/transactions

BEs are great for creating activities, cases, receipts, etc. automatically. There are many reasons why this type of thing is needed and BEs can solve it.