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.
