Mendix excels in scenarios involving Business Process Automation, making it a strong choice for applications requiring workflow automation, including processes like request approvals, document management, and other business workflows.Conversely, Mendix may be less suitable for projects that demand highly customized solutions with extensive custom coding. Its primary focus on low-code development may not align well with the requirements of projects that heavily rely on intricate and specialized coding.
Nintex works well for linear processes that have multiple players. It's helpful to capture the triggers for why a process begins and the outputs it creates. It does have a way to link subprocesses. It's not as helpful for processes that are done by a single user (SOPs seem to work better for this) or iterative processes.
We're able to really easily develop different views that are very specific to a customer's needs or customer's different types of user needs. So for example, the production managers can have a certain view that's relevant to them and then certain line managers can have views that are specific to them that allow them to run different scenarios which they define. So it allows us to easily build customized apps for each different type of user.
Integrations with other services using various secure authentication methods, along with the seamless integration with SharePoint, are the icing on the cake. This makes it superior to other BPM tools available in the market.
Flexibility in application development - The diverse configurable properties offer multiple ways to utilise the controls and events, affording the flexibility to expand your scope and enabling the creation and use of processes in a myriad of ways.
The streamlined and efficient deployment process significantly accelerates release management, allowing for faster and smoother implementation of updates and new features.
The user interface of the pages offers a more refined and appealing look and feel compared to most other BPM tools.
New Responsive Form does not allow to create a custom button anywhere we want. It will be useful to allow to add the button control anywhere within the form that can trigger the click event rule.
It will be useful to allow CSS in New Responsive Form.
Found HTML Table tag does not work properly in New Responsive Form.
More functionalities related to HTML, CSS and JavaScript in New Responsive Form will be very helpful.
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.
A 10 would say I have nothing to wish for. A 9 means I haven't seen anything better.This tool really helps you in the whole creation and maintenace cycle, so from requirements to building/modeling to testing to deploying to capturing feedback.
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.
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.
Response times are quick and you will get updates regularly about the status of your request. Even with very technical questions they have specialists that can help you with your problems it will give you an answer or help you with a work around.
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.
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.
Mendix would be my preferred system all the way. The system is designed for these kinds of works. I've worked with WP and DNN but they should be used just for websites. To create an app for a business value, I would suggest Mendix. Also, the offline capabilities of Mendix have greatly improved since the deployment of Mendix 7.13.
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 lacks the development and robustness that Nintex provides. Nintex not only covers Microsoft environments but also Google and other important platforms.
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.
It helps to speed up application development because of its low code by the fact that it's low code. It allows professional developers to focus more on specialized application development rather than the more routine application development that business IT and super users can do for themselves with some coaching from the IT department. So it's just allowing the more specialist professional developers.net, for example, Java in our organization to focus on more complex engineering application developments.
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.
