First advantage, from a business point of view, is that it's cheaper. From a development point of view, it's easy to develop because it's a low code and low code solution. And almost Nintex provides all the possible solutions in their built-in criteria. So, we have only to configure it. We don't have to write anything from scratch at all.

It's easy to learn. However, there is very little content available for the Nintex also, but they are providing their own documentation and all. So, it's easy to learn also.

Within Nintex Workflow, I think the automatic triggering of the multiple workflows and the setting up of the auto trigger of those workflows are some of the valuable features of the solution. So that is nice.

Our company needs K2 as an engine. We don't prefer to use the forms because the overall cost is high. Because of this, we have to go to workflowengine.io since it gives us the same results at very low prices. It's not restricted to processes or something like this.

The interface is very good. We developed it there and it makes it easy to handle the workflows. 

It is very easy to use. Microsoft technology integrates well with K2. YOu can develop prompts to your .NET framework and are able to integrate K2 workflows within the system.

The solution is stable.

Technical support, especially during the first year, is very helpful and responsive. 

It's not hard to set up. 

This solution is very easy to use and customize, using almost zero coding. It's built on SharePoint which many companies in our country have experience with. This made it easy to adapt the application in our environment.

The latest version of Nintex has many features. We have a clear roadmap and the necessary application to integrate it into our platform.

The drag-and-drop feature is quite interesting; it helps us a lot. We can manage different dates within a single workflow and identify the number of tasks we can dynamically dedicate to other users. Even if we assign a task to a single person at any point, we can change the delegation in the future or the responding entity at any time. Moreover, Nintex integrates with Microsoft ecosystems such as Office 365, MS SQL, and Azure. This makes it a strong candidate for anyone interested in Nintex.

It has a lot of features for creating and managing workflows, as well as for integrating with other applications. Nintex offers features, particularly to ensure a user-friendly experience.

The most valuable features of this solution are that it's no code, it's very flexible, and it's easy to design.

The workflow engine of K2 is its main strength. Its workflow engine is probably one of the best, and that's the reason why Nintex bought K2. It can clearly handle any complex process or scenario.

K2 is almost low-code. It is a no-code or low-code solution. You don't have to read a whole lot of code. It is pretty much GUI based. Their support is also excellent.

The biggest advantage of K2 is SmartObjects, which allow you to separate the data from the application. It is a standalone application that allows you to build a data source from different places, which a lot of other applications also do. It is called SmartObjects technology, which is pretty powerful. If I have data from different applications, such as JD and ServiceNow, I can just create a SmartObject based on a data source and use it. I have some forms that have six, seven, or eight applications in a single form with data from different places.

The Nintex Workflow's straight workflow and auto-response feature, along with its layer response functionality, make it easier for my end users to respond to emails. They can either opt for a date response or respond directly on our website without having to navigate to the initial screen. Overall, it is a straightforward and user-friendly process.

It is very easy to create and deploy. It does not take your time like SharePoint Workflow. There is no need for the IT people to do it. SharePoint Workflow, needed a programmer to do it. So there are vendors looking forward to Nintex because it is easy to create by the end-user.

Nintex Process Platform’s most valuable feature is workflow. It is flexible and shares an update quickly. It is easy to maintain as well.

The solution is good.

The solution has the capability to handle robust execution.

K2 has a very wide collection of smart object technology. It's phenomenal. The concept of the smart objects is core to K2. 

The setup is easy.

The solution is stable.

It can scale well.

Support is helpful. 

I really like the visual representation. It actually looks like a flow chart, which is nicer than a SharePoint Designer workflow, which doesn't have that ability.

As a workflow automation solution, being able to route, approve and manage content is one of the few areas in SharePoint where there is a true ROI. Provides the ability to automate SharePoint processes (building sites, lists, updating content).

You can also automate document and content processes, onboarding and offboarding, and general IT and HR solutions.

With an extensive list of integrations with LOB data, your workflows can extend far beyond SharePoint, driving adoption of SharePoint and saving people, departments, and companies significant time in their daily processes. These are huge value drivers for SharePoint and Nintex.

K2's best feature is that it can solve complex tasks, issues, and projects with little coding.

