@balupad141
Even if you try to use some flow as a reusable component, it won't be considered a sub flow. You can call them as another run flow action only.
This way, it remains in one place and communicates with multiple desktop flows, functioning as a reusable component. In the future, if you modify them, it will affect other flows as well, but it won't impact any production bot unless you make changes in dev environment and move the recent updates into production environment.
If you don't want to take any risks, you can copy and paste the same reusable code into your all desktop flow as sub flow. This way, it won't affect other flows.
To sum up, if your goal is to maintain consistency and ease of updates, using the "Run Flow" action to call a centralized workflow is the best approach. If you need to avoid any risk of impacting production projects, consider copying the workflow as needed, but be prepared for increased maintenance efforts.
Thanks,
Deenuji Loganathan 👩💻
Automation Evangelist 🤖
Follow me on LinkedIn 👥
-------------------------------------------------------------------------------------------------------------
If I've helped solve your query, kindly mark my response as the solution ✔ and give it a thumbs up!👍 Your feedback supports future seekers 🚀