Task Bot vs Process

​@ManojYadav That’s an excellent question, and one that I just made a video on Automation Anywhere University about. It mostly has to do with business process flow and being able to more clearly replicate that flow to better organize your automations.

But there’s another story. The other story is data.

Processes allow you to start Task Bots, API Tasks, AI Agents, child Processes, etc., and get the data from any point in that Process.

For example, if you have a Process that gets data from a Form, does something with that data in a Task Bot, then it hands off to an API Task to call a web service, then you want to create a report in a Task Bot, you can “grab” the data directly from the Form, the Task Bot, and the API Task, without having to pass it along from Task Bot through the API Task to finally get to the reporting Task Bot. 

It just makes data flow a lot easier. Fewer input and output variables to worry about.

Additionally, a new feature called Split and Merge allows you to run multiple bots in parallel for each Branch of the Split and Merge! (This is done with either a Device Pool or API Tasks. It’s really cool!)

teteeettete