What previously stood K2 apart from Nintex was purely the ability to have workflows executed outside of SharePoint. Nintex are due to release a product that resides in Azure that provides this feature as well. K2 should really look into redesigning the development GUIs they are …
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 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.
Nintex Process Platform is much easier to begin with as low code or no code tool, which reduced amount of time and effort to learn and we can start working on it within a few weeks after taking the training session with Nintex. We can build the same application with same …
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 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
We started with Nintex Worklow some years ago. We see the benefits of automating workflows to process the data and that issue increment then business because we were able to process great blocks of data with almost a little effort, so the benefits were obvious. After that we …
Easier to use. Less complicated in setting up the system although K2 may be more powerful in terms of features and also not dependent on sharepoint engine. Nintex serves our purposes.
I previously had used SharePoint and this was at my last employer. At my current job we use Nintex and have since I joined the company. I have found Nintex much more user friendly than SharePoint and that it crashes less. I also think it has a better technology interface.