SharePoint Solutions Architect at a tech services company with 1,001-5,000 employees
MSP
Browser-based Vizio-style designer means no need to install client tools to create workflows
Pros and Cons
  • "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."
  • "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."
  • "While Nintex Workflow has pretty robust troubleshooting abilities, I think that improving the default logging and notifications would be helpful."

What is our primary use case?

As a Solutions Architect my role is to help my clients implement tools and technology that can build and automate their businesses. While my clients and their environments very widely, Nintex delivers a product that can be used regardless of the industry, division, etc.

In most cases we help clients implement Nintex Workflow to automate business processes that can be tedious when done manually, such as information approvals, notifications, and integrations with other system/data.

How has it helped my organization?

The biggest improvement to the organizations that I work with is that it allows the users to reduce, if not eliminate completely, the amount of human interaction, for both complex as well as simple business processes. This allows the users more time to focus on aspects of their work that can have more impact on the longer term strategies of the business.

What is most valuable?

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.

What needs improvement?

While Nintex Workflow has pretty robust troubleshooting abilities, I think that improving the default logging and notifications would be helpful. Many times we work with clients that have started a workflow, but find that it doesn’t work as they expect, and need assistance in troubleshooting and correcting any errors. That, and offering a licensing model that allows for multiple small workflows, would be a huge improvement to an already great platform.

Buyer's Guide
Nintex Process Platform
April 2024
Learn what your peers think about Nintex Process Platform. Get advice and tips from experienced pros sharing their opinions. Updated: April 2024.
770,428 professionals have used our research since 2012.

For how long have I used the solution?

More than five years.

What other advice do I have?

I have used Nintex Workflow 2010 and Nintex Worflow 2013. I have not worked with a client that has the most recent version deployed.

Overall, I would rank Nintex Workflow at eight out of 10. It is a strong product and is definitely best in its class. It offers strong usability with the in-browser, Vizio-style designer, and can also deliver on some powerful workflow actions. There are times, when dealing with complex workflows, where understanding the application and its nuances is required.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
PeerSpot user
Enterprise Architect at a consultancy with 10,001+ employees
Real User
Top 5Leaderboard
Good support, straightforward to set up, and improves our process performance
Pros and Cons
  • "It has integration with BI and Analytics tools, and RPA toolsets as well."
  • "We would like to design parallel workflows and long-running workflows, along with new features for connecting to cloud-based systems."

What is our primary use case?

We have implemented an end-to-end workflow solution for a private bank for their loan origination system. We have also implemented a claims reimbursement system, and item-level permissions for SharePoint lists using Nintex workflows.

For end-to-end approval workflows, Nintex workflows are deployed on the SharePoint front-end servers. The claims reimbursement workflows are end-to-end workflows for approvals of claims within the organization. Those for financial services include loan origination, legal and compliance, and core banking system workflows.

Resource management and employee onboarding workflows have also been created to automate the employee onboarding process.

How has it helped my organization?

From what was a 20 to 30-day approval cycle, it has now come down to between two and three days for approving loans and claims.

SharePoint does not support item-level/row-level permissions, and we were able to implement the solution using Nintex workflows.

The product and its features have improved the productivity and efficiency of the process flow within the application and systems, providing end-to-end connectivity to all systems.

Tracking of all approvals minutely, audit logs for issues, and helping to find out any non-compliance in the process flows.

What is most valuable?

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.

What needs improvement?

We had issues with long-running workflows for approval processes. While the workflows are waiting for the action to be taken by the approvers, sometimes the approval takes time and workflows do not respond to the actions after a certain number of days.

We would like to design parallel workflows and long-running workflows, along with new features for connecting to cloud-based systems.

When the workflow tasks increase in number, there are issues with performance that need to be addressed.

For how long have I used the solution?

We have been using the Nintex workflow solution for close to eight years.

What do I think about the stability of the solution?

The Nintex solution is stable for small to medium workflows and even, to an extent, large workflows.

What do I think about the scalability of the solution?

The Nintex solution can scale from a single server to multiple server deployments to manage workloads.

How are customer service and technical support?

Good customer support in terms of help desk, and support for fixing product issues.

How was the initial setup?

The initial setup was straightforward, with appropriate demos, documentation, and user manuals.

What about the implementation team?

Implementing the workflows as a development vendor for a major financial services organization, real estate firms, and insurance companies.

What was our ROI?

