Appian Reviews

Normally, we are building platforms. At the moment, we are running 19 big projects, and we had never used Appian before. One of our customers is a big consulting company, and one of their customers wanted a project with Appian.

They don't have Appian developers, but we have a very good team. They reached out to us and they had some projects in 2022 with Appian, and they asked for our support. I gave my BAs and PMs an introductory level Appian course, and now some of the developers are doing the associate and lead developer part for Appian.

The application life cycle is very clear. I started learning it and giving some workshops to my team. Creating the users and the building is very structured. Documentation is nice and it's easy to learn.

There's a nice fundamentals course that I can ask my project managers to easily learn, while the other local, no-code platforms don't have that option.

The certification is pretty expensive, and it doesn't allow for a tailored UI. I'm a little bit disappointed with the exam. It's different from the preparation, training, and sample exam.

One of my lead developers failed to pass this morning. I'm a bit sad because it's $200. If I ask 10 of my developers to get a certificate, it's $2,000. It's a scaleup company, so we have more than 60 people at the moment, but I can't ask most of my developers to get the certificate.

From a developer point of view, I can't try this in the free version because you can't buy one or two subscriptions. You need to get the minimum package for premium, which is about one hundred seats.

From the first day, I wanted to see the capability of reaching other functions, Google Cloud services, and cognitive services. There is already an OCR, intelligent document that comes in the My Cloud and which Appian gave me as a sample. I can't build it because it uses the Google cognitive services as a backend, and this is the thing that we couldn't try. 

You can't really test the software properly without actually buying the license first.

Something I would like to see improved is an SQL database connection.

We have been using Appian for over a month. We are still on the trial license instead of the full license.

I'm happy about the stability. It looks promising for me.

I can't predict how many developers it requires. It really depends on the type and size of the app and the capability of the developers.

We run a one-hour workshop from scratch. My developer can create the users' data, custom data types, a small UI, and a nice flow and read right from the databases easily. In one hour, he can complete as many tasks that normally take many days.

The scalability is a bit limited for the SQL databases because for some of my cognitive services, I'm using no SQL databases in the cloud. Appian doesn't support it. Appian only supports relational databases. There is no database for the unstructured data.

We are building platforms, but normally we are fully in Azure and the whole platform is in Azure, but because some of our customers and potential customers want to use Appian, I'm preparing my team for such opportunities.

You can't really test the software properly without actually buying the license first. Certification is expensive.

Appian is like a butter knife, not a Swiss Army knife. It will serve the business user's solution. It'll create a very good thing and the application is clear.

I really enjoy it because the PowerApps from Microsoft mature and are internally connected to other platforms inside Microsoft.

However, it doesn't explain the learning part very well non-technical people. There is a separation, but in the Appian fundamentals, this course is just for the BAs and the PMs. If they want to lead a project with Appian, this is the minimum standard that they need to know. At that point, it's easy for me to train project managers and business analysts. I think that's the advantage of Appian.

I would rate this solution 8 out of 10. 

My humble advice to someone who is looking to implement this solution is that they need to replicate. It's a so-called no-code platform, but it's not no-code because it has its own coding site. That's why they need to build one of their own solutions with Appian first to understand the how-to-dos first and become more confident. Luckily, the learning curve is not that steep.

Appian is basically for workflows and workflow approval.

In a banking scenario, suppose as a customer, I apply for a loan. That loan needs approval from a manager. In addition, I will need to provide documents like my Social Security, personal details, company details. There are levels of information that can be maintained in the back-end. If you are the manager you can check that I provided all this information and, based on the criteria, you can approve a loan of 300 or a loan of 400, all within the back-end.

An advantage of this tool is the area of workflows, mainly for back-end users. It is not for end-users.

Another advantage of this tool is its reports and records. You can maintain dashboards, layouts. If you with a Java solution, it takes six months time. If you use this tool, you can finish in one or one and a half months' time. It took us six and a half months time to develop a small application in Java, but within this tool, we developed it in one and a half months, including the records and reports.

Also, there is a version coming out every six months with performance improvements.

You can develop a back-end UI and back-end reports using this tool.

It needs a better UI. There has been a lot of development in version 18.1 but we still need more for it to compete with other BPM tools.

Stability depends on the development. If you do proper development the stability is okay. Whenever you are getting data from the database, you have to write more code rules, more views. It will take a long time. Going forward, you can have performance issues. Initially, it works fine, but going forward, you are hitting performance issues whenever you create the views to get the data from the database. That's what I found in my previous project.

I used Oracle BPM. I switched because, as a developer, the market was becoming completely saturated and I was not getting any jobs.

The setup is straightforward. No complaints, no issues.

