Appian vs Nintex 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 Workflow's UI is far easier to use than SharePoint Designer's UI. You can drag and drop actions to where you want them, move them around, copy them...all in a very intuitive way.
• SharePoint Designer workflows are linear, which is too inflexible for many of our business process. Nintex Workflow's looping, parallel actions and state machine allow for a very dynamic workflow that can do far more work for you in a single workflow. I particularly like the state machine, which allows you to go forwards and backwards or even jump around in a process based on user responses.
• With Nintex Workflow, you can query lists for items that match specific criteria then loop through those items to perform actions on them. This workflow can then be scheduled to run at specific times, automating many of the tasks you now do manually. For example, we have document libraries where the documents have expiration dates. We wrote a workflow to alert the owner that the document was going to expire at 180, 90 and 30 days from the expiration date. This workflow runs nightly.
• Nintex Workflow integration actions extend the workflows outside of the site collection. You can use web service calls to interact with lists and libraries in other SharePoint site collections, even in different web applications or farms. You can query Active Directory to get more user information. You can even make direct SQL calls to bring in more data.

Read full review

• There is an improvement required for Reporting part.
• UX can also improve such as in consideration of some CMS system. Sometimes business usually compares the UX with some CMS systems like SharePoint.
• Tableau or any other visualization tool integration is Key to provide Single customer View.

Read full review

• Images in notification are not impossible to accomplish, but because Nintex Workflow (and/or SharePoint) truncates the url for relativity purposes makes it difficult to just add the location of the image to the source editor.
• Nintex Workflows in my experience do not behave consistently with SharePoint document libraries that require more metadata around a document to entered. The workflow in some instances start once the metadata information have been entered (which is what I expect) and at other times start once the document has been uploaded and prior to entering the metadata.
• Nintex Workflow conditional start is not always consistent. There have been some instance where I have had a workflow set to start on a condition and when the condition was met the workflow failed to start.
• Error messages from Nintex Workflow failures are at times vague which makes it difficult to troubleshoot quickly especially in more complex workflows.

Read full review

• Appian has given us a great return on our investment. It has given our senior management more insight into where we are spending our money and how much our projects are actually costing.
• Automation of many of our daily tasks.

Read full review

• We had a positive ROI for SharePoint Administration and Governance. We were able to cut our administrative workload significantly.
• We had a positive ROI for our SharePoint PowerUser group. They were able to create complex workflows based on business processes that were compliant with numerous regulatory statutes.
• Our Project Management Office estimated that one of the solutions they used that was based on Nintex saved approximately 8 hours per week per project manager.

Read full review