Appian vs Kissflow

• 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

• Ease of Use: It's easier to use and see workflow tasks that are assigned to you, workflows that you've participated in, or workflows that are pending other peoples approvals. From a development side, it's easy to pick up and begin creating processes if you know Excel formulation, which is easily researched as well.
• Ease of Access: Since KiSSFLOW is hosted in the cloud, you can access the site from any internet connected device. All you have to do is sign in with your account, as opposed to needing to be on the network to access like our previous system.
• The App: This is a feature we really hope to get a lot of use out of. With the way our business is structured, there are a lot of Regional positions that are always on the go. Because our current system requires a user to be on the network to access, this makes it hard for these roles to respond to tasks, causing bottlenecks. With an app available, along with push notifications, we can keep these tasks responses on pace with the associates required in that task.

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

• The reporting could use some improvement. The actual reports are OK, it is access to the reports that is the problem. This is related to the permission schema. It really just has user, admin, and nothing in-between. There really needs to be something like report admin or something. Excel exports for data are needed as well.
• The user workflow selection UI is not the best. There is a big red + sign in the lower right of the browser window that is not labeled. That is not clear. Also the selection list is just a pop-up window, it really should be a full page.
• The mobile app does not have all the features that the browser version has, especially admin tools.

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

• Kissflow has helped us keep careful records of costs and pricing for various products, which indirectly impacts our margin.
• Our owner had trouble with the phone app, so ultimately we stopped using Kissflow for purchase requests. There is some lost potential there.

Read full review