# Whats your process flow like? **URL:** \ **Category:** Ignition\ **Created:** [October 29, 2024, 5:40pm UTC](https://forum.inductiveautomation.com/t/whats-your-process-flow-like/97913 "2024-10-29T17:40:29Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![drewdin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/drewdin/32/3363_2.png) [@drewdin](https://forum.inductiveautomation.com/u/drewdin)\ **Post date:** [October 29, 2024, 5:40pm UTC](https://forum.inductiveautomation.com/t/whats-your-process-flow-like/97913/1 "2024-10-29T17:40:30Z")
I'm curious to your standard design process flow, with having a global project, a scripting project and then my other projects. I tend to have three to four designers open, its a bit clunky and I try to close what ever I am not using but my screens are busy. Whats your process flow like? Any tips or suggestions? ---
**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:** [October 29, 2024, 5:45pm UTC](https://forum.inductiveautomation.com/t/whats-your-process-flow-like/97913/2 "2024-10-29T17:45:45Z")
I avoid directly opening inheritable projects. Just leaf projects. If an inheritable resource needs to be updated, I override in the most convenient leaf for testing (or a new leaf project), and then send the finished resource back to the inheritable project after testing. (There should never be anything but project scripts and UI resources in inheritable projects.) ---
**Author:** ![drewdin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/drewdin/32/3363_2.png) [@drewdin](https://forum.inductiveautomation.com/u/drewdin)\ **Post date:** [October 29, 2024, 6:04pm UTC](https://forum.inductiveautomation.com/t/whats-your-process-flow-like/97913/3 "2024-10-29T18:04:56Z")
do you break up your global scripting project with folders for each project? That's where I have the most back and forth. I have my project scripts that are called in tag change scripts, etc... ---
**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:** [October 29, 2024, 6:11pm UTC](https://forum.inductiveautomation.com/t/whats-your-process-flow-like/97913/4 "2024-10-29T18:11:43Z")
> [@drewdin](#): > > tag change scripts I minimize use of tag event scripts, due to the thread pool overload hazard. Only events defined on the tag need the global scripting project, so only pure tag actions go there. Tag Change Event scripts in a project do not need the global scripting project. See this topic: > [@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… ---
**Author:** ![drewdin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/drewdin/32/3363_2.png) [@drewdin](https://forum.inductiveautomation.com/u/drewdin)\ **Post date:** [October 29, 2024, 6:19pm UTC](https://forum.inductiveautomation.com/t/whats-your-process-flow-like/97913/5 "2024-10-29T18:19:22Z")
Thanks, I was reading that and another post. I have a UDT and the simplicity of calling the script from a tag change in UDT made it easy. I see that its better to run the tag event script outside of the UDT, its just more configuration. Thanks again ---
**Author:** ![drojas](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/drojas/32/3403_2.png) [@drojas](https://forum.inductiveautomation.com/u/drojas)\ **Post date:** [October 29, 2024, 7:47pm UTC](https://forum.inductiveautomation.com/t/whats-your-process-flow-like/97913/6 "2024-10-29T19:47:39Z")
If you have multiple projects, I do tend to create a separate Alarming project that only contains all the alarm notification pipelines needed. Another project for gateway scheduled/timed scripting actions. Another project for Reporting and scheduling, another project for front-end administration of users (such as creating users in your Identity Provider for example). All this to minimize updates to the main project your users interface with all day.