K2 Platform

It is well suited when being used outside of SharePoint by custom applications or when all you are looking for is Forms and workflows. As a SharePoint embedded workflow engine it has a long way to go to compete with the likes of Nintex

K2 offers ability to version control process definitions and process instances. It also provides mechanism to recover from errors (such as retry, or move process instance to newer definition). This feature is critical especially for long running processes involving multiple approvals/user actions. K2 also provides excellent, powerful reporting out of the box. Custom reports can be built leveraging the existing skill set such as SSRS.

Unlike many other specialized workflow platform (SharePoint workflow, Nintex etc), K2 BlackPearl platform is powerful and allows integration with any system that supports standards such as .NET, Web Services etc. Developers can build reusuable custom activities, custom functions etc. or leverage growing list of community developed library at K2 Underground. K2 also allows Visio based plugin to allow Business users to define process flow and then have it imported into Visual Studio for developer to implement it. K2 also provides multiple ways to define processes targeting different audiences (K2 For SharePoint designer, K2 Studio for less complex processes and Visual Studio for developers)

Cons

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 or Groovy out of the box.

Better integration with TFS automated build tools is one feature that is missing out of box. My organization has controls on code migration and deployment and use TFS for other code and builds. We cannot use the automated build for K2 workflow projects.

Ability to define business rules in external rules engine/repository which can be used by workflow processes

Usability

Appian8.8

Based on 28 answers

The interface is as difficult to use as you make it. We like to follow the KISS principle and automate the mundane so that our staff can concentrate on their day job and not have to worry about what happens next.

K2 platform has multiple designers (Web based designer ,k2 studio, visual studio) each targeted at business analysts,power users, and developers. The platform provides consistent web experience in workspace navigation for users and admins and provides excellent reports out of box.

Support

Appian8.4

Based on 52 answers

Appian updates happen automatically and regularly (about every two months or so). We are informed when updates are coming to understand the timing, and in our short timeframe (about 6 months) we have had no issues with functionality breaking

It was a complete online training with virual machine provided by K2. All the infrastructure was set up before hand. The training material was pretty thorough. The instructor was knowledgeable. Overall the training program was well designed and planned.

Alternatives Considered

When evaluating Appian we were asked to compare it to other enterprise tools we currently use such as Atlassian's JIRA and Rally. It is really impossible to compare the two for the simple fact that within Appian you can build the workflows and data capture mechanisms that each of these tools offer. The difference is that with Appian you can customize the workflows to an infinite degree whereas with an off the shelf application you are relatively limited to what the developer provides.

1) Nintex Worklows for SharePoint: This product is integrates with SharePoint really well. Also it is less expensive. Developers/Power users doesn't have to leave SharePoint to develop the workflows.2) SharePoint workflows : Most of the cases we are able to address the business requirements using SharePoint workflows.

Return on Investment

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!