Microsoft Power Automate Reviews

I use both the on-premise version and web versions because they both have different tools. I use them both for different use cases and different scenarios.

I use Microsoft Power Automate to make reports and web scraping. I automate the reports with the desktop version because it works well. I use Microsoft Windows, to do some commands in the CMD, also known as the line assistant. When it comes to the web version, I mostly do reminders, scraping, extracting data from emails, and creating ticket systems. I take that data and put it in a list or create a table in Excel to extract information and automate that part. 

Microsoft Power Automate has helped our organization by making processes faster. I do some consulting on the side about Microsoft Power Automate. We realize we don't need as many people to work on something because you can automate it or at least semi-automate the tasks.

The most valuable feature of Microsoft Power Automate in the desktop version is web scraping because you can do a lot with it. I work in retail and you can study prices changes, which can give you a lot of information. The solution is no code which is a large advantage.

In the web version, the most valuable features are creating tickets, taking email information, and creating a ticket with it, similar to an IT ticket.

Microsoft Power Automate is a tool that is easy to learn. There is some basic logic that you will have to understand but overall it is not complicated.

I think the language Microsoft Power Automate uses when you do expressions could be better. What they use is not a popular programming language. It would be better for Microsoft to find a more popular programming language, such as Python. It would take away the whole no-code aspect of the solution but you don't need to write that many lines of code to improve something in a process. Instead of no-code, they could be a low-code environment.

I have been using Microsoft Power Automate for approximately seven months.

The stability of Microsoft Power Automate is good, I have not had a problem with the performance.

Microsoft Power Automate is scalable.

We have approximately 10 people using this solution in my organization. The solution is moderately being used. The more you use it, the more ideas come to you of what you can automate or what can you create. In the future, it's going to be used more.

I have not contacted the support from Microsoft.

The implementation of Microsoft Power Automate was straightforward. It took only hours to do the full implementation.

I did the implementation of Microsoft Power Automate in my company. Additionally, I do the maintenance and patching of the solution when needed.

The cost to use Microsoft Power Automate is approximately $15 per user per month, for the basic plan. However, the solution comes free with the Microsoft 365 Suite.

You have to pay extra for the scheduling of the automation tasks.

Microsoft Power Automate is a newer solution to the market. UiPath is a lot more popular and has more features than Microsoft Power Automate. There's a lot of potential in that Microsoft Power Automate because it connects well with other Microsoft programs inside the Suite which makes it even more powerful. UiPath connects with other applications, but the fact that if you use Microsoft in your organization, it's more seamless. It works better. 

I learned Microsoft Power Automate faster because I know how to use Microsoft Excel, and that teaches you how to think more logically when it comes to computers. If you have an Excel or programming background, it's going to be easier because the logic creates the flows. If you won't want your learning curve to be that steep, I would recommend learning Microsoft Excel and then going Microsoft Power Automate. You will have more ideas of what you can do with the tool.

I rate Microsoft Power Automate a nine out of ten because you have to pay to receive the schedule functionality of the automation, which is important.

The solution has helped our company with automation. 

Microsoft Power Automate is an easy-to-understand solution. 

The tool should improve its price. 

I have been using the solution for three months. 

I rate the product's scalability an eight out of ten. 

We haven't activated technical support since it's expensive. 

Microsoft Power Automate's setup is easy. 

I rate the solution an eight out of ten. 

I've primarily used some automations, however, it was just for practice. I automated a few activities here and there. I have not used it extensively. For example, I can use it to read some emails or share files, or pull information from Sharepoint, et cetera. It can help me create new records for auditing purposes. It can pull data to show we are in compliance. 

The most valuable features include its ease of use for automation creation. It's very easy to use. We can go online and watch videos and figure out how to use it. 

It can help us improve many processes and workflows. It helps with efficiencies. 

The functionalities are very similar to other types of languages. It's not hard to learn, which means we'll be able to make more workflows in the future. 

It is stable.

It can scale well.

The solution comes bundled with Microsoft 365. 

I haven't come across any downsides to the solution.

We'd like to see even more free courses to help people learn to automate smarter. 

For countries in our region, it's not very well known. Microsoft has to do a better job of advertising it and how it can help businesses so that it becomes more well-known and widely used. 

So far, the solution has been stable. The workflows have been good. There are no bugs or glitches. 

The scalability has been fine so far. I haven't come across anything that would make me think it wouldn't be. 

We plan to use it more to make more workflows in the future. 

