Appian Review

Workflow engines work extremely well to bridge the gaps of processes within our core systems


What is our primary use case?

I work for the largest distributor of Toyota Lexus in the Middle East. My area is related to car motors. I'm an IT senior general manager and we are customers of Appian. 

What is most valuable?

The workflow engines are a valuable feature. We use them to bridge the gaps of processes within our core systems that are either too difficult or too costly to develop within the core system. We bridge those gaps using Appian. 

What needs improvement?

We'd like to see the employee experience improved, something we can integrate with SharePoint. Right now we're looking at the Power BI which belongs to Microsoft. It has a lot of good features for low-code no-code development kinds of things. I'd like to see the ability of the software itself to integrate with the core systems. It's a gap that Appian hasn't fulfilled. 

I'd like to see integration with Microsoft products as an additional feature. Microsoft Team, or something like that. It's not there or if it is, it requires some work to enable easy integration with SharePoint. 

For how long have I used the solution?

I've been using this solution for eight years. 

What do I think about the scalability of the solution?

The scalability and stability of this solution are good. 

How are customer service and technical support?

I'd say that the technical support is good. 

Which solution did I use previously and why did I switch?

We visited the workflows that are provided within SharePoint but they did not fulfill the kind of things that we were looking for, or the problems that we were trying to solve at that point of time. We were planning to work on specific domains, specific areas, but you cannot make it work for complex things. 

How was the initial setup?

The setup is not completely straightforward but not too complex either. The deployment itself wasn't too difficult, but this is something where features evolve and the things within it over time start moving. Adapting to any new feature while continuing to work is not simple. It makes things more complex. There are around 5,000 people using the product and we have five people dealing with maintenance. 

What's my experience with pricing, setup cost, and licensing?

The price should be lower. It's not too expensive but I believe the price could be better. 

What other advice do I have?

The product needs to be supported by top management for it to work. This is one of the things that we faced at the very beginning. Second, from a technical point of view, you need to have a dedicated team taking care of this from a product management point of view, not necessarily from a technical point of view because that can be outsourced. I recommend not doing the development in-house, rather to outsource it with one or two partners and the corporate team. I recommend going for the full cloud-based solution architecture rather than having part of it inside and part of it outside. If there is no issue with data sharing then I would recommend going for a fully cloud-based solution. It gives an advantage and reduces a lot of management headaches. 

I would rate this solution a nine out of 10. 

Which deployment model are you using for this solution?

Hybrid Cloud
**Disclosure: I am a real user, and this review is based on my own experience and opinions.
More Appian reviews from users
...who work at a Financial Services Firm
...who compared it with Pega BPM
Learn what your peers think about Appian. Get advice and tips from experienced pros sharing their opinions. Updated: January 2021.
457,209 professionals have used our research since 2012.
Add a Comment
Guest