Looking at the capabilities and usage for all process flows to be automated within multiple systems and applications throughout the enterprise, the ROI will be met and break-even reached within a year.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Nintex Process Platform
April 2024
Learn what your peers think about Nintex Process Platform. Get advice and tips from experienced pros sharing their opinions. Updated: April 2024.
770,428 professionals have used our research since 2012.
Digital Solution Engineer at a tech services company with 1-10 employees
Real User
Feature rich, affordable, and responsive technical support
Pros and Cons
  • "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."

What is our primary use case?

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. 

What is most valuable?

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

What needs improvement?

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.

For how long have I used the solution?

I have been using this solution for approximately one year.

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

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

How are customer service and technical support?

The technical support is very good.

Which solution did I use previously and why did I switch?

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.

How was the initial setup?

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.

What about the implementation team?

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

What's my experience with pricing, setup cost, and licensing?

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.

Which other solutions did I evaluate?

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

What other advice do I have?

I would recommend this solution to others.

I rate Nintex Workflow a nine out of ten.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Other
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
it_user1269510 - PeerSpot reviewer
Chief Information Officer at a construction company with 51-200 employees
Real User
Very simple to maintain and develop with customization an easy process
Pros and Cons
  • "Easily maintained and customization is quite simple."
  • "Difficult to include external partners with the solution deployed on-premise."

What is our primary use case?

Our use case of the solution is to help the sales people in the field, enable them to have all the information from the backend and to more easily put together a proposal for management regarding new tenants of shopping centers. There is a process that flows to the works department, the legal department, the asset manager, and the project manager. They are able to make suggestions, comment, discuss numbers, and make some declarations. It provides good feedback to the management who then need to make a decision. We provide this service for both internal and external clients. We're a customer of K2blackpearl and I'm the company chief information officer. 

What is most valuable?

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. 

What needs improvement?

I think there can be improvements in the product but that may be linked to the decisions that we have taken to put it on-premise, because now we're making big changes and the scope of the project has changed so that we now want external partners to have access to the system. Because we're on-premise, it's more complicated to provide access to their own network. Next time I would go for the cloud. 

For how long have I used the solution?


I've been using this solution for about three years now. 

What do I think about the stability of the solution?

Stability is good, no issue there.

What do I think about the scalability of the solution?

Scalability is good. We implemented it in Belgium and then in France and we're now expanding the scope further.  

How are customer service and technical support?

We haven't needed to contact technical support as we work directly with the integrator. 

How was the initial setup?

I believe the initial deployment took about three months. We used an integrator to help with that and it was successful. They provided some training for us so we'd be able to figure out how to do things ourselves. It was great. 

What other advice do I have?

I would suggest to anyone wanting to deploy this solution to find a good integrator that understands the business first, not only from the technical side. Don't hesitate to take the journey. I would also suggest starting with a small solution and then expand it. Like everything, do a minimum viable product and then extend it a bit more slowly and grow into it.  

I would rate this solution an eight out of 10. 

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
IT Development Manager at a tech services company with 201-500 employees
Real User
Useful for internal process automation but the integration could be improved
Pros and Cons
  • "The solution helped us automate several processes we used to do manually."
  • "We cannot use the same solution on cloud."

What is our primary use case?

We use it for internal process automation.

How has it helped my organization?

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

What is most valuable?

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

What needs improvement?

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.

For how long have I used the solution?

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.

How was the initial setup?

The initial setup is straightforward.

What other advice do I have?

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

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Associate Solution Architect at a tech services company with 10,001+ employees
Real User
Easy to use, helps automate business processes, notably reduce development efforts
Pros and Cons
  • "Valuable features include workflows (escalation, reminder, LazyApproval, actions, etc.) and ease of use."
  • "Currently, copying workflow actions from one workflow to another is not possible. Also, the Office 365 solution is not as mature as on-premise."

What is our primary use case?

We use it for SharePoint 2013 and 2010, and SharePoint Online (Office 365).

How has it helped my organization?

Able to automate business processes and help reduce a significant amount of development efforts.

What is most valuable?

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

What needs improvement?

Currently, copying workflow actions from one workflow to another is not possible. Also, the Office 365 solution is not as mature as on-premise.

For how long have I used the solution?

Three to five years.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Automation Team Lead at a tech services company with 11-50 employees
Real User
Stable and easy to use with good integration capabilities
Pros and Cons
  • "The integration capabilities have been very useful."
  • "The Workflow Designer needs improvement."