I've never used technical support in the past. 

In our company, we have people looking for new opportunities and tools to help the sales force in automation matters. 

The pricing is not clear to me. I don't deal with that. We have Office 365 and the solution is included in that bundle. 

It's a good product. If a company needs to automate something, it's a very useful tool.

I'd rate the solution eight out of ten.

We could use it more. It's still new to me. 

We are using it for automating legacy systems as well as email verifications. I haven't touched on the APIs yet, but the use case is for user accessibility to and from data sources.

The solution is still in the development phase. It is not in the production run at the moment. Therefore, at the moment, there is not a significant visible improvement.

In terms of deployment, it is a mix of hybrid cloud and on-premises. Microsoft is the cloud provider. It is a single environment deployed over multiple branches in each province of the country. Currently, the version that we are using is the latest Microsoft release.

Its ease of use is most valuable. A lot of the bulk functionality is done either through standalone or custom connectors and standard API processes. 

There are two versions of the automation suite. You've got your cloud functionality, and you have got your on-premises functionality for legacy systems. There are a lot of functionalities between the two systems that don't cross-correlate with each other. A lot of the functionality in the cloud system is not there on the production side in the on-prem system. If they could implement some of the similar functionalities and streamline them for integration, it would be a lot easier. There should be seamless integration between the two systems.

I have been using this solution for three months.

It is highly stable with good performance.

It is extremely scalable. It integrates with a lot of existing systems, both Microsoft-related and non-Microsoft-related, and it is extremely extensible. The additional support validation and software integrations that are available are limitless.

Our experience of the technical support on the solution has been minimal because there have not been a lot of technical issues with the implementation. The turnaround time for any type of technical query is usually a day to two days, but before that time period is up, they either have a solution or a guaranteed workaround.

We previously used Automation Anywhere. We switched because of the ease of use. The functionality of Automation Anywhere is for a very specialized use case scenario. They focus on a lot of areas, but Power Automate has a lot of simpler solutions and easier approaches. For example, we have a solution in place that has three or four RPA scripts for a single process. With the Power Automate solution, we have a single script running for maybe five sub-processes. It is a lot more streamlined and consistent.

At the moment, it is still in development and is a matter of integration. It does require a bit more technical know-how, but it is mainly done from the environment perspective and from an administrative point of view. 

From a development point of view, the crossover is pretty much the same for going, for instance, from Blue Prism to UiPath, or UiPath to Automation Anywhere. There's a transition period level of difficulty. So, from a development point of view, it's fairly the same, but from a technical point of view, Microsoft does require a bit more technical know-how to get the environment set up.

With some of the integration conversions we've done from one platform to the other, from a development standpoint, it has taken us close to a month in the development environments, and this is interrupted. If we had an uninterrupted conversion, I would estimate a maximum of a week. We just need to get it converted and implemented.

We've been doing everything in-house with direct help from a Microsoft representative. We have a single person to take care of it. It doesn't require a massive deployment team.

So far, based on the development calculators that we've been running, it's running far smoother and far more efficiently and faster. So, the estimated return on investment over the past three months that we've been calculating has been looking far higher than the Automation Anywhere solution.

At the moment, from our experience with the two, Power Automate is a lot more expensive solution than Automation Anywhere, but it is also a far more reliable solution. 

With the price increases and with the current pandemic situation going on worldwide, a lot of the prices have fluctuated, but the packages and the all-encompassing features you get with the Microsoft package far outweigh the benefits from the Automation Anywhere side. Each package on the Automation Anywhere side is cheaper, but we need to continuously purchase subsequent packages to continue with our automation to the extent that we require. So, the Power Automate solution is a bit more pricey, but it does offer us a far better range of capabilities.

There are different development plans that you can use. Additional licenses might be required for additional features, such as your Azure Logic or your Dataverse capacity. There is a limited capacity package that you can purchase, and then you have to have an additional license for added capacity.

I would advise paying critical attention to the environment that you're setting up. User access roles, either through Active Directory or through the database control method, should be the key focus. After that, you need to assign roles and licenses as necessary. From there on, you need to integrate the system. 

The Microsoft documentation portal for both cloud and on-premises is going to be the easiest to follow. All the solutions are there. For technical assistance from the Microsoft side, contact details are available on the documentation portal for any type of query.

I would rate it a solid eight out of ten. For me to give it a ten, there should be seamless integration between both the cloud and the on-premises solutions. There should be the exact same or similar functionality between the two to make the entire automation process a bit more streamlined.