I hear the price was hiked a little recently. Initially, it was low. But it's okay compared to Pega.

IBM has Business Process Manager, Oracle has its BPM as well.

If you are looking for back-end solutions, this tool is 100 percent a fit. So Appian BPM for the back-end and, if you want a front-end, I don't suggest using Appian BPM. The Appian back-end is only for internal users, not for end-users. For end-users, you can use Java.

Appian is really helpful in automating different processes. Our clients use it for process automation and leveraging updated features like Appian Portal and Appian RPA. The main use case revolves around external application building in nature, making it comparable to other mobile app general interfaces, particularly those heavy in user interface and user exchange. Also, Appian Records integrates all systems, providing a consolidated view, dashboard, monitoring, and report.

Appian helps in consolidating systems within the client's network, correlating data points, and offering visual dashboards to get a real-time view of various factors. Clients can check the functional state of their current infrastructure and monitor it in real-time, which also relates to the financial side of operations with business reports and similar functionalities.

The valuable features include process automation, Appian Portal, and Appian RPA. Appian allows easy integration with other systems, offers a visual dashboard, provides real-time analytics, and is flexible to be used by non-technical users for automating simple process flows. Additionally, Appian's data fabric now helps in correlating data across various systems for consolidated monitoring.

From a reseller's point of view, subscription licensing could be improved to be more cost-effective, especially for new prospects and smaller investments. Appian has new subscription models, but they might not always be feasible for smaller customers. Competitive pricing on the external user side is good, but internal user pricing needs to be adjusted for better market reach.

I have been working with Appian for nearly six years.

In terms of stability, Appian is quite reliable. I have not encountered any major downtime in customer environments. Their support team has been effective, making the solution stable overall.

Technical scalability is generally good, maybe an eight out of ten, however, some clients encounter issues due to high costs, affecting their ability to scale effectively.

Customer service in the Philippines is rated around a seven due to response times and the lack of a direct support line.

Neutral

The initial setup is generally simple and well-supported by the platform's flexibility and ease of use. My technical colleagues find Appian easy to learn, though they need to continuously adapt to new features.

Appian is promising yet the cost can be a barrier. The subscription cost is higher compared to competitors, which can hinder potential market expansion, especially for new prospects.

The main competitors for Appian are Pega and OutSystems. Appian is set apart by its RPA capabilities, though it is still catching up with the likes of UiPath.

Appian is a promising platform with significant functionalities, but it would benefit from more cost-effective pricing for smaller clients. The technical support could also be improved, especially in providing direct and faster response options.

I'd rate the solution nine out of ten.

I mainly use Appian for end-to-end process automation.

We use appian for IT services implementations of our esteemed clientele in CX transformation, process automation ,EX transformation and app modernization areas

Appian's most valuable feature is that we can create end-to-end process cloud ntive  workflows with minimum turnaround.

Appian could be be further improved by making it a strict, no-code platform with in-built process packs.

I've been using Appian for six years.

Appian is stable.

Appian is scalable.

Appian's technical support could improve, especially their response turnaround.

Positive

used multiple options. Since i represent  product agnostic  IT services organization, cant comment furthur on this

The initial setup was relatively straightforward, and deployment took around an hour.

NA

first year itself break even happened.

no

Anybody thinking of implementing Appian should have an enterprise-wide roadmap. If you're doing an enterprise-wide digital transformation, Appian is worthwhile, but not for just one or two use cases because the license costs are higher. I would rate Appian as nine out of ten.

Appian is a very low code platform. It's very easy to learn and use. It provides a lot of built-in functionality to address common business use cases, like user and task management, record and data management, and robust reporting on both business and process data.

Appian has greatly improved how quickly we are able to build and deploy technology solutions for our business partners. We're delivering a lot more than we used to and at a lower cost. It has proved especially useful for building regulatory applications, which are usually very time-sensitive and have to be delivered very quickly with hard deadlines.

The main challenge with Appian has been our inability to customize the user interface. It has it's own built-in UI components and doesn't provide much flexibility to customize or extend those components. This is becoming less of a problem in newer releases of the product as they continue to enhance their UI capabilities and introduce new slick features, such as sites, billboards and embedded interfaces.

More than four years experience spanning development, deployment, and administration for versions 7.4 through 17.3.

No, we have not encountered any significant stability issues with Appian. The product is very stable across all its different versions.

We have been able to easily scale Appian to meet our needs and haven't hit an upper threshold yet. We've encountered performances issues now and then, but we have always managed to resolve them through code, configuration changes, or additional hardware.

Appian technical support is generally good, especially for high severity issues. They are usually able to quickly bring in experts who can be very helpful in quickly narrowing down issues and driving resolution.

