# Stored Procedure Transaction Group **URL:** \ **Category:** Ignition\ **Created:** [September 6, 2024, 1:29pm UTC](https://forum.inductiveautomation.com/t/stored-procedure-transaction-group/95632 "2024-09-06T13:29:54Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [September 9, 2024, 1:58pm UTC](https://forum.inductiveautomation.com/t/stored-procedure-transaction-group/95632/6 "2024-09-09T13:58:05Z")
> [@thidalgo](#): > > the same behavior is expected for Gateway Event Scripts Yes, but if any project has edited/overridden the gateway event scripts resource, any event scripts added to the inheritable project later will not propagate to the leaf projects. Anyways, don't try to define anything but library scripts, Perspective views, Vision windows, and Vision templates in your inheritable projects. Gateway events should only ever be defined in a leaf project dedicated to "background" operations. See this topic for related ideas: > [@Where do/should Gateway Scripts live with respect to an inherited project structure?](https://forum.inductiveautomation.com/t/where-do-should-gateway-scripts-live-with-respect-to-an-inherited-project-structure/83460/3): > > Put all of the logic in project library scripts, in the "universe" project at the root of your hierarchy, if you must. Then, in leaf projects, use one-line calls to the appropriate logic from event scripts and message handlers. (I don't agree with your desire, but this is what you must do to achieve it.) I recommend you not put all your scripts (eggs) in one inheritable project (basket). I recommend a hierarchy something like this: universe ├bg\_common │├gsp │├background1 │├background2 │└we… --- _[View the full topic](https://forum.inductiveautomation.com/t/stored-procedure-transaction-group/95632)._