Nintex Process Platform Reviews & Product Details

Good, this is easy and flexible. i recommend to all others

Nothing much, but sometimes its hard to use some actions. especially mobile forms are not friendly.

used for all departments

Usability , UI , workflow on cloud , mobile app

error handling, some limitation on cloud version

services Request & HR reqyests

I love how easy it is to quickly get a solution up and running! I can demo a working solution to a group in a matter of minutes rather than weeks or months with custom coded solutions. The drag and drop interface allows me to teach others how to use it and enable other areas of the business to create their own workflows, thus engaging them throughout the process.

Some of the error handling is cryptic. This can cause us to waste time pinpointing exactly what went wrong. We generally put in "Log history" actions and then dump variables out to that, which forces us to run the workflow knowing that it will fail to determine what went wrong. This is a good debugging approach, but if there was a way to "Preview" the workflow somehow it would be awesome!

We are using the workflow platform for task automation and approval, internal data lookups to populate out to lists, and even internal site creation automation. We have streamlined different processes that were very paper driven and opened up channels to communicate and track changes to requests and tasks, thus giving more visibility to executives.

Nintex is a real time saver when comes to solving approval processes.

there are some bugs, although they maybe related to underlying Microsoft foundation.

Document approvals

Easy and user friendly No need for any code experience

Some limitation on some controls Other is fine

Automate many bussiness forms and work

I like the GUI that you are presented with as a user. Using Nintex Workflow is extremely easy.

I don't like some of the limitations with timer jobs. I wish nintex would allow for timer jobs to run as close to a few seconds as possible. Currently the lowest frequency is 5 minutes.

We have been able to improve processes through the use of workflows. We tend to notice that with each project our ability to create better workflows increases.

Simple and easy to create a form and workflows. I have implemented many projects within less time using nintex

The feature of limited action in a workflow sometimes it will be a hindrance.

I am using nintex to create SharePoint forms and workflows. Less time consuming and easy to work with the drag and drop feature. Even a non technical user can also learn easily and work.

The connection manager and action set are the two major features I liked the best. Now the reuse of workflows make them more efficient and less cost. We reused many workflows using this. Calling sub workflows is also very easy. Also use of workflow forms association to tasks is the game changer.

I disliked the feature of Large workflow rendering issue. Once the workflow has hundreds of actions the rendering is a big issue.

We solved many manual complex business processes into a easy workflow based system. We eliminated many existing paper based business process to automated web based apps. Made the people accountable and task assignment app made life easy.

Nintex provide a lot of functionalities that allow to a anyone users automate their process, no matter if you are an advanced user or common user, the interface is very intuitive and actions can be set for your needs. I had automate around sixty process without any advanced experience using workflow automation platforms. Also provide Nintex Live, a good way to capture information for users out of the company.

At first I was needing more actions to handle and generate documents, however this functionalty was release for all platforms and now I'm very happy using this functionalty in my process.

Now we are capable to measure our process, before that, this measure was very hard to complete because we didn't have data to make it, now with we have available a lot of process data and we are makings insights with this data.

Promapp is easy to use , it has great sharing capability and is such a great ''GOTO'' for new staff and for keeping all procedures in line within the company.

Haven't come across anything I don't like as yet

Shortening processes that were otherwise time consuming. Having consistency in roles throughout the Company. Identifying procedure issues within roles

The UI, look and feel is great with they way everything is so clear and simple. Its really quick to create forms and processes from start to finish. Like the integration aspect also.

No search function withing the rules there is however in the states but not within the rules itself, but rectified with K2 Five. Package and deployment tool dependencies has constant conflicts that takes ages to compare. (Apparently Fixed in K2 Five)

Multiple Departments on one platform processes for each system etc Hospital Management Hospital Enquiries Hospital Accounts Customer Management Leave Systems Claims departments

The ability to provide an IT supported platform to the business where they can develop through configuration their business process fast and fully controlled by them.

The ability to store information in another platform like SQL server is great but you need super users or people with some skills to create databases. If this would be a functionality where it can be translated into non technical terms but still have the ability to create a new database outside the K2 database.

