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

Simple engine to pull and process a Transaction from an Orchestrator queueThis engine contains code that will do the following:1. Read a configuration file, by default located in Data\Config.xlsx and output as a dictionary named config2. Calls ProcessLayer\InitAllApplications.xaml, where you should initialize applications3. While there are items in the Queue, read a new Item and process it.<ul><li>3.1 Get Item from queue</li><li>3.2 Execute Process - retry if you run into a AppEx</li><li>3.2.1 Calls ProcessLayer\ProcessTransaction.xaml, where you should input data into your opened applications</li><li>3.2.2 Evaluate Process wb output</li><li>3.2.3 Recover if wb failed with AppEx</li><li>3.2.3.1 Call ProcessLayer\CloseAllApplications.xaml</li><li>3.2.3.2 Call ProcessLayer\InitAllApplications.xaml</li></ul>4. Call ProcessLayer\CloseAllApplications.xaml

A simple workblock engine made in UiPath Studio to process Orchestrator queue items

Senior Software Engineer

Can this framework be extended to work with other types of inputs, like Excel, CSVs, databases etc?

simple and easy Queue framework - The structure is similar to “Local MiniFramework” that handles tabular data.Because it is simple and easy to understand, it is recommended for those who have not mastered REFramework.


Easy approach to handle transaction data of a queue.. :) 

A little bit less readable than reframework. Still not bad.

Queue MiniFramework

Queue MiniFramework

Help

How To