Microsoft Flow and Azure logic apps : These new and cool apps are gaining on Nintex and provide most of the features to end users that Nintex provides. They run on a different workflow engine and do not have most of the limitations of the workflow manager service. Microsoft Power…
Nintex forms has easier onboarding then PowerApps, but perhaps doesn't have as much freedom to connect to different datasources. Nintex workflow is a lot more feature rich than MS Flow however not as easy to access.
Nintex was chosen as the tool to build apps because of the native offline functionality, which was lacking in PowerApps. The offline option works great and any entries submitted are saved in the outbox and re-submitted even if the device is turned off. It also has excellent …
These used to be great tools until the new pricing model made them really painful and expensive to use. Nintex pricing is more reliable and we can plan better.
Also PowerApps/Flow don't seem as intuitive to learn, they need some 'development' background.
Nintex is easier to learn than PowerApps. Powerautomate has better performance and flexibility than Nintex Workflow. We selected Nintex for its mature capability and "no-code" functionality.
Once you have O365, the obvious choice of tools would be the ones that are part of the platform and are included in your subscription, like PowerApps and Flow. Still, we often choose Nintex Process Platform instead.
Regarding forms, Nintex Process Platform provides a more …
I used SharePoint Designer and Microsoft Visual Studio. We are testing also Microsoft Office 365 Power Automate and Power Apps which are in a competition to the Nintex Workflow Cloud. K2 was not tested but in the focus, at the end the pricing was to expensive for small/mid size …
Nintex Process Platform has an expandable option, which can design and develop numerous business operations, and support them without fail. Further, Nintex Process Platform concentrates on Form generator, a factor that automates the project management process.More so, Nintex …
Verified User
Employee
Chose Nintex
Nintex is still ahead of the curve on many of its competitors for a number of actions they offer. We do frequently evaluate other tools as many other offerings are rapidly closing the gap. Microsoft Flow has come a long way in the past year and I foresee them giving Nintex a …
Nintex Platform integrates into SharePoint so it appears to the end-user as though it is SharePoint. Also, Nintex Platform is on-premise. We cannot do cloud-based software.
Nintex Process Platform is great for more complex and heavy processes as compared to some other similar tools. Additionally, it offers great support in case of any issues.
We selected Nintex Process Platform as we already use Nintex products for form and workflow development and are familiar and comfortable with them as a Vendor. The option to tie process automation directly to the processes as drafted in the platform was definitely an added …
Microsoft InfoPath. We felt InfoPath isn't as flexible and the functionality it offered was limited compared to Nintex. Also there was information that InfoPath was going to be discontinued (at that time).
Nintex process platform is so easy for non-IT users to use for themselves and automate their day to day workflows, which is a huge success for the overall organization. Browser-based process modeling and WYSIWYG form builder is a great option for non-IT users without steep …
ITLAQ's SPARK/SPARKnit is not in your list of products. SPARK provides all of the basic functionality of Nintex forms and workflow at a much smaller price. The Microsoft Power Platform is inexpensive, but slightly more difficult to use.
Microsoft Flow is immature, but it plays well with Office 365. What we are seeing is that Office365 is a very different animal, but Nintex appeared to focus on major tool integrations as their primary release and the basic functions of WIP tracking, approvals, notifications, …
We selected Nintex Workflow because it seemed to be the best and most popular at the time. But after awhile we saw that Microsoft Flow better suited our needs. Its large selection of connectors that allows integration with other services(DocuSign, Gmail, SalesForce) and it's …
1. PowerApps functionality comes with E1 over E3 License without adding extra costs 2. For Nintex you pay (at the beginning) for each workflow, so my intention would be, to do no workflows to prevent additional costs, but I want a platform with a fair price that allows me to …
PowerApps is what the company has presented to us as our option. While Nintex is nice and relatively capable, it is always a +1 to the Microsoft platform and requires its own validation and integration. Nintex can also be feature limited in its online version depending on the …
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.
Power Apps is ideal for scenarios that are neither too complex nor too large. It is easy to begin development in Power Apps, as it is one of the best tools for low-code development. Power Apps can be implemented for complex scenarios as well, provided there is strong knowledge of the tool and ample time for planning. Our applications benefit from Power Apps' cross-platform support, making it easy to use on any device, including desktops, laptops, and mobile devices.
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.
Power Apps has formats that are pre-built that don't require any coding which makes it easier to achieve your vision. This does become a challenge if your App needs don't fit into that format.
We deal with a ton of data so the fact that you can connect to any data source in addition to their pre-stablished data connections makes the process a breeze.
The online learning resources and tutorials are helpful as well for those who are tech savvy.
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.
Sometimes the cost of solutions is greater than the benefit. Licensing is expensive relative to the scope of some business user-created personal or team-level solutions.
While there is a starter-kit for Governance, it is complicated to stand up and requires dedicated resources to provide on-going governance operations. Many organizations are not going to be able to dedicate resources to governance and this causes the sprawl, solution duplication, silos, unneeded and unplanned licensing expenses, and a general "wild wild west" environment.
There needs to be better direction and best practices given around Power Platform Environment utilization and optimization.
The accessibility to the platform and ease for business partners to independantly create solutions is both a benefit and a negative. When the business outcome needed is a good fit for PowerApps it is a quick win, but when not a good fit it becomes a frustration for the business partner attempting to make the platform do something it is not well-suited for. The business partner entangles tech teams in the effort which drains resources and provides a lack-luster solution. All of this to say, it would be beneficial to have some tools that business partners could leverage to determine\understand if the type of business outcome they need is well suited to PowerApps or not.
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.
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.
PowerApps is a great solution and I have spent the last year familiarizing myself with the platform and building custom applications to complete a whole range of tasks such as asset management, custom invoice generation, and item restriction tracking. We as a company have barely begun to scratch the surface of what can be achieved with PowerApps.
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.
The community forums are extremely responsive to questions asked, there is a good body of online documentation and many community posts to draw from. Although the platform has changed, which means some of the posts are out of date and the solutions provided aren't relevant. Of relevance, I read over 400 articles plus documentation to get this first app built in SharePoint, move it to SQL and make it work exactly the way it should.
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.
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.
1. PowerApps functionality comes with E1 over E3 License without adding extra costs 2. For Nintex you pay (at the beginning) for each workflow, so my intention would be, to do no workflows to prevent additional costs, but I want a platform with a fair price that allows me to create workflows without thinking about the price for each workflow and we use only some workflow and relative easy workflows and forms as a medium-sized company. 3. PowerApps provides a lot of functionality without needing to invest in premium features directly.
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.
