Hello,

Until recently, (if I'm correct) you could simply write a single Deluge customization in Books or Inventory that would trigger regardless of whether the associated record was created (or edited) in Books, Inventory, or Commerce.

Sadly it appears that this is no longer the case - and without any apparent communication of this change to the user-base (at least none that I ever came across).

And so despite the fact that such data is commonly shared between all of these linked applications, it now appears any new or edited item, invoice, sales order, estimate etc. will only trigger Automations  and Flows in Books if it was specifically created or updated in Books, and only trigger Automations and Flows in Inventory if created  or updated in Inventory, and only trigger Flows in Commerce if created or updated in Commerce.

Because of this change, users are now forced to replicate the same scripts so they are present in Books and inventory, or adapted to trigger a Flow for Commerce.

Why reason would there be for this change as it only creates an increased likelihood for error?

Imho, it would be much preferred if either:

A) Customizations written in Books or Inventory would go back to the original implementation and continue to  trigger off ALL new orders in the system (as it previously did), and simply include a filter to allow the user to determine the trigger to only respond to new orders by Commerce, Books, or Inventory if that's the intention.

or 

B) Alternatively, simply have a common pool of Deluge customizations that should simply be shared among all three apps (along with any others that also share the same data resources).  Similar to A, a filter could simply be added if a user only wants to affect records that were instantiated by a specific application instead of all of them.

-Bryan