In UIPath we have reFramework (dispatcher, performer, reporter) and the queue/orchestrator splitting the work between bots.
Can somebody please point me to a similar way of doing it in the Appian Academy?
Thank you so much.
Discussion posts and replies are publicly visible
In Appian, the automation model is not structured around the "dispatcher and performer" concept as it is in UiPath. That approach is specific to RPA platforms like UiPath, where queues in Orchestrator are used to separate data collection (dispatcher) from data processing (performer).
Appian, on the other hand, follows a process-driven and low-code architecture. Business logic, data management, and integrations are handled differently—typically through process models, data stores, and smart services—all within a unified platform. There’s no need to separate dispatcher and performer roles.
To get a deeper understanding of how automation works in Appian, especially with Appian RPA and integrations, I highly recommend following the official Learning Path on Appian Academy, where you can explore step-by-step how solutions are designed and implemented.
I think the important difference between UIPath and Appian is, that in UIPath you start thinking about a bot doing something, while in Appian, we start thinking about a potentially complex business process end-to-end. In Appian, RPA is just a bridge to incorporate legacy tech into such a process.
David Jimenez Stefan Helzle - thank you so much guys. As you suggested I'm following the official learning path, hopefully will achieve the same kind of knowledge that I have in UIPath.
Hi,
Appian doesn't use REFramework or dispatcher/performer models like UiPath.Instead, it uses process models, Appian RPA bots, and robot pools to manage execution and scaling.Workload is managed via Appian Records, Data Stores, and looped process flows, not queues like in Orchestrator.