Appian vs Nintex Process Platform

• I have observed after version 17.1 we have a lot of good features in Appian that improve usability (UX). This adds real value in this competitive Digital space.
• You can understand business use case and convert it to a logical process automation.
• Process Modeller has improved a lot and providing smart services use adds more value.
• Service integration helps us to seamlessly integrate with third-party systems

Read full review

• Nintex Platform allows you to easily turn a SharePoint list into a dynamic and robust form that is attractive and end user friendly.
• Nintex Platform is entirely web based and requires absolutely no additional software but is feature rich.
• Nintex Platform has a large user community who will answer questions.
• Nintex installs directly on top of SharePoint instead of requiring an additional server.
• Nintex integrates with SharePoint seamlessly.

Read full review

• Advanced functionality requires use of the Appian expression language. The more advanced the logic, the harder it is to build with the expression language. This means development expertise is more relevant if you need advanced functionality, which I imagine applies almost all the time. I would much prefer if they allowed some common language such as JavaScript out of the box.
• Debugging has proved difficult. It’s easy for developers to get the app to or feature to a “working” state but it needs robust alpha testing.
• Deployment can be tricky. When a solution gets big and there are many teams and dependencies, it needs a careful process to ensure things don’t break.
• Reasuability of Appian objects is both a pro and con. Reusing objects across apps may be more trouble than its worth because of creating heavy dependencies. Experience is helpful to strike the right balance.

Read full review

• Hide/display rules on forms rather cumbersome
• Need to be able to add comments to workflows
• Printing of workflows: the resulting format is not usable at all
• Responsive forms - not sufficient density - too much white space
• Need ON DELETE trigger!
• Need a better way of implementing smarts within the form (e.g. update fields if a particular value is chosen in another field) than javascript and the JS editing/debugging process is horrible

Read full review

• Our objective to reduce customer effort when dealing with government by 25% was exceeded. In the process of applying for an alcohol licence renewal alone, we saw approximately 80% reduction in time and effort for the business customer - and that was just a prototype! Imagine the possibilities when this is taken into a live environment!

Read full review

• With our diverse organization, being able to establish consistency is key and we can do this by creating a standardized form, process, and workflow with automation. So the process is easier and all of our people are doing it the same way. That is a game changer.
• The licensing is a little hard to follow and can make the product unaffordable.
• The approach of Nintex hosting the solution makes Nintex design their product for maximum usage. They have to make sure they can have their product embedded in a number of different systems; so, they use industry standard protocols and development.

Read full review