The biggest selling point for us was that the solution had out of box connectivity with UiPath and we didn't have to write any custom code to be able to invoke UiPath bots and automation solutions. That worked well for us in the past but when you talk about other specific functionalities, like the applications or authentication on native operating systems for mobiles and those kinds of things, K2 is lacking big time. The solution doesn't really have a good set up and I think as more and more businesses want app rather than desktop systems or web systems, K2 is not necessarily the best solution going forward.

Being able to simply create workflows to handle business processes. It allows us to route approvals to users without human intervention.

The feature that I found most valuable is the ability to impersonate the users so that high-level access to certain resources can be provided. For example, impersonating the super admin allows you to perform actions that cannot be performed by regular users, and they can be badged with this kind of action set. 

Another thing that I like is the deeper loops, and also deeper schedules so that you can schedule a particular workflow to a particular type.

The Vizio-style designer that runs in the browser is, to me, by far the most valuable feature of the solution. It means that the customer doesn’t have to install any client tools to create powerful workflows.

Another feature that is very close in importance is that it leverages the out-of-the-box SharePoint back-end. This means that you don’t need to install or deploy additional infrastructure to support Nintex Workflow, unlike some of its competitors.

State machine and sequential Workflows are excellent features for creating complex state machine and sequential workflows that integrate with major Microsoft products like CRM Dynamics, SAP, and Peoplesoft.

We can create workflows for document management, publishing workflows, and create other custom workflow solutions spanning multiple roles and levels of approvals.

It has integration with BI and Analytics tools, and RPA toolsets as well. 

Custom integration using REST APIs for Line of Business applications is helpful.

It provides good audit and reporting for workflow tasks to detect and resolve issues.

The SharePoint feature is a really good connection, there are many features that are good. 

The value of this solution is that it's easy to maintain, and to further develop. It's quite low code, so there is not the need of really specialized people and customization is quite simple. 

It supports SharePoint in the platform, and it's easy to customize to the maximum extent.

• Workflow (escalation, reminder, LazyApproval, actions, etc.)
• Ease of use

The solution in general is very easy to use. It's very user-friendly, and it has satisfied the requirements I have. 

It's a really good platform. 

The integration capabilities have been very useful. It's very powerful and very advanced.

The stability of the product is quite good.

The most valuable feature is the workflows. We have started working with the SmartObjects and the SmartForms, as well.

1. SmartObject makes the center of data management, where developer and/or someone can call to it with only one place. SmartObject will return data from other system (such as MS-SQL, Oracle, SharePoint, SAP, etc.) to solve requirements.

2. K2 connect for SAP, easy to make interface between SAP with K2 connect for SAP service designer. Developer can design interface without coding and transform it into SmartObjects.

3. Workflow, to support more complex business processes, logic and data flow without coding.

4. SmartForm, fast and easy to develop web form to connect to SmartObject and workflow. Where you can create web application and ready to release to users within an hour.

• Scheduling a site workflow is much easier and more convenient. 
• I like the feature of getting an email for a workflow error, then I do not have to go through every instance. 
• Conditional start of the workflow is the highlight of Nintex Workflow. 
• Only Nintex has the feature which allows attachments to an email.

It is very easy to use events. K2 has useful tools.

The design and the vision the solution allows for is great. 

It's gotten better with time. version 4.6, for example, wasn't the best but 5.4 and 5.6 continue to be a bit fancier and offer up a bit more. The improvements are great.

The enhancements, overall, are great. It's so easy to use compared to the competition. Its enhanced usability makes it the best of the lot.

We are able to use K2 to manage as our environment and have everything deployed to the servers.

The performance of the product is excellent.

The solution offers very good integration capabilities. We've never had issues integrating it without solutions.

Scalability, good performance, and the K2 designer to create workflows/screens are the most valuable features.

• Lazy Approval (email-based approval)
• External system connectivity actions
• Delegation
• Rapid solution development

I find it useful to utilize LDAP query action to find out the status of a particular user.

• Allows us to provide desktop/laptop and mobile solutions to our users.
• Using workflow for simple approvals and LazyApproval; the feature is easy to implement for mobile approval.