What is our primary use case?

I primarily use the solution as a development platform.

What is most valuable?

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.

What needs improvement?

The Workflow Designer needs improvement. For example, when you design a workflow on K2, it shows the entire area between one action and another action. However, you should be able to see the structure for this action. It's not automatically structured.

It sould be automatically structured from the shared action to the following action. In K2, you should be able to organize it by yourself. Workflows should be very easy to organize exactly as you need them. It shouldn't be inflexible. The mapping processes need to be better.

You can't really change the look and feel. You should be able to customize the solution a bit more.

The document generation, the dynamic document generation, could be a great addition as a feature.

For how long have I used the solution?

I've only been using the solution for six months. It hasn't been that long just yet, however, I am enjoying the product.

What do I think about the stability of the solution?

The stability is very good. There are no bugs or glitches. It doesn't crash or freeze. It's reliable.

What do I think about the scalability of the solution?

The product doesn't seem to have many limitations. It can likely scale well. 

How are customer service and technical support?

There's no need for technical support as we order services done for us. As far as it's from K2 goes, there's a web solution on the platform and there are partners for the company. Up until this point, however, I haven't found the need to reach out. I haven't had problems that required assistance.

Which solution did I use previously and why did I switch?

I worked with Nintex for a few years. Recently, after I ran a comparison between K2 and Nintex, I've been working for six months on the K2 platform. I've found it very useful, and very easy in comparison. However, I still use both. Nintex acquired K2 recently.

How was the initial setup?

Compared to Nintex, Nintex is easier to set up. Unlike in K2, in Nintex, you can just build on top of SharePoint. If you want SharePoint, the environment is set up and can install directly in Nintex. In K2, you are configuring two environments. 

What's my experience with pricing, setup cost, and licensing?

I am unsure of the exact pricing. Nintex acquired K2 in 2020 and there may be a shift in the cost structure. I can't speak directly to that, however.

What other advice do I have?

We are a K2 customer and a Nintex partner, although, since the 2020 acquisition, they are the same company now.

I would recommend the solution, especially for companies that are working to go paperless.

I suggest that if they want to integrate between systems from a strategy department into another department, to really look at the integration layers that they have, as it's very advanced.

In general, I would rate this solution at a nine out of ten. We've been largely happy with the product.

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
Lead Technical Architect at a pharma/biotech company with 10,001+ employees
Real User
Easy to create workflows but the SmartForms need to be simplified
Pros and Cons
  • "I think that it adds value to any organization, mainly in terms of business applications where you need workflows."
  • "I would also like to see the BPM features from Pega implemented, that have to do with the implementation of AI, and the robotics."

What is our primary use case?

Our primary use for this solution is for automating workflows in business applications.

What is most valuable?

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

What needs improvement?

The SmartForms need to be simplified so that the non-expert, business users can make use of them without coding. That will help a lot. 

I would also like to see the BPM features from Pega implemented, that have to do with the implementation of AI and the robotics.

The AI should be able to learn inside the platform so that it adds intelligence to the tool itself. That way, it can handle the things that are being taken care of by external entities. It will first learn how to handle new events, and then handle them by itself in the future.

For how long have I used the solution?

Six years.

What do I think about the stability of the solution?

I would rate the stability four and a half out of five. Overall it is good, but sometimes it fails.

What do I think about the scalability of the solution?

This is a very easy solution to scale out.

We have approximately sixty thousand users for this solution. Perhaps one hundred of them support the applications and integration, but the majority of them are end-users.

How are customer service and technical support?

Technical support for this solution is good. We have a contract with them and the support is good. They always help.

Which solution did I use previously and why did I switch?

I have used Pega and I feel that it offers more than the K2 solution, in terms of the latest technology. For example, I like their implementation of the AI and the robotics inside of their system.

How was the initial setup?

We are part of a technical team and we have the expertise, so the initial setup was not complex for us.

What about the implementation team?

We had a consultant from K2 assist us with the setup.

What other advice do I have?

This is a good solution and it is easy to implement. I think that it adds value to any organization, mainly in terms of business applications where you need workflows. It is easy to use, and workflow design can be done by business users. Overall, it is a good product to have in an organization.

I would rate this solution seven out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Download our free Nintex Process Platform Report and get advice and tips from experienced pros sharing their opinions.
Updated: April 2024
Buyer's Guide
Download our free Nintex Process Platform Report and get advice and tips from experienced pros sharing their opinions.