It's a pretty big learning curve with Microsoft Power Automate and I'm trying to do a couple of other things. But I really have made some progress. I've actually started creating some bots. I've run into some snags. I haven't found my way out of the snags as yet. That's kind of why I'm not quite ready to publish because I'm not an expert yet, but I am actively working on it.

Microsoft Power Automate is on-premises because I'm using the Power Automate Desktop. So it's a desktop piece that I'm actually using and that's definitely on-premise. What I'm actually doing is interacting with actual systems. I run a clubby cloud system for moving data back and forth.

There are some very long processes that are happening now, where we need to move data from one system to another and do some analysis, and all of that. We're trying to automate some of that process to link the systems together. So some of it is actually reading the webpage, taking information off of the webpage, and doing things with it.

Power Automate is very user-friendly, it is easy to use. I find it very easy to use, easy to follow what's going on, to navigate around and get things done. I really like it. 

One of the features I like is the elements. Let me describe it. With Power Automate Desktop you're interacting with other pieces of software. That's kind of the whole point. You're grabbing information from other software so that you can then pull it together and move it back and forth between systems and do other things with it. Power Automate Desktop allowed me to quickly visually identify parts of a screen and record it. So I can see that I know I'm going to have to click this button here, this field there, and this tab here, and I can literally go and quickly just record all of them and identify them and have them in a list that I can see and say - there's my list of things.

Now when I'm actually pulling the logic together, it's really, really simple to just grab it from my list of elements and just fix things together. So I'm able to move faster than I can with Help and with the other solution. I really, really like that about it. I like its integration with other apps

Well, not integration. Because the whole point of Power Automate desktop is to grab information from other apps. So it's not a side feature, that's what it's designed to do specifically. So, that makes it easier to visually capture information from other applications, and then reuse those fields from other applications. I think it's the reuse that's really useful. Because I can see that I've done it. Whereas with the other one, did they do it or not?  But I really like that it is easy to capture visual elements of other applications and reuse them. 

The other good thing was the trial period. There's a much more realistic trial period of 90 days. So it encourages you to dig in on your own, and try and figure it out, because if something doesn't go right, you don't have to figure it out in 30 days, like all the others. So it's a 90 day trial, which makes sense to me because if it works, trust me, you'll never give it up. You going to use it, going to be hooked anyway, so 90 days make sense.

The problem with Power Automate is what happened when I had it set up to read web pages and Excel workbooks. But that was my first test, and I was working on it for around three days and then took a break of about two days. When I went back to it, all of the Excel, and all the Excel functions, just disappeared. Completely vanished.

I had installed it on my laptop. I had the spreadsheet there and all the features, because you have to do things like tell it to open the spreadsheet, tell it to read the cells, that kind of thing. And then you tell it to go to this webpage, and when you get to the webpage, log in, put in a username and password and then click on a button. So you have to put all of these steps and sort of link them together. And then when I came back, the flow was there, but it said all the steps that had to do with Excel were invalid. Anything that has to do with the web, it just said invalid. The whole tree, all instructions are still there, but the components that talk to Excel and the web were just gone. Just totally vanished.

When I looked up the help, it said that sometimes that happens when you're not connected to the internet. So it was kind of straight forward but complex as well.

It was straight forward, and then it just crashed, essentially. It just went. And I couldn't figure out a way to get the modules back. What on earth? So I switched to HelpSystems Automate, which I had also installed on my machine about a year ago. But now that I'd started working with Power Automate, that gave me the confidence to launch into the other one. So I launched into that one and that's where my HelpSystems Automate review would start. But if I would just stop by Microsoft Power Automate Desktop, that's where I'm stuck. I literally have not gone back to it. I actually find its easier to use. I prefer to use it, but it's just not working. It just stopped working. I don't know how to get this part back.

That's why I told you  I don't want to give a full review as yet because I don't know if it's something I did. I don't think so. But it just stopped. I'm still trying to give it a little grace, trying to figure out, trying to make it work.

What was difficult though, the weirdest thing, was just simple things like manipulating strings.

In terms of what features should be included, what would really help would be more help navigating webpages. What would help would be the help itself - if there would be lots of official walk-throughs. If it would say, for these scenarios, this is how you should do it, with the screen screenshots and the step-by-step thing. With other products I've used, even as a programmer back in the day, nothing ramps up learning faster than walk-throughs. It's not really the product itself, but more walk-throughs to help people ramp up their learning much faster.

