UiPath vs iceDQ: Which is a better fit?

Alexander C.: Hello, my name is Alexander. I am an RPA developer. I give UiPath a four out of five and for more videos like this, please click below. We use UiPath at my company and team to translate data from an [inaudible 00:00:16] systems to the client's system. Normally this would be a manual process. However, using UiPath, we are able to translate from our forms to the client's forms. That would normally be done through an online portal, the robot then inputs all the data that we've retrieved either through an SQL database query or through our own Google document forms and put phones through it into the client's Systems. UiPath is excellent for those who are not solely technically minded. A lot of the processes that we fulfill with UiPath have to come through a business analysts mind and where business analysts are seeing a waste of time. So in theory, robotic, and it'd be hard for them to delegate that, to a technical person. Whereas with UiPath, they can simply create that process themselves, as it's all very low code, very user friendly, and the workflows are quite easy to read. So someone with a business analyst background and point of view can fill that need very quickly and efficiently. I dislike some things about this UiPath. For example, there are still some issues regarding crashing and other bugs that have not been ironed out. For example, if you undo certain things within certain scopes, it will appear like nothing's happening, but you'll come to realize that it's undone something from another scope and you have to go back in searching for that also it does not remember from project to project, what variables you've been most recently using. So you have to go through a very slow interface to go grab specific variables from other packages.