We wanted to consolidate multiple existing legacy desktop applications into one unified web-based platform and Appian was one of the best options available.

Pretty straightforward, since we had people with the necessary foundational system administration background, and Appian was very engaged early on to help us get up and running.

I don't have enough exposure to pricing and licensing.

Oracle BPM, Pega, and D+H.

Excellent BPM tool: The best among all the ones I've tried.

To get the most out of the product, put the right team in place first. Follow the Appian recommended setup/development/initial rollout best practices and do things right the first time.

Using this solution allows us to have faster testing on multiple devices.

The solution is simple to set up.

It's a stable product.

The product is open-source.

The solution needs to have more features. If you compare it to, for example, Katalon, Katalon had more features. 

We'd like improved functionality for testing new devices. For example, the last Apple phone is always a pain. The CEO of the bank has it, however, he wants the application running there. The testing of the latest models needs to be possible.

I've been using the solution for about a year. 

It's my understanding that the solution is stable. We haven't dealt with bugs or glitches and it doesn't crash or freeze.

I've never directly dealt with technical support. I can't speak to how helpful or responsive. 

We find the product simple and straightforward to set up. It's for a mobile application for bank solutions and mobile banking.

We are using the open-source version. We only invested in a couple of tests. However, we are using the open-source version which doesn't cost anything.

We also compared the solution to Katalon, and Katalon had a few better features than Appium. I cannot name each specific feature, however, I know that Katalon had some features that made it even faster.

We are customers and end-users. We don't have a partnership with Appian.

I'm not sure which version of the solution we're using at this time. 

I'd rate the product nine out of ten. We are quite happy with its capabilities. 

We use this solution because End-to-End Process Automation in Appian is robust and scalable. Thousands of process instances can run concurrently. Apart from that, development is fast for process and workflow automation when the developers are experienced, and the code can be reusable.

This solution has helped in creating a process platform for the bank because it can handle cross-department processes. Process culture is making noise inside the organization because now, everybody knows that their time is being monitored. 

This solution provides for fast development with Quick Apps and simple CRUD user interfaces. 

Some of the other features are:

• Fast development with SAIL
• Beautiful user interfaces that are limited in customization but have the benefit of fewer problems with usability
• Having data in memory using KDB technology is also a good idea
  

I would like to see better monitoring for business events in synchronization with business rules.

There should be a better development for Cases, because it is not really a capability of the product. You have to develop the behavior.

The documentation needs to be improved.

This is a scalable solution that can run thousands of processes concurrently and fault tolerant

I used IBM BPM 8.5.7 prior to adopting this solution.

The cost depends on the number of users, although I recommend taking an unlimited license.

We evaluated both Pega and Activiti before choosing this solution.

In general, Appian is a great competitor in process automation. However, in my opinion, compared with IBM they lack documentation, development methodology guides (scrum is not enough for BPM adoption) organizational change management is a prerequisite for any BPM journey, real examples like IBM Redbooks, the academy is great I think that more real business cases would be better, webinars etc

In my opinion, it is not good to let developers design their own business database. Normally, they are not experienced at this. Perhaps for mid-size business, there is no problem, but when you have a big business it gets complicated and a database designer is required.

We primarily use the solution for approvals. 

The data types that we've built in Appian are very vast. We can customize the solution or point to predefined data sources. That makes it very unique.

The reusability is great. You can build it in one place and use it in many places. 

It is stable and reliable.

The solution can scale well.

Technical support is helpful.

It is easy to set up.

There is no UI customization possible. We'd like it to be more flexible for branding purposes. 

I've been using the solution for almost two years. 

The solution is stable. There sometimes is downtime during upgrades, however, it is reliable. I'd rate it eight out of ten.

The solution is scalable. I'd rate it eight out of ten. 

We have about 500 users right now, and we expect to expand usage in the future. 

We've had good support from the Appian team. They have a good support model and are easy to reach. 

I'm not sure if there was another solution used previously.

The initial setup is very straightforward. It's not overly complex. It's a cloud-based tool which makes it very light. There's not a lot of overhead.

We had basically a one-click deployment. The implementation is deployed via predefined screens. It makes it very simple.

There are also good import/export features that are helpful. 

Appian mostly manages the deployment, and one or two people are required to manage the overall platform once deployed. 

We did not use any outside assistance. 

It does take time to get an ROI. Depending on the licensing type, chances are you will begin to see an ROI, especially for time to market.

I don't deal with licensing. I'm not sure of the exact cost. 

I'm an end-user. 

We are using the latest version of the solution. 

While there are a lot of factors when it comes to choosing a solution like this, Appian is a very robust platform, and it does offer advanced use cases. If you are more into Microsoft, however, Power Apps may be a better option.

I'd rate the solution eight out of ten.