That would be really great. Especially around web automation and services automation. Hooking into the EPI's of other solutions would be great. Right now we're just relying on the community of YouTube videos. People just set them up and do YouTube videos, and that's how they're hoping it will get solved.

It's not the type of setup, but it's the training on using the product that I would like to see more of. Better training on using the product itself, walk-throughs in particular, as a training method.

So I tell people that with Power Automate, you you can record the interview, that we're doing here, and fill out the forms automatically. All you have to do is sit down and engage the client with the right questions, and the system would listen to the interview and fill out the screen for you. So you thought, that would be really cool. Now you've downloaded it, and you're trying to figure out how on earth you do it. A walk-through is where you would go and this thing would literally say, "Capture audio and video." They give you a scenario and then they would have a little video that you can watch that shows you how to actually set it up. And then, in addition to that, you'd have a detailed scenario. This is what you want to do. Then it would have all the steps that you would need to actually do it end-to-end. If you follow the steps at the end of the walkthrough, you would actually have a working solution by just following the steps. By doing that, you're learning the product. You're learning how to use it. You learn so many things by using walkthroughs. And it's just training. It's not the actual product itself, it's training that goes along with the product.

This is Microsoft technical support. I'll try them. I haven't called Microsoft technical support in years. It's usually not a very good experience, but I will try. I will reach out to them and see what happens. When you go to support they tend to lead you to communities where other users are having issues. It's sort of, "see what you can find in the community." I will get back to it because I have to desperately get this thing to work. No matter which tool I use, I have to get it to work.

The price is why I even considered it, because HelpSystems Automate was winning all of these awards and was supposedly the easier tool to use. That's what it says. But Power Automate's pricing model had a more gentle incline. That's why I went to the Microsoft Power Automate Desktop in the first place, because the pricing seemed to be more favorable. It the end, once you're using it for the whole organization, you end up paying the same thing for both products anyways. But to get started, Power Automate Desktop seemed better priced. But then it stopped working and I don't know how to get it back working yet.

I'm using the HelpSystems Automate now, and I'm stuck on another step. I mean, it's hard and that's good. If it's hard, it means you'll get paid. So the bit being hard is not the issue. I just have no idea how to get Power Automate to work again. So when I do, I guess I'll let you know.

The licensing was on a monthly basis. I liked it because it gave me a more reasonable per user cost. So I can set up one user like me, and then quickly set up all the workflows that I need, and it allows me to evaluate better and longer. I can onboard two or three other logins at a very reasonable price. Ultimately everybody wants to just dominate the entire organization anyway, and so the price is going to get ridiculous at some point. But by the time it gets there, the organization would be benefiting so much from it they don't mind. Whereas with the other solution, you have to bite the bullet a little sooner.

I think you have to have an office license. I'm not sure actually. Maybe you can just use it by itself, but I'm not sure.

Right now, on a scale of one to 10, I would give Microsoft Power Automate a six since I can't actually use it. I really can't go past six. Maybe once I actually start using it, I'll rank it much higher. I think it has great potential if I could just get it back working.

We use Microsoft Power Automate for various personal initiatives of people to automate their own work.

It is used in a laboratory environment to connect the laboratory systems and to automate the connections between them.

The most valuable features are that it is low-code and simple.

For simple use cases, it is easy to use but as soon as it becomes complex then it doesn't fulfill the requirements.

It doesn't have any OCR capabilities. It doesn't really work with our ERP system, where we can log into the ERP system and have a robot updating it directly.

Microsoft is early on in this game and not really very far yet. They just need to mature their solutions.

In the next release, I would like to see a centrally-governed system, where you can access fully automated processes. This would include the ability to connect to other systems and log into them.

I would like to see it as a centrally managed solution.

I have been using Microsoft Power Automate for six months.

We are using a local partner of Microsoft in the Netherlands, and it's going quite well.

At the moment, we're using both Microsoft Power Automate and Microsoft Power Apps. We also use Kofax.

If you are using it as a user, I'm not aware of how complex it is for setting up central governance on it. But with proper RPA, you very much need the central-governance to ensure that things are conforming to standards. 

As soon as it starts being involved in business-critical use, then governance is very important.

I haven't seen that the central governing of it to be easy.

We use a local partner to help with the implementation and it's going quite well.

I am not aware of the pricing, but the problem is something we run into often. As soon as you want to use a data service, all of a sudden the license cost goes up. 

