We were founded in 2005 in a tiny apartment in Bucharest, Romania as DeskOver.

Fittingly, it was a customer who, in 2012, first saw the immense possibilities for us in the fledgling RPA market. Our desktop automation product launched in 2013. In 2015, we introduced our enterprise platform along with our new name.

Today, UiPath is the fastest-growing enterprise software company in history with scores of offices, thousands of employees, partnerships with the world’s best consulting and BPO firms, a 500,000-strong developer community, and 5MM+ robots at work in over 5,000 global enterprises.

Our mission is to deliver the leading Robotic Process Automation platform to our clients for an automation first mindset.

We build software robots that automate repetitive processes. Our software robots take on the tedious, mind-numbing work and free people to do the more stimulating, creative work worth doing.

But no matter how much we’ve grown, one thing hasn’t changed. We’re still building a company we love to work for

Tripartite Process ModelRobotic Enterprise FrameworkMany business processes in the enterprise world follow this pattern:<ul><li>Some Excel files come by email</li><li>Actions required for each row</li><li>Updated Excel files sent back</li></ul>To automate this kind of process with UiPath, we split it in three phases:<ol><li>Monitor email, download attachments and upload data to Orchestrator queue</li><li>Process items in queue with several robots in parallel to keep up with volumes</li><li>Assemble data back to Excel files with new info/status and send them back</li></ol>Leading phases 1&amp;3 can be executed by a single robot in one&nbsp;Dispatcher&nbsp;process with a recursive schedule.The main&nbsp;Performer&nbsp;structure handles application interaction and status updates in the 2nd phase.See User Guide for more details.

A lighter version of Robotic Enterprise Framework ready to run with Excel & Queue input data

Amatarh

Hello, I am a little confused about the structure of this project. The dispatcher and the performer are part of the same project but I think they should be separate. When I publish, I think a project con have only 1 entry point. Each folder in this project has a main. If I wanted 1 robot to run the dispatcher and 1 to run the performer wouldn’t that be 2 projects?

Lite ReFrameWork

Lite ReFrameWork

Help

How To