We selected Nintex because Process Manager is a purpose designed platform for knowledge management. However, what we discovered is that there are significant limitations, which has lead us to now explore developing a knowledge management platoform in sharepoint. this is a much …
Microsoft environment does not have the scalability of Nintex; it is perfect for small and medium-sized companies, especially in environments where Microsoft environment is almost entirely used. Although Microsoft offers options to connect to other applications, its platform …
Nintex Process Platform is a great tool for automatic tasks and creating forms in SharePoint Online. For automating using other applications, including third party, Power Automate has more usage.
Xmind was great for mind mapping, but when I tried to use it as a process mapper, I found it was rather lacking. It has its uses, but process mapping (at least for us in our stage and phase of mapping) was not up to the task, unfortunately. We didn't have any other software we …
We use Outsystems for other processes in our operation but we see that this platform is not able to indentify processes when drawed. Besides that OutSystems requires some basic development knowledge to use it. This makes it not really useable for business units.
Nintex workflows has much complex process management tools and better integration tools than Microsoft Power Platform. Being able to host it on premises is also an important feature for companies that are not cloud fans.
Nintex was selected because it was somewhat unique in its capabilities and depth/breadth of ability 7+ years ago. However, the competition has now caught up and pricing is a significant factor in whether we continue to use Nintex going forward.
Nintex Process Platform was and still is by far the most flexible and easy-to-use than any of the other form creation and workflow designer apps we looked at.
It's much more reasonably priced and we were able to actually experience the platform for a bit before we made a decision. And by the time our demo was finished we had already started depending on it for some of our processes so it would've been very hard to separate from it.
We use Microsoft Power Automate as well in our organization but used Nintex Automation Cloud workflows for most of the automation workflows because NWC is low code solution to develop automation workflows for SharePoint, integrate well with Microsoft teams, better designer tool …
We are using Nintex for SharePoint 2016 forms and workflows only for all kinds of automation. It has the following benefits over others. It is faster than working with the old SharePoint Designer and its
textual design or Visual Studio with coding. Less complex workflow can
It easily tailor to the use case we had that is to effectively automate email communication, while it had other options that allows us to integrate more use cases in future. While the other options did allow us to manage but the results were ineffective and there was no scope …
It offers the same user experience as other RPA solutions such as Automation Anywhere and UiPath, but with the added benefit of being able to leverage the cloud for scalability and manageability. Blue Prism Cloud works in conjunction with existing IT infrastructure, allowing …
Better User Interface.Better customer service.Easier to learn and use. But has greater risk compliances. Less preloaded automation. Less editing features and a big no while working on big projects. Fluidmesh is better in pricing and better management of multiple projects but I …
Blue Prism has played a very crucial role in understanding the analytics of the firm and the customers to know a better understanding of their requirements and to be delivered.
Both are great tools and each has pros and cons. They used to rectify the cons in the subsequent release. While getting an RPA software into our firm we did a benchmark between Blue Prism and AA to see which will suit well for us. It was neck to neck in most of the automation …
I use all the three tools and I felt the blue prism is best suitable for back end automation and performing the tasks robust and in a proper manner. It has all the features involved and all the purchased licenses are same with the features available to all the users and making …
UiPath is a good tool but open source so has a bit of limitation (but not much). We'd rate both the products at par almost but Blue Prism is more popular and famous as of now so our team took that into consideration before making the final decision about the purchase.
We implemented Blue Prism RPA for a highly complex process which required a complex set up. Since then, it has been working excellently with high accuracy.
Blue Prism RPA tool is best for any kind of user. You need not be a hardcore programmer to work on automation through Blue Prism. The core architecture is very simple and it is easy to build and maintain the infrastructure required for Blue Prism. Blue prism portal is very well …
In our company, we are using many RPA tools. For most of our medium projects we are using Blue Prism, as other tools are frequently crashing. One of the best features is that the robots can be unattended. Blue Prism has a high rate of reliability when compared to other tools, …
Estágio de desenvovimento RPA (Robotic Process Automation)
Chose SS&C Blue Prism
We chose BluePrism for the well-defined hierarchy. The values of the company were in agreement with ours. The negotiation was good, and we were convinced that the tool would meet our demands satisfactorily.
It’s more robust for enterprise usage; UIPath had an awful demo when we talked to them. Automation anywhere focuses on desktop automation with its recorder capabilities. Work Fusion focuses on intelligent use cases as opposed to automating the commonly used manual processes. …
UiPath is a more visually appealing, middle of the range, free alternative to Blue Prism. It's, in my opinion, easier to pick up, obviously due to a person being able to download it for free and try it out, and also because of it's excellent online academy. However, Blue Prism …
The Nintex K2 platform is not only efficient and developer-friendly, but the support provided by the vendor is also highly commendable. The platform's ease of use and robust functionality make it a preferred choice for developers, while the vendor's exceptional support ensures smooth implementation and ongoing assistance, enhancing overall user satisfaction.
Blue Prism Intelligent RPA is well suited for the processes which are rules-based in nature. This software works well with web based application integrations. It's very easy to capture the object details and code the workflow with ease. The record functionally will do the trick most of the time and will save a lot of effort in coding the workflow. Work needs to continue in the surface automation part. It works with surface automation but there are chances of failure sometimes and we feel like the control of automation is very fragile.
Difficult to fix flows that are in process (such as re-assigning a task for someone that is OOO or has left the company).
Nintex support team does not have resolution SLAs (only acknowledgment SLAs). Occasionally this has led to key issues taking weeks to resolve.
The number of integrations available is impressive, however, sometimes key methods are not available within an integration. This has been improving significantly in the past 2 years as the platform has matured.
Object handling can be improved more and instead of going through each and every object to find its functionality it is hard and only the experienced BP tool user can understand.
The identification of the elements can be improved much more with having useful details in place instead of only using the Indexes for the elements.
In the environment variables pane, they can add some grouping facility to divide the variables in the environment variables section.
Can improve the calculation stage for doing string operations using the VB commands instead of using code and inbuilt native functions to save time.
Renewal is mainly on the fact that Nintex is so widely used and it would be impossible to migrate all of these existing workflows to another engine. Third-party lock-in within SharePoint is pretty strong, which makes it difficult to move to something else. Our Nintex database is well-over 100 GBs. Nintex email support is very good, and I've been impressed. The Community however is non-existent and filled with unanswered questions.
Nintex Workflow does exactly what it is advertised to do: make workflow development fast and easy. It doesn't provide very much new functionality, but it isn't really supposed to. When I am working with a client on a SharePoint project, I am always happy if I hear that they use Nintex Workflow, as it makes workflows much easier.
A very user-friendly workflow creation process. A dashboard to provide a full visibility of the workflow and processes. We're able to easily monitor ongoing, pending, stopped, error workflows and act swiftly when there was a red flag. Also implemented workflow approval process where task require multi-level approval for proper ISO documentation.
The Nintex Process Platform has never crashed or had any availability issues during my usage. However there was an issue that was of my own making that caused a slowdown of the system. I had set up a process to run once a day and check for employees on a list that had certain parameters selected, and for some reason that I had to troubleshoot, the process instead ran constantly, which filled the cache quickly. I ended up having to dismantle that process so the system didn't crash.
Unlike any other process automation product out there. Not only is it a low-code, easy to use tool for building processes in environments like SharePoint or Salesforce, they have really started to expand their tool-set by offering tools to manage other things like process mapping, RPA, mobile,etc.
The support team works as fast as they can and they are usually fast to solver the issues. Sometimes they need more time to solve one of them because our workflows and so on are more complex than usual clients.
Support is good and now with time online support in other forums is becoming available as well. Blue Prism support in itself is also good. Documents and blogs can help to find the solution. Since it's relatively new, sometimes if I'm stuck it can take time to find the solution or connect to their team.
I used the Nintex training software, it was easy to watch and follow along. It didn't go too fast and was descriptive enough to understand what the steps needed were in order to produce efficient workflows and user friendly forms.
1.Start with Simple Workflows: Begin with basic workflows to gain user confidence before tackling complex processes. 2.Involve Stakeholders Early: Engage business users and IT early to align workflows with real business needs. 3.Comprehensive Training: Invest in user training to ensure smooth adoption and reduce resistance. 4.Leverage Prebuilt Templates: Use Nintex’s templates to speed up implementation and maintain consistency. 5.Iterate and Optimize: Continuously improve workflows based on user feedback and performance metrics.
I was not part of selecting Nintex, but I think Nintex does a better job of generating linear flowcharts vs. Microsoft Visio because it automates the majority of the process of creating process maps. (Microsoft Visio is better for creating flowcharts that are not linear. because it is less automated and more flexible.)
It offers the same user experience as other RPA solutions such as Automation Anywhere and UiPath, but with the added benefit of being able to leverage the cloud for scalability and manageability. Blue Prism Cloud works in conjunction with existing IT infrastructure, allowing users to continue running their current IT operations while automating processes.
Compared to Automation Anywhere and UiPath, Blue Prism Cloud has several distinct advantages. Firstly, it provides pre-built templates for commonly used tasks, enabling businesses to scale faster with increased agility. Secondly, its hybrid deployment model allows users to select either private or public clouds - providing improved scalability and flexibility.
The scalability is really bottlenecked by the imagination of the user. I was able to make processes for my own personal usage, making my daily tasks easier. I was also able to make processes that affected hundreds of employees, making large standardization and efficiency gains. So either way, the system is used the same way, and I was the limiting factor.
People have woken up to the amount of overlap after mapping their processes.
People can be resistant to process changes. You need to have the support from above or support from the 'business' that you are process changing to be able to see the positive impacts.
Numbers talk. if you can get a general salary figure from your HR dept to show savings for 'employee bands', then when you present reports, they will be all the richer in data.
Saved a considerable amount of time ( More than 5000 Hours of manual work so far )
Saved considerable amount of money as well ( If their costing improve, this matrix will improve largely for all organizations )
It requires very less coding so instead of hiring new people trained in a specific tool we were able to manage this with the existing workforce with a few weekend classes.