It's more fragmented licensing, where every little thing that you add, you get an extra license cost.

Microsoft is gradually becoming better, but for RPA, it's not fully there yet.

If you are looking for a low-code, simple to deal with email and extract a spreadsheet, then Microsoft is a good option. However, if you have a complex RPA use case where optical character recognition or PDF ingestion is needed then Kofax is a better choice.

I'm responsible for the center of excellence running Kofax as an RPA solution, and not for the Microsoft Power Apps.

I would rate Microsoft Power Automate a seven out of ten.

We use SharePoint to collect information from tests, exams, and similar things that we do in our office. When people complete the tests, we use Microsoft Power Automate to collect the results and email them to appropriate people. We are currently using the latest version of Microsoft Power Automate. 

Its integration with SharePoint and Outlook is the most valuable. 

I found it very easy to use. I could do everything that I wanted very quickly, and I didn't have any complications at all. I never had a problem in using Microsoft Power Automate.

If someone was just about to start using it, it would be better if it was a bit more user-friendly in terms of understanding function references. I come from a bit of development background. To me, it all makes quite a lot of sense, but someone using it for the first time would probably battle understanding how the functions work. This might be something they could improve on.

It would be really useful if it could publish data to Power BI. We like to use Power BI for our reporting, but we can't directly integrate the data across. If there was a way to automate the collection of the data and push it straight into the Power BI platform, it would be quite useful.

I have been using Microsoft Power Automate for about three months.

It seems to be very stable. It has been running now for about three months, and it regularly gets used, probably about 30 times per day. I haven't had a single missed event. I have received all the emails, and everything works great. Today, funnily enough, I have started building a new solution for something similar. So, I went back and actually checked the records for the last three weeks, and everything was perfect. I haven't had any issues with it at all. 

I am sure that it is going to be perfectly fine for what we need. We are looking at about 30 people using it in one day over the last three months, which is not a very high volume. We are not going to do more than probably a maximum of 50 users a day. 

I did not have any need to contact them.

Previous to this, I used Microsoft Flow, and before that, I used the SharePoint workflow. We switched from Microsoft Flow because Microsoft actually changed their product and went from one to the next. It used to be Microsoft Flow, and then they revamped it and re-introduced it with a new name. I just carried on basically using the same platform. It is better than what they used to have. That's for sure, but I'm still effectively using the same product. They had advertised through emails and other mediums that they have switched to a new product, and it has been rebranded. I thought I'm going to try it, and I just found it very friendly and easy to use. So, I just stuck with it.

It is integrated completely with our Office 365, so I didn't have to set up anything. Everything just works automatically. The security works from the first time. When I logged in, it straight away identified me. I could immediately get a list of all the people to whom I needed to send the stuff. It connected straight away to the SharePoint. I didn't have any problems at all.

The original product was set up by the consultant firm that looks after our IT. We don't do it on our own. They set up everything and configure it. All I had to do was just log in and make sure everything works the way I wanted it to do.

I don't deal with the financial side. I know that we pay for a per-user license. It is probably less than $20 a user, but I am not sure about the exact figures.

To use this solution, you need to maybe brush up a little bit on how to use the function references that are available in Microsoft Power Automate. The code that you use for the functions is a little bit different from what you would use if you were using Excel or anything like that. So, you just need to brush up on how the functions work. Once you understand them, it is pretty simple.

I would rate Microsoft Power Automate a ten out of ten. Everything has been perfectly fine. I am a happy user.

The primary use we have for this product is a solution we created for a client to download daily data from a big company's website. It is a website tool for helping the company monitor the channel for managing their associate or partner responsibilities. They needed to visit the website every day — or as often as possible — so they could get information from the parent company, or collect orders or complaints from there.  

The most valuable thing about the product is that it is simple. When you go into the UI — and probably because Softomotive has about a 20-year long history in the IT industry — there are small details in the features that simplify how you work with it. It has all the big features like competing products but the detail is the kind of thing that makes users feel more comfortable using the product than if the details were not there. So those kinds of ease-of-use details are good things for Softomotive. The design is a GUI interface which is really for non-programmers. There is only the graphic user interface so it is simple to use.  

I think the primary thing that needs improvement in this product is the stability. It looks like it is easy-to-use and that is very nice, but it is more important to have a stable product and not just one that is easy-to-use. If I am working to create a simple process, odd errors occur quite often and in the middle of creating the process.  

