Automation Anywhere Vs Uipath.
Automation Anywhere and UiPath are two of the best RPA tools that keep on dominating the market. Having used both of the tools, I will share my experiences whilst my learning journey.
I began my journey with Automation Anywhere by completing the course on Automation Anywhere University website and did all the tasks the trainers were demonstrating. I did all my tasks on Automation Anywhere Community Edition, which is available and accessible to all.
This made my learning smooth.
Automation Anywhere is beginner friendly. A limited number of packages are present in the control room (where bots are created). If we desire to import other packages we have to download them from the bot store and then import in the control room.
Just like Automation Anywhere, I began learning UiPath by enrolling in the Automation Developer course. I installed UiPath studio and began creating the bots as instructed in the course.
Below are the comparisons that I can make from my learning process.
|
Automation Anywhere |
UiPath |
| Automation Anywhere Community version is Cloud based. | UiPath is required to be downloaded and installed on the system. |
| Automation Anywhere is Java Based. This makes it easier to learn. | UiPath is based on the .NET framework. If you are someone who is well versed in .NET, learning UiPath will be a piece of cake for you. |
| By look and feel it is easy to develop a bot in Automation Anywhere. Each action seems to be very compact on the main window after using, that makes the code more readable comparatively. | UiPath actions don’t provide much readability even if the view is collapsed. |
| We can break down a process into sub-processes and create smaller bots for each sub-process and then link all of these sub-bots together via a masterbot and call each of these sub-bots one after one from the master bot. | We can create and invoke multiple workflows within one project. |
| Automation Anywhere is less supportive in terms of anchors. | Anchors are not mandatory but it is easy to indicate anchors which improves the element selection methods in Uipath. |
| Automation Anywhere doesn’t show the recently used activities/actions. | UiPath has a separate section under actions where recently used activities are mentioned. |
| Automation Anywhere has message boxes to display on-the-fly results. | Apart from message boxes, UiPath has logs to send the messages to the terminal panel. These logs have log levels to indicate if the message is some error, warning etc. |
| Automation Anywhere has more organized options within a single Loops’ package. | UiPath has categorized its loop activities to different packages/groups which makes it difficult to find an appropriate looping activity sometimes. |
| By default Automation Anywhere has more packages in the control room. | By default UiPath has fewer packages than Automation Anywhere in their Studio. |
| We can add comments before some action. | For every action used, annotations can be added. |
| Each action used has a compact view. | Each action has an expandable card-like view, which can be collapsed. |
| We need to provide a full path of all files,folders, application exe’s used. | Files, folders, Apps used may be bought into the project folder and the paths used can be relative. |
| If Excel is not installed on the system, excel basic packages can be used and not excel advanced. | If Excel is not installed on the system, Excel application scope can’t be used. However, excel workbook activity can be. |
| Automation Anywhere supports multiple scripting languages like Python, JavaScript, Vbscript. | UiPath supports vb scripting, c#, python scripting. |
| Automation Anywhere is easy to learn, easy to use. | UiPath has predefined frameworks that require more of the technical expertise. |
| Automation Anywhere doesn’t support integrations directly. Credential settings are required every time. | UiPath supports third party applications integration with other tools like Gmail. |
| Automation Anywhere has just one single UI component, which acts as the control center as well as the development environment. |
UiPath has multiple Ui components.
|
| Automation Anywhere identifies elements captured using Xpaths. | UiPath uses AI based selectors, either fuzzy or strict. |
| Automation Anywhere has an inbuilt version controlling system. | UiPath supports integration to Git, TFS and SVN for version control. |
| Automation Anywhere has only one development environment, and that is for developers. | UiPath has UiPath Studio for / Studio X business users |
| Importing packages that aren’t in the control room by default is difficult. | Importing new packages is easy as the studio auto imports it, after install is clicked. |
| Same elements being used through multiple processes need to be updated individually for all instances, incase of some update or change. | UiPath provides the flexibility of UI Libraries, which help in capturing some element, and reusing it anywhere we want. Change in the element in the UI library will be reflected through all the instances of that element. |
| Testing is done by creating multiple cases externally and modifying code accordingly. | There is a separate functionality for testing workflows/Bots in Uipath. |