I have 10 individual projects, each one is a “robot”, some depend from a choice. For instance I have project 1. If the answer to project 1 is yes, it should run project 2, else it should run project 3. But then, In project 3, if the answer is yes, it can go back to run project 2, but if the answer is no, it runs project 4, and so on. It’s a big project and I’ve decided to make small projects of the several actions, so the debug would be easy. Can someone help me decide the better way to join them ? Flowchart? Invoke? Switch ?
Hi, @Celia_Roque1 You can handle this easily by using a Flowchart as your main controller and Invoke Workflow File to call your smaller projects.
Flowchart is great for Yes/No logic, and invoking workflows keeps each part modular and easy to debug. Just pass data through input/output arguments as needed.
In short: use Flowchart for logic and Invoke Workflow for execution. It’s clean, scalable, and works perfectly.
Hi @Celia_Roque1
You can create a Parent flow in the parent flow you can use Invoke process to run that smaller process one by one.
Welcome to the communtiy
Flow chart with multiple invokes for each procedure would be the best option
Cheers
You can convince the projects into one but I would suggest to analyze and think through about how you will handle retry, error handling etc.
Remember this will overcomplicate the bot.
Hey @Celia_Roque1,
if possible, please provide a process diagram. I’m pretty sure that will help us give you better advice on how to tackle your situation.
Best regards