The additional features I might like to see in the next release would be adding in some capabilities that other products already have. For example, some RPA process management framework. UiPath has something like that, RE Framework (Robotic Enterprise Framework), which is something in Softomotive we have to develop by ourselves. They have some premade processes in WinAutomation, but in running a process they should have some kind of error handling. For example, if there are tasks that should be run like 100 times and maybe it will freeze up at the 50th cycle, then the process should start again from 50, not from number one.  

If they can come up with some kind of framework and error handling, that will enhance the stability of the running processes made out of their solution. Right now I cannot resolve these main issues on my own and they should be added to the product.  

I started testing it out three months ago and have been using it for about two months.  

The stability of the product is not always good even when working on simple projects. This is not a bad product — I still use it — but the stability is something that they need to improve.  

Scalability is just buying more licenses. I worked for RPA consulting company and a development company and then I worked as an RPA developer. Then I was dispatched to a company to develop a process for that company. That company at the time purchased ProcessRobot, and then recently WinAutomation — I think five copies. They tested it and they are now trying to expand usage.  

I have been in touch with the technical support for WinAutomation by Softomotive a lot, really. The support is good and they provide the information or answers I need.  

I have used other products in the past. For example, by comparison, UiPath might be a little bit more stable but it is also a little bit more complicated in the UI/UX (User Interface/User Experience) than Softomotive. UiPath has not got some of the fancy features — just the basic ones. You just collect your UI elements or web elements and use the basic features. But say you maybe run a process 1000 times in both tools. UiPath seems to me in our testing to have fewer errors than Softomotive. But the complexity of the project or the stability would make me choose one product over the other.  

The setup in WinAutomation is kind of straightforward. I did not experience any trouble in the installation. ProcessRobot is a bit different and then UiPath is a little bit more complicated in the installation, but I think it is manageable as well.  

To actually get the product to work from the point of installation to where I could start running some processes took maybe a month the first time. But this included learning the product. Development with a little experience using the tool usually takes 15 days or about two weeks.  

We did the deployment of this by ourselves.  

Because I am in this industry, I am gathering information about different tools all the time. I use mainly WinAutomation and ProcessRobot and maybe UiPath for only a month. It is sometimes just to collect information and other times to consider other products.  

I think the advice I can give someone considering this solution has to do with making a smart choice. If someone wants to do some RPA project without already knowing a product, then he or she needs to take quite a long time to learn about RPA. You can look at the subject to learn about it and then learn a little bit about programming. There is not just one place to find this kind of tutorial and educational material. A single vendor will only provide what you need to use their product. Each vendor has different educational materials from different perspectives and different methods of teaching.  

If they want us to use Softomotive as a solution, they may have to do less work in learning about RPA because it is easy to use. But they should probably also visit the UiPath website or maybe AutomationAnywhere to compare the products and features. In many ways, the products are the same with the ultimate goal being that of creating a working RPA process.  

But I think there is a difference in the availability of information and user communities. UiPath has a little bit more structured education system and their community is larger. Because Softomotive is not as widely used it is more difficult to ask other users questions. You may have to direct your questions to the software team. But with UiPath, they can ask questions through a web portal like forum.uipath.com. It is less stressful to ask a question and get an answer from other users.  

ProcessRobot users also have a smaller community but they cannot ask questions from support unless they have the license for the product. WinAutomation is different. It is kind of a semi-commercial product but it is not totally free like open-source. There is also a little restriction on which questions you can ask of support before you invest in the product. They are very responsive and also helpful and their company helps people directly. You go through a sort of process. Maybe Softmotive might not always find an answer or give you a particular solution. Then you can also be a little creative and look for how something is solved using other RPA tools like consulting UiPath Academy. This might give you some hints about what you are trying to accomplish.  

Sometimes I have found that I kind of I reached a dead end. I had no answer as to where to go. I was just confused and then I could not find any answer from the Softmotive website and there was nowhere to ask the question that I had. Other vendors also have wonderful features and then I tested those to see what they could do. It is kind of a long process to develop a stable process and you have to continue to learn.  

On a scale from one to ten where one is the worst and ten is the best, I would rate this product as a seven. Of course to rate this software higher, they would need to work on the stability issues, enhance the available resources for users, and fill in some of the features that are missing which other products already have. 

* Added on 2020-07-17 : Now that Softomotive is acquired and WinAutomation have become a part of PowerAutomate and the price has gone down almost to half of its original price, the future is quite promising for this product.