Appian vs Nintex Platform

• Appian is great for sharing information across processes. The platform is designed such that objects from one application can be simply referenced in another (if your security permits it, of course.) This makes information sharing across processes quite simple from a technical implementation perspective.
• Development cycles on Appian are shorter as compared to traditional methods. We're able to churn out solutions at a higher velocity.
• Building a user interface is fast and simple. It has limited widgets but meets our needs 95% of the time out of the box.

Read full review

• The WYSIWYG workflow designer makes workflow generation straightforward.
• The ability to call external APIs makes integration with other systems outside of SharePoint easy.
• Using SharePoint as a platform allows us to quickly distribute the workflows throughout the organization.

Read full review

• We haven't found the on-premise upgrade process straightforward. The versions seem to change fairly significantly and the installation guide isn't a good as it could be.
• Appian doesn't seem as resilient as other applications. For example, a VMware server recently had a failure and automatically failed over to a secondary. Every application running on the server recovered without intervention, but Appian didn't and was unavailable for around 2 hours whilst we worked with Appian support to diagnose and fix the issue.
• Lacking flexibility around proxy servers but this seems to have been resolved in version 17.3

Read full review

• The workflow designer seems to have some rendering issues in non-IE browsers.

Read full review

• Appian is an accelerator for us. We don't need to build in the business process management in house.

Read full review

• We purchased Nintex Workflow along with Nintex Forms and together they have provided us the ability to eliminate several paper based processes. The combination of customizing the form and building a robust workflow behind it has brought forth immediate cost savings and really has the departments excited to further leverage the product.
• We have a couple of Nintex Workflows built out for SharePoint site requests. The user fills out a form for a new SharePoint Site Collection or Subsite providing details on what type of site it is, why it is needed, the target audience, etc. The request goes through a few approval steps and once approved the site is automatically provisioned. The requester is notified as the workflow progresses so they know the status.
• We use workflows to assist with our document lifecycle. For example the workflows are scheduled to execute on a regular interval and look for items which certain metadata attributes and meet certain age criteria. The content manager is notified when items are approaching an even such as archive or removal and given the opportunity to extend that time.

Read full review