Likelihood to Recommend Nintex is best suited when processes are drawed by the business and then can be furter enhanced by IT professionals. When only used by business units we see that there are some lose ends in processes and some bagic process knowledge is needed. Therefore it is wise that the persons in the business who will use Nintex have some basic knowledge on how to set up business processes
Read full review React is a JavaScript user interface construction library that works well for: Developing web apps with dynamic and complicated user interfaces. creating reusable UI elements that may be used in other applications. creating single-page applications with dynamic content updates that don't require a page reload. The Virtual DOM's effective updating mechanism allows it to handle large volumes of data updates. React, on the other hand, might be less suitable for: Websites that are simple, stagnant, and have no interaction. Other libraries or simple HTML, CSS, and JavaScript may be a better fit in such circumstances. Web sockets may be a better choice for applications that need real-time updates, such as chat or gaming apps. When creating mobile apps, React Native is a better option. Server side rendering only, as React is designed to run on the client side. Read full review Pros Easily build approval process using email and assign a task actions in Nintex Workflow Easily manage security at item level with O365 permission action in Nintex Workflow Easily use Rule in Nintex Form to build the Input Form and manage the events Read full review React is fantastic for building performant user interfaces. Our web app is snappy and great for our customers. React has the philosophy of doing one thing and doing it well which is the view layer of the application. This makes it incredibly intuitive and flexible for developers to use. React has lead the way in being able to write modular and structured code. It is a drastic improvement since the days of spaghetti jQuery code. React has an unmatched community. The amount of tools and libraries available is fantastic, and there plenty of solutions available online for common problems. Read full review Cons Adding Machine learning features like the "Image and Text Automation" component, which allows bots to extract data from unstructured sources like scanned documents or PDFs. Natural language processing (NLP) features to understand and interpret human language, which can be useful for tasks like customer service or data entry. mostly for middle east countries where Arabic language is used. Integration with external systems where many industries uses their own legacy systems and they need RPA bot to interact with their systems as well. Adding More OCR tools for Document data extraction and dynamic content. Read full review Debugging React is challenging. Bugs in react code generate stack traces internal to React and it is often totally unclear how it relates to the code you actually wrote. Relating your React elements to corresponding DOM elements is difficult. The intentional separation of virtual and actual DOM also makes it difficult to map the elements to the structures in the DOM. This is partially ameliorated by the use of the React dev tool, which provides a DOM-like view of the React elements, but the tool still does not provide a direct correspondence with the DOM that is often necessary to figure out why something isn't right. Because JSX is React-specific and not a language feature, a special compilation process is necessary to convert JSX code to normal JS. Coming from a C++ background, compiling things doesn't bother me, but many JS developers are used to a less structured development. Read full review Likelihood to Renew We are currently investigating which collaboration platform best suits our needs. Chances are that we move to SharePoint Online and then we're going to also consider the microsoft power platform (power automate and power apps) to develop forms and workflows. Aspecially the pricing model for the cloud is currently a blocking factor to go for the Nintex solution in the Cloud.
Read full review Usability Based on the on-prem experience with this tool, I believe that they have a lot of potential to help the online version catch up to where the on-prem left off. Nintex developed their online version and it is not as fully formed or capable compared to the on-prem version, and the licensing model scales back what we would have liked to be an expansion or at least continuous improvement of existing flows. It is also not near as user friendly specifically to non-developers and has an uncanny similarity to Microsoft Flow in the online instance. Consistent with my reviews of the tool - I believe they have some good approaches to design thinking that, if translated well from on-prem to online, could make this a clear winner again.
Chris Carpenter Staff Project Manager, Awesomizer, Fixer, Maker, Collaboration Enabler
Read full review React is just a bit of a different animal. I was avoiding it for the longest time. I thought for sure I would land on Vue or something else with a more approachable and familiar appearance. But after taking an online course in React, I started realize what people were raving about (and complaining about) and decided to implement it at our office for one of our products.
Read full review Reliability and Availability 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.
Read full review Performance 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.
Read full review Support Rating 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.
Read full review Since it's open-source and very popular, the community support for React and related tools and libraries is excellent. There are a lot of people using the same tools, and so issues tend to get fixed quickly and "recipes" are easy to come by. And since it's backed by Facebook, they have a dedicated engineering team working on the progression of React.
Read full review In-Person Training The trainer addressed the smallest queries in a friendly and timely manner; He walked us through all the necessary products we were using
Read full review Online Training 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.
Read full review Implementation Rating test runs for key persons to insure the system is set up prior to rolling out I think the platform is good, I think the roll out and the local implantations is where we are failing as a company in using Nintex
Read full review Alternatives Considered 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
Read full review While this is a widely contested debate with various blog posts and benchmarks all over the place, its really a personal choice to determine what works for the team. Coming from a Angular 1.x background, I decided to try a new framework when Angular 2.x was announced and at that time React is gaining popularity and Vue hasn't taken off yet. Compared to Angular 1.x and Vue (hybrid of React and Angular) that split the logic from the html templates, I loved the way React breaks code into components using the jsx syntax. In my mind, this allows for cleaner components and easier maintenance
Read full review Scalability 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.
Read full review Return on Investment We have saved our company thousands of dollars by creating our own customer support system rather than using a 3rd party tool. The ability to generate documents/PDFs in workflows has solved a great number of process issues for us and groups who had previously been using paper documents. Automating many permissions updates through workflows has been a huge time saver for repetitive processes. Read full review Our web applications now run much faster because the whole page doesn't reload We spend less time developing UI components because a lot of them are readily available on NPM We don't have to optimize apps for multiple browsers since React natively supports it. Read full review ScreenShots Nintex Process Platform Screenshots