Descripción general de precios de la plataforma de procesos Nintex

It's a cost-effective, easy to implement e-sign option that's customizable.

Reporting could be a little bit more robust, but it's adequate.

Obtaining signatures on critical insurance documents at Point Of Sale. It supports a superior customer experience for both agents and consumers, and reduces both UW expense and coverage exposure.

To the reviewer: Please delete this review. I see no problems with my review but I'm being rejected over and over again. I no longer have interest in reviewing the product if you're going to toss my review out... I've answered all the questions, and submitted my validation but for some reason its not registering one of the questions, even though I've answered them all and I see no real issue with my reviews. Your system needs to provide a more detailed reasoning behind rejections so we can know what's wrong with the review. Please remove the review, and remove my account from your system. I have no desire to do any further product reviews for you. This was a complete waste of my time. Nintex has a great setup for workflows. It allows for additional features that the default sharepoint workflows do not like looping. While loops, and for each loops make nintex workflows invaluable and far superior to sharepoint designer.

There are several limitations like being able to return distinct values in a drop down box for nintex forms. Plus they seem to reserve a lot of very useful key features for the enterprise level package even though they advertise their basic level as enterprise level software and charge enterprise level prices for the basic packages.

We solve many projects using nintex workflows and forms. Ranging from database cleanup, to database monitoring and basic document library check ins and outs, versioning for code and other basic sites as well.

How user friendly it is, and how easy it is to create workflows.

The Cost is to high in Office 365 and is based on usage and not price per year. We therefore are not considering nintex as an option. Would love to use it but since the pricing is so unclear it will not be approved within my company.

IT is quick to create workflows.

Would you like to design and publish a simple form and workflow in minutes? This product does that with ease. Learning the basics is quite easy. In your first session you should have no difficulty putting together a simple form (the time off request or expense approval are common examples) and showing it off to colleagues. Need to add in complex business requirements? It'll take longer to figure out, but the platform does provide some great features to help you get where you need to go. There are exceptions to this, however (see my comments below). Overall, I'm able to find solutions to 90% of my requirements with out-of-the-box Nintex. The support team is solid--if a bit slow to respond. My company pays for Premium Support, which promises an 8 hour response time. They meet this by sending you an email acknowledging the request and stating that the issue has been passed to an engineer. I've found that the engineer will take anywhere from a few hours to a few days to get back to you. Overall, I've been satisfied with the overall expertise and professionalism. I would recommend paying the extra for the support--if you use the product a lot, it'll save your power users and developers many hours by being to ask a question instead of attempting to solve it through trial and error or by searching Nintex Community.

You are confined by the product's limitations--especially on the O365 platform. You'll want to meet a business requirement for the workflow and turn to google searches to find the solution, only to discover that the Nintex platform doesn't support it on the O365 platform. Often, the feature is supported in Nintex for SharePoint on-prem, but that doesn't help those of us working in the Cloud. There is also no obvious roadmap for O365 enhancements and feature releases have been very slow in the past 12 months. As a workflow builder, you quickly learn to abandon pushing for solutions to what does work and instead focus on different ways to accomplish the same business requirements--it's just a much better use of your time. Lots of platform limitations can be solved with Javascript and CSS (which the platform allows), but these solutions steer the product away from the power user and toward a developer. If you've purchased this product to get away from paying a developer to do this work, this may catch you by surprise. Other issues can't be solved at all. One of the bigger limitations with the O365 platform is building workflows with conditional or timed starts--these features are simply not yet available on the O365 platform. I've found that our developers solve many of these problems by writing specific workflows in native SharePoint, which is great but really diminishes the value of purchasing Nintex in the first place. Finally, there are warning signs that come with any app build on O365 SharePoint. First, if you end your relationship with Nintex, your workflows stop working. Second, Nintex support doesn't have much visibility into the O365 back-end. I've been told by multiple support engineers that they simply can't see what's going wrong in many occasions like the could in on-prem; MS doesn't make the logs available. I could go on, but as you can see from my rating of 7 I'd still recommend this product to those who feel it meets their business requirements.

Mostly Forms and Workflows for regular business processes. For example, a user submits a form with information, which is then circulated through a series of approvers. Once the approvals are complete, the Form serves as a historical reference of both the information contained in the form and the documentation of approvals for future audits.

The nintex workflow engine is a very capable tool that makes creating no-code solutions a breeze. It allows the IT professional and developer alike to create robust solutions to real-world problems. I recommend this product to anybody who will listen - this should be included with SharePoint by default.

There isn't much for me to complain about other than the price... but as with all good things you get what you pay for. Price has been the hardest selling point of nintex, but once management sees the end result they are usually very happy. I have also attempted to be a business partner, reselling nintex products - however I gave that up when I was shorted by commission fees which were supposed to be 10% - I got 0% and after three months of asking with no response, I finally got a lame answer that I didn't qualify for it - after my rep got back from vacation...

In the last three companies I've worked for, we've used nintex to automate many pen and paper processes, we have also used it to automate metrics collection, automation of AGILE/PMBOK support processes and have utilized it to help manage our ISO and ITIL infrastructure (CMDB) and internal audits.

The uniqueness of the K2 platform is that it has the ability to work as a stand-alone system, separate from SharePoint. It is one of the things that that drew us to K2 is the fact that it is its own platform but that it also plays well with SharePoint. The fact that it also connects to a WIDE variety of other external sources is a huge advantage. You can connect multiple lines of business to each other and simply your business processes. And that is a huge value.

Most of my team has been trained on and very used to K2 4.7. K2 Five represented a large challenge because everything is web based. There is no more forms designer (Please bring it back ASAP) and the designer in the web lacks many of the features that the forms designer had. So K2 really needs to bring back the forms designer from 4.7 or hurry up and get the web version caught up with features. Also, they need to get on-prem releases out MUCH sooner than once a year, especially since they deployed what I would feel to be an incomplete version of K2. I feel like it was released too soon when we purchased it. And the install on-prem was a huge challenge for us as well. But K2 5.2 is much better and so they are definitely on the right track.

We are rebuilding security assessment processes. Also rebuilding our architecture design and review processes.

I like the current pricing that the product has for onPrem. I bought license for the farm and users can use the workflow wherever they want in the farm. I don't like the idea of moving to paying for the number actions. The win of this product is that endusers are empowered to make workflow for themselves. Changing the pricing model will mean I need to be concerned more about how workflows are programmed to ensure best value but this development back on the SharePoint team.

I have had difficulty getting actions to work as expected. I have also had difficulties with the scheduled workflows not working. The solution being to reinstall which means downtime. This has also had a negative impact on how users are responding to Nintex.

Business process automation and integration with other systems for syncing data into and out of SharePoint. We don't have forms at this time. We are also still 100% onprem. We will eventually be in the O365 but that will be a small footprint because much of our content needs to remain highly secured and confidential.

The versatility has practically no virtual limits and is priceless in the industry.

The only thing that comes to my mind is the cost but at the same time it is well worth it.

The platform manages and automates a lot of my company processes and facilitates day to day operations.