Nintex Process Platform Reviews

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.

• Supports conditional approval by business logic very easily
• Multiple approvals
• Notice of approval by email

Performance. Some customers ask why K2 is slow? Upgrade to current version will get the better performance.

More than 7 years.

Easy to makes deployment package.

Found less in the current version.

No.

Eight out of 10.

Eight out of 10.

K2 is my first and only one solution that I recommend.

Setup is easy in standalone. Distributed setup is complex and requires more network knowledge.

I’m working in the development field and do not know much about this.

No, my team was trying to map requirements to the K2 solution.

K2 makes your work simple.

To automate a manual process through Nintex Workflow in a SharePoint environment.

It provides data accuracy with fewer failures. It saves time as tasks are automated.

This tool is really helpful in reducing a lot of manual work. Its drag and drop components help to create a workflow faster than SharePoint Workflow Designer.

• 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.

Converting a document from PDF to MS Word, or vice versa, needs to be improved.

Our maintenance costs are reduced.

For the past three years, I have been using Nintex with SharePoint 2010 as well as the 2013 environment.

One use of the solution is for the leave request process end to end. Someone submits a request, there is verification, and then depending on the answer of the monitor of the human resources, a document is generated for a digital signature where the item is stored in SharePoint. 

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

The interface could be better and more language support is needed in the development environment or in the solutions platform in general. Here in Algeria, we have clients wanting the solution to be in French instead of English.

In the future, I think it would be a benefit for the company to have a larger social media presence. This way more people would know about the solution and its benefits.

I have been using this solution for approximately one year.

The solution is stable. For what I use it for, I have not had any problems or encountered any errors.

We have two people using the solution in my company. We are building demos to show potential clients.

The technical support is very good.

I used previously K2, then after Nintex bought K2, we are now using them both. 

The main difference is K2 is used for complex and deep processes. While this solution is used for simple to moderately complicated processes.

In the initial setup, I found there to be too much compromise in the cloud version. The cloud version is deployed in any environment with no problem. We did not install an optimized version for now, but I think it is not going to be complicated because it is on serval different SharePoints.

We did the implementation ourselves and it took one week to do. The maintenance of the solution is done by Nintex on their end.

The price of this solution is affordable but the problem in Algeria is our community is a bit slower. The new clients might feel the solution is a bit expensive.

I have evaluated Kudzu and SAP CRMs previously. They both have CRM connections which are good.

I would recommend this solution to others.

I rate Nintex Workflow a nine out of ten.

We use it for internal process automation.

The solution helped us automate several processes we used to do manually.

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

The integration could be improved, and we are looking for a solution on Office 365, not on-premise SharePoint. In addition, we cannot use the same solution on cloud, and we have to purchase it all over again to get it on cloud.

We have been using this solution for three years. We have a perpetual version, so we stopped renewing it last year. It is deployed on-premises on Sharepoint.

The initial setup is straightforward.

I rate this solution a seven out of ten because of its limitations.

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

It didn't calculate the designs I needed. If a customer doesn't know what to do with the BPM tool, then they won't know how to start using the tool. It is very flexible because you can design your own main forms, but if there were some templates according to your market, it would be more useful for a new customer. That would make K2 more user-friendly and easier to use.

Perhaps they may add some different holdings, and if you carry a file which uses either shape, you can handle the document. That's not our preferred method to manage software. Perhaps they could add a simple archiving function in the software. That would be very useful.

We've had some problems but they solve them in a very timely manner, so even if it has a problem, they fix it. Problems are rare, but sometimes it stops and you have to check it. We didn't have too many problems but sometimes it stopped and didn't go forward. 

It is very easy to add users.

We have implemented K2 for two companies, but there are four or five companies using K2. There is a common problem right now in Turkey, so it is not easy to manage software installation.

Their technical support team is very fast. They make a remote connection and help us out.

We actually don't need this solution in our own company. We have a demo platform that we implement because we are developing software, so we don't need this solution. We use alternative management stuff.

The initial setup is very easy, it doesn't take too much effort to install if you know what to do. Setup time depends on what you do. For example, you can get up and running and make the system worthwhile within one week or it could last two or three months. This is a complicated question.

It is very flexible but that also means that it has too many tools. It is hard to stop. You can do whatever you want but this takes practice to understand how to use this solution best.

If you need to integrate into anything, K2 is very useful. I advise you to be organized from the outset, before starting the project. This is very important.

I would rate this solution an eight out of ten. We have examined too many workflows. Some are better, but this one is good enough.

We primarily use the solution for government and public e-services. We always deal with K2 in these areas. We use the solution to mostly deal with workflows.

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.

Even though the performance is better than the competition, it needs to be enhanced and improved upon. They could always refine this a bit more.

The licensing needs to be improved. Right now, we find it's getting more expensive to use the product.

The K2 platform could be enhanced.

We have approximately six years of experience working with this solution. It's probably been a bit more than that, actually.

You can definitely scale the solution. K2 has a feature that allows it to go with other solutions quite well. It's the best option for companies that need a solution that can scale due to the fact that it can integrate with many systems.

We've dealt with customer service in the past and they were satisfactory. They are very good and very easy to work with. We haven't had any trouble in that regard.

Largely, the initial setup is straightforward. It's not too complex.

The deployment of the product takes two or three days. In terms of the workflow, it can be implemented in about one week. Overall, you can go live within two or three weeks.

The licensing is quite extensive. I cannot speak to whether it is cheaper or more expensive, however, the licensing model needs to be reimagined and revised. Overall, I've found that they've become more expensive over time.

We have a partnership with K2.

All in all, I'd recommend the product to other organizations.

I'd rate the solution eight out of ten. If the pricing was better, I'd probably rate it higher, however, their licensing model has changed and things are more expensive than they used to be.

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

There are several products. One of them was a product to improve the claims management of an insurance company.

The Management console needs to improve because sometimes it is too difficult to manage the workflow instances.

I have used this solution for two years.

In previous versions, I found different issues in regards to the stability. Currently, with this version, it seems that those issues have been resolved. The same has been experienced in terms of the scalability.

Technical support is not so good, i.e., you should have a good contact inside the company, because the service desk is not that efficient.

The initial setup was absolutely complex. It is so difficult to configure the previous versions. But in the new version, the installation has improved and it was much better.

It has a good price for the licenses as compared to the other market solutions available.

It is a very good solution to implement simple workflows with little integration.

The integration could be better, but for simple workflows with simple integrations, it is a good product.

We are using Nintex Workflow for internal reviews between banking groups, and automating the workflow.

Integrating with work services is required, and it's an area that needs improvement.

Stability needs improvement.

From a monitoring point of view, and alerting should be improved.

We have been using Nintex Workflow for almost four years.

Unfortunately, Nintex Workflow is not that stable. We are looking at shifting to another tool.

We have over 200 users in our organization.

We have technical support available to us, but we have not utilized often, our resources are capable of addressing all of our technical issues.

Previously, we did not use another solution, it was our first test workflow system.

With the initial setup, most of the cases are straightforward.

The deployment and implementation are done ourselves.

Comparatively, it's expensive.

We are planning to decommission this product for use and we are still exploring other products.

I would recommend some other tools rather than this.

I would rate Nintex Workflow a seven out of ten.