Fine then
Let’s go one by one
Dispatcher is a bot that we create to load some data into the queues/datatables. This data can be later used by another bot called as Performer.
Basically, it is breaking one single big bot (having both functions of loading and performing) into two pieces. One bot loads the data & the other performs over it.
So if you have got a process where it first fetched the input data from a resource and then process it later then use dispatcher and performer concept
Or
If you have a process which is used to keep the input ready for other multiple process then use a single dispatcher process to create new queue items as input so that it can be picked and processed by multiple performer bots
First scenario - you have one bot to fetch input and it has to be used by multiple other processes
Then use one dispatcher process and have multiple other processes called performer to process those data
Second scenario - you have one process where we need to fetch the input and validate and then only process
In that case use a dispatcher to fetch and upload the data ready in a queue or excel or keep the input anywhere readily
Then use a performer process to pick that input, validate and then process it
Yes ofcourse we can keep
But it is always to have two different process where at the end of the first process [Dispatcher] use a START JOB activity and call the second performer bot so that they will be ran one after the another in sequence
Hope this would help
Cheers @georgecristian.ivan