Customer setup and modification, Purchase order management, manual allocation, Inventory automation, Audit tools for supply chain, HR training and overtime,...

I like how K2 has evolved over time to become more capable and more user friendly. We have done a lot with no-code solutions using K2.

Development can be a little frustrating. We are not on K2 Five yet, but we have had lots of little issues of extra "rules" cropping up during iterative development of a new form or workflow that causes things to break. It can be difficult to troubleshoot, especially for non-developers. It also seems that there are certain "orders" of doing things that make things function more smoothly during development, but until you have experienced the pitfalls, you don't always know that.

We are automating everything from document approvals to user onboarding. The primary benefit we have realized is business analyst have been able to create applications with little IT support.

The thing I like best about K2, is that they are incredibly dedicated to supporting their product and partnering with us on solutions. We can reliably count on timely responses to support tickets. We've also gained a lot of useful knowledge using mentor credits and they are always available for general product support. With our last SharePoint workflow vendor, we had essentially zero support, so this is quite a change. Our company has a culture of mentoring citizen developers, where we meet weekly to talk about product updates, obstacles, how-to's, and show what we're working on. They've been incredibly helpful by joining these weekly citizen developer calls.

Permission can be a little difficult to wrap your brain around. Their are permissions around forms, workflows, and publishing rights. It's important to establish governance and best practices around who is allowed to design workflows and to have a review process on what is put into production. It is possible for a poorly designed workflow or loops to degrade server performance and/or bring down your environment.

We build a broad range of business solutions and automation in SharePoint. For instance, we built a SKU management system, email replacement systems, and dynamic intake forms to log tickets with the correct information the first time to allow the business to process requests. We've been able to build forms that dynamically hide and show information and pull data from other lists and data sources. This is the type of stuff we needed to rely on workflows in the past. We can also pull data from other sites and site collections which eliminates the need for duplicate data sources. The workflows are also a huge improvement from what we had before. The user tasks allow you too see a single workflow from the start of the process until it's completed. It also allows you to see who approved the requests and send reminder emails without building extra workflows or steps. This is a huge improvement in terms of ease and ability to audit processes.

Easy automation process to cut down on our internal processes.

There have been no issues that we have any issues with.

Reduce paperwork.

I love that Nintex lets me integrate with a range of cloud services with there simple drag and drop approach but if we need to cut some code xtension lets us do that too!

Nothing that I can think of at this stage

Its about the long tail of problems, Nintex lets me solve problems quickly. One project we are currently rolling out is an asset management solution that uses bar code scanning, stores data in Office 365 and integrates with Xero.com

The products are intuitive, easy to use for simple or even moderately complex processes, but with the extensible tools you can connect to your data no matter where it lives.

Sometimes support can be slow to get back to you. However, the community and online resources are great

As a partner, we solve lots of problems for customers - and the ROI on Nintex is second to none.

Drag and drop is probably the best and easiest thing in the world to do.

I've disliked error lookup in sharepoint logs to figure out my issues.

Travel forms are now all done digitally and approved through the necessary people all through Nintex Forms and Workflows. The IT Form we have is very nice as well for setting up a user on the network as well.

K2 provides an excellent, well round platform, feature rich for the simple to the most complex SharePoint workflows. Computations, logic, branches, loops, advanced conditions, web services, data integrations, multi stage multi step workflows are all possible with this system.

K2 has a bit of a learning curve. However, the online documentation and examples keep improving so this is a good thing.

I have solved fairly complicated problems such as migrating database drive Lotus Notes applications to SharePoint On Premise and Online using K2. Was able to use web services api to interact with the Microsoft Office 365 apis from SharePoint via K2.

I like the possibilitiees that nintex workflow gives me to do about just anything I can imagine.

Some parts of the manageability for things like history and task lists can be hard to manage when you run large amounts of workflow executions

HR including onboard, offboarding and hiring. Sales people incentives, Shared service offerings, Financial system& ERP change requests.