UiPath Documentation


Please use the following links to browse the documentation:

Orchestrator - https://orchestrator.uipath.com/
Robot - https://robot.uipath.com/
Studio - https://studio.uipath.com/
Activities - https://activities.uipath.com/
The Orchestrator and Studio documentation contain all the versions starting with 2016.2. Change it from the left drop-down list.

Orchestrator API Guide :
You can make requests directly in Swagger Guide, using https://platform.uipath.com. Request examples are automatically built in cURL, Node, Ruby, JavaScript and Python.
c#, swift, go and objectivec are also supported, but not displayed.

Best Practice Guide: UiPath Automation Best Practice Guide 05 25012018.pdf (1.5 MB)

Detailed learning materials?
Documents on Ui Path
V2018.2 Release for Community
UiPath v2017.1 SP 1
UiPath exploration

Hi Thank you for your post.

Is there also an Orchestrator Architecture document for version 2017.1?

Kind Regards,


Broken Link :


@ovi Looking for the above link. Wanted to know how feasible it is to migrate 2012 Sql Express 2016.2 Database to 2012 Sql Server Enterprise Edition for 2017.1 database(on a different server). Can it be done during the installation process and can I expect the data to be moved?


Hi Vinay,

Please check now, doc team has just fixed the link.


Excellent! Thanks. @docteam




Is Generate Connection String feature in image supposed to be visible on the Robot screen? The link at the end is broken.



Broken. Fyi I get 10$ for reporting every broken link.:wink:



Sure thing, you’re now promoted to Documentation Police Officer :joy:

Thanks for letting us know!


Broken link



Yeah, i think it’s because the guides for 2018.1 have been added today and the links are slightly changed.
Try with this one https://orchestrator.uipath.com/v2017.1/docs/about-upgrading-and-migrating-to-20171


In a production environment is it necessary to have orchestrator, SQL server and indexer, for orchestrator v2018, on different servers or some of the components can be clubbed together, like orchestrator and SQL server, on one server and indexer on a different one etc?
Also, is it necessary to have a separate indexer, like elasticsearch, or can just database logging suffice?


The elasticsearch component is really what you want to derive out from your logs - dashboards, reporting, or a means to quickly search through your logs. SQL is sufficient, but you will soon find that you are reaching capacity when you try to log too much things. If you are log-light, and operationally don’t requires alot of searching through logs, you can probably skip it. Having operate with it, I find that providing much more information than the vanilla dashboards on Orchestrator.


thank you!