Appian Reviews

My organization only has a few use cases for Appian, but one of the use cases I'm working with is for a corporate real estate project.

Appian has benefited my organization because of its low-code feature, so my team only has to do minimal coding, resulting in quick deliverables.

What I found most valuable in Appian is its latest feature, which lets you drill down on multiple things through the structure of the reporting and UI side of the solution.

Appian has a few areas for improvement, which my organization raised with the Appian team. One is the Excel output which is limited to fifty columns when it should be up to two hundred or three hundred columns. Fixing this limitation will make the solution better.

What I want to see in the next release of Appian is on the interface side, where the current square-shaped buttons should be round. Having available buttons for the different functions of Appian will also help enrich the UI.

I'd been using Appian for two years now.

Appian is a stable solution, so I'm giving it a nine out of ten.

I experienced a few issues in Appian scalability, particularly in the data or records area, so it's an eight out of ten.

I don't personally have experience contacting Appian technical support, but my peer used to get in touch with Appian, and from what I heard, the support team had been helpful.

My organization only used Appian.

My experience with the initial setup for Appian is nine out of ten.

Appian was quick to deploy. It took a very short time because my organization has the SaaS version.

An in-house team deployed Appian in my organization.

There's ROI from Appian, but I cannot give data about it.

A different team handles the pricing side of Appian.

I'm using Appian right now.

My organization uses the 22.3 and 22.4 versions of Appian in production and the sandbox environment.

In the organization, Appian is deployed on a SaaS environment.

Deploying the solution requires two people.

Appian is a good solution, so I'm giving it nine out of ten.

My organization is an Appian partner.

Appian is a platform that focuses on human-centric workflows around processes. It facilitates requests for policies or incidents involving groups of people. The application manages the workflow between individuals to negotiate and confirm these policies.

Appian is managed and upgraded regularly.

The most productive aspect of Appian lies in its ability to develop interfaces, particularly user interfaces. Creating user interfaces is highly productive when these interfaces are integrated with the original database. In such cases, using record types proves to be a very efficient method of handling data. The synergy between interfaces and record types enhances productivity.

The case management studio is still immature, but it looks very nice. However, the VPN should be improved. The case management system needs improvement, but it has some promising features. Appian has the commitment to continuous improvement. With each new release, they enhance the platform for all users.Currently, making changes requires too much backend development work. They're working on streamlining this process, particularly with VPN integration. As it stands, storing everything in memory doesn't effectively handle large datasets. Transitioning VPN processes to a more traditional database approach would greatly improve scalability and usability in real-world scenarios

When the sentences are too long, they become difficult to manage. The scalability is low, when they become complex. The integrations are fine. There are some minor errors and details, but it does a great job in explaining errors within Appian. Internally, there is much information to help you understand what's going on, but not always. Sometimes, it's difficult to know what's happening, but these instances are rare.

Architecturally, there is an issue with Appian that it tends to put all the applications in the same infrastructure. Big customers resort to having several installations of Appian to deploy different applications in different infrastructures. They face the problem of managing assignments. Appian should make it easy to deploy different applications in separate infrastructures. Additionally, there needs to be a way to unify them because without using VPN, users are left without a unified inbox. Applications can't use the VPN and have to resort to their own solutions to show users their work, leading to inconsistency. Since each application is different, it becomes crucial to have a centralized point where users can find their work. Even if the applications are split into different installations, there needs to be a single way for users to find all their work.

I have been using Appian for two to three years. We are the using V24 of the solution.

The solution's stability is better.

I rate the solution’s stability an eight out of ten.

The solution is difficult to scale. 1,000-2,000 users are using this solution.

I rate the solution’s scalability a six out of ten.

I have used SoftEther VPN.

I rate the initial setup a seven out of ten, where one is difficult, and ten is easy.

The platform was set up by third party.

The solution is expensive. 

I rate the product’s pricing an eight out of ten, where one is cheap and ten is expensive.

We evaluated Outsystems. Appian is much proactive to create solutions applications.

The most frustrating aspect is its DPM offering. It fails to support VPN due to its limited scalability. You can only use the VPN for isolated cases. When attempting to apply it in a real-world scenario with multiple applications, it becomes unusable due to its lack of scalability. It boosts everything into memory. 

It is very easy to develop interfaces and access data with Appian. The local code acts as a communicator. The interfaces function as record types, and the logic you program use special rules, which resemble a kind of functional language exclusive. This combination of user interfaces and record types, along with the special rules, is very productive. You typically need to write much less code compared to other platforms

Intergration is good.

I recommend the solution, One should evaluate the VPN needs very closely. Not everybody needs VPN, but those who do should take a closer look to avoid surprises. You can use VPN in Appian, but it's somewhat different from what you might expect.

Overall, I rate the solution a nine out of ten.

We use Appian for the automation of processes. The solution is typically used to automate case management.

The most valuable features of Appian are workflow management and the ease with which you can build the UI.

One of the areas that Appian is working on is to improve its UI capabilities and give more flexibility to the UI.

I have been working with the solution for around seven years.

Appian is a very stable solution. We've never faced any huge glitches or bugs with the solution.

I rate Appian ten out of ten for stability.

Appian is a scalable solution. However, we have to be a bit cautious if large volumes of data are being exchanged and if there are any use cases to transform the data in between.

I rate Appian a six out of ten for scalability.

Appian's technical support is pretty decent. The support team responds on time and sticks to their SLAs, which is good. Appian provides good support from an infrastructure and platform perspective.

Positive

Appian's deployment is pretty good. To run your deployment processes, it has separate built-in utilities and tools to deploy packages across the environment. I work for a services company, and I have built applications for some of our clients leveraging Appian as a platform, which is used probably every day.

I am using the latest version of Appian. Appian is deployed on Appian's own cloud in our organization.

Appian has a very strong workflow engine compared to other solutions like OutSystems and Mendix. I would definitely recommend Appian to someone who is looking for strong workflow and process capabilities. However, I recommend other platforms like OutSystems and Mendix to someone looking to build their own mobile app or looking for a lot more flexibility with respect to user experiences.

Appian is a pretty good tool. It's a low-code platform where you can start building your applications pretty fast. It has got really good workflow capabilities and a very good process engine. The solution has started integrating with cognitive services, RPA, and other services, which are probably at their initial stages, but the platform's roadmap is really good. Appian is definitely a platform to explore if you are considering a low-code platform to be part of your tech portfolio.

Overall, I rate Appian a seven out of ten.

We use the solution internally. It is for internal front ends for capturing transactions and then managing the workflows and sending them to back-end systems. 

The rapid deployment of solutions is excellent. 

It's cloud-based, and it was a smooth transition from the cloud to on-premises. We've really enjoyed the automatic updates. We never have to manually upgrade to the latest platform. It saves us some work. The cloud setup is simple.

The solution is very stable.

It can scale well.

Technical support is quite responsive. 

We have a growing need for more DevOps for deploying branching strategies, and Appian is not great at that. If that had more DevOps capabilities, it would be an excellent product.

On-premises setup can take a while. 

We've used the solution for the last five years. 

We've only had one 15-minute downtime incident that was related to an AWS hardware issue in their 1AZ. That wasn't Appian's fault. That was it. It's been pretty stable and reliable. There are no bugs or glitches. I'd rate the solution's stability nine out of ten. 

The solution can scale. 

They've promised they will bring out Kubernetes, which we currently don't have. Right now, it vertically scales. There is no horizontal scaling yet.

So far, we've scaled from 4XL to 8XL without issue. I'd rate the solution seven out of ten. 

We have 400 users on the solution right now. 

We do plan to increase usage. The solution is mission-critical. 

Pi and P2 issues get responses within a couple of minutes. Support is very responsive. 

Positive

We did try to shoehorn Cibo into doing everything. We unbundled it into different domains. 

If you do the setup, there is a bit of a learning curve you have during the initial setup. On the cloud, the deployment is much easier. They spin it up for you and manage it for you. It's less work. For the on-premises deployment, I'd rate the ease of setup six out of ten. It took a few months to deploy. Cloud deployment, of course, is much easier since there really is nothing to do. We deployed over a weekend.

We deploy every month. It takes a couple of minutes to deploy the latest features. 

We run a lean show and only have about five people dealing with the solution. There's an architect, two engineers, and a few QAs.

We have an integrator helping us from India. 

I don't deal with licensing. However, my understanding is that it's not the most expensive. It is moderate. I'd rate the pricing seven out of ten in terms of how expensive it is. 

We're a financial institution, and we're customers. 

I'd rate the solution eight out of ten.

I'd advise users to choose their implementation partner very carefully. Do the due diligence on the implementation partner for the best results. 

We primarily use the solution for application creation and process automation. 

We have 15 different applications running from CRM applications to case management applications, and we are using some RPA functions. We have a big stack of applications we are using. 

The quick development cycle is great.

The ease of development is great.

It's a stable product.

The solution scales well.

There is no issue with setting it up. It's easy.

Pricing is very competitive.

Technical support has been amazing overall. 

There needs some improvement related to the chatbot features.

The performance could improve. If we could calculate the amount of data that will be realized, it would help us a lot. 

I've used the solution for three years. I've used it for a while. 

We'd had no issues in the past three years. It is stable. 

I'd rate the scalability ten out of ten. It's excellent.

We have the maximum license, and we do not plan to increase usage as we do not have plans to increase our workforce. 

Techncial su[port is excelelnt. It's one of the best companies offering support right now. 

The initial setup is straightforward. It's pretty easy. It's not complex. 

We have witnessed an ROI while using the solution. 

The pricing is very competitive. It is not overly expensive. 

We have the solution implemented in our firm. 

New users need to understand the technical aspects of the product in order to take full advantage.

I'd rate the solution ten out of ten. 

Our client, a telecom company, has use cases related to the telecom domain, and it's around workflow management kinds of use.

Their workflow, which can be easily built into a BPM, is one of the best features.

The development time for Appian is far less than high code languages, like .NET, Java, or some other languages. 

We delivered the first application within 12 weeks, and that was a really big project. If we went with some high code tools, definitely it should have taken more than 15 or 18 sprints, and every estimate, in that case, would be a two-week sprint. It took only around 40% of the typical development time.

The initial setup is easy.

It's very stable.

You can scale the product well.

We have a partnership with Appian. We have worked with Appian to deal with issues. They have already incorporated many things into their platform. One of the things we have discussed, which I can highlight, is related to Excel manipulations. They have incorporated their Excel manipulations so it's far better than the earlier version. Earlier, we had to go with a plugin for even a simple Excel or spreadsheet calculation. Now, they have included all those things in their own out-of-the-box functionality.

It's definitely a tool and does not require high code language. There could be a scope of enhancement for capturing the variety of use cases. One thing, for example, is Excel manipulation, which they now provide in their out of box functionality, however, that can still be improved. 

It's a stable solution. It's reliable. There are no bugs or glitches and it doesn't crash or freeze. 

We have a good number of developers in our company. We have around 75 Appian developers, and overall, if we talk about the Appian's practice, it's around 100 people.

We are dealing with a couple of different Canadian clients.

It can scale quite well.

Technical support is helpful. Their SLA is very good. IIf your system, your cloud, is down, which normally does not happen, however, in some cases where, due to some heap memory or some other kind of things, they can assist. I just faced one or two instances in the last three years where their servers dropped due to the heap problem. They responded within their SLA, two hours, however, usually, they fix those types of things in 20 to 30 minutes.

Usually, what we use, is Appian Cloud. That's provided (or set up) by Appian itself. If we talk about the Appian deployment from the lower environment to the upper environment, from the development perspective, and developer perspective, it's very quick. They have in-built DevOps, so it's a one-click deployment from the lower version to the upper version.

Appian helps with the implementation setup.

I'm nearer to the technical side, so I don't deal with the pricing. In general, it's not an expensive product. We can say it's an affordable product. I can't say it was expensive. It depends on what the usage is, however. If you are using Appian where it's not required, definitely you will feel like it's expensive, however, if you are using Appian on a fuller scale, then definitely you will not feel like it's an expensive product.

We would recommend this product to others. 

From a low code BPM platform, I would rate the solution around nine out of ten.

I've used it for analytics and automation. I use it for processes related to validation. It's for business process automation. It can be used for mail ticketing, validating products, invoicing, processing, order to cash, et cetera.

It helps with working with API projects. It helps me work with clients and helps with automation with UiPath. 

It's a popular solution with clients. 

The price is not that high. It's affordable.

The setup is easy.

It is stable.

The product is quite innovative. 

There is a lot of documentation available.

The solution could offer better features. We'd like to have more options for automation. We have more affordable UiPath automation features, which are lacking in Appian. It really needs to invest in automation more. 

It would be useful if they could create an academy or forum in the future to help active users answer questions they have about the solution.

I've been using it for one year.

The solution is very stable and reliable. It is innovative. The customers I have been working with choose Appian based on its innovation and reliability.

There are a variety of customers using the solution. We're a consultant group and have customers across many sectors. It's hard to quantify how many people are using it. 

Technical support is very helpful. I've also uncovered a lot of documentation that can help me. It would be ideal if they could create an Appian Academy or official forum to help people learn more about the solution and troubleshoot problems. 

I did not have any issues with e Appian installation. 

The deployment of projects depends on the data I work with or the projects I deploy. A simple project will happen fast. A more complex project will take longer. Typically it takes a day or two. A more complex deployment may take a week.

I use orchestrators during the deployment. I simply need to develop a process in the studio first and then I need to activate the robot and connect it with the orchestrator. 

I'm not sure about the licensing. It's not part of my direct scope. However, my understanding is the pricing is reasonable. 

I am using the latest version of the solution. 

We have an on-premises deployment for right now. However, I'm open to trying the cloud deployment in the future. 

I provide the solution for my customers. I am an AI engineer. I provide a solution and find use cases for the customers. 

If people are interested in the solution, they should start by reading more about it and learning more about the offering. 

I'd rate the solution eight out of ten. 

I am working in a software house, and we are using Appian to build a custom-made application while trying to fulfill our client's requirements.

I don't think we currently have any applications for our internal processes, which include a set of Oracle APEX products or applications, especially custom-made applications, which is something we need for ourselves. However, we have many use cases for our clients.

Workflow Engine is a valuable tool. Besides the resource kit, I believe both tools are very, very convenient for our clients.

I don't think I have anything to comment on the areas that need improvement in the solution, but I can refer back to my technical team. As the solution architect, I don't have hands-on experience with both products.

If you ask me about my thoughts on what is missing in Appian or my opinion on what I would want the vendor to add in the future, I would say that the product is in a state of perfection. However, we can't really guess what AI and big data models might sell us in the near future.

I am currently using Appian and Oracle APEX, and I will soon start to use Appian Version 23.1. Also, our company has a partnership with Appian.

I won't be complaining near the client. Stability-wise, everything is okay.

It is definitely a scalable tool. I would rate its scalability not less than eight and a half out of ten.

Even with an on-premise implementation, the scalability is still high, so it is easy to scale up.

I don't have any experience with it personally, but our team that practices on Appian uses the technical support very frequently, maybe on a daily basis or so.

We have been using APEX in our organization for some time now, and I was checking the comparison between Oracle APEX and Appian on peerspot.com for an unbiased opinion. Presently, we are implementing both Oracle APEX and Appian almost equally for small to medium purposes. However, for enterprise needs, I think we will choose Appian.

It depends on the functionality that we are using. For instance, having an LMS solution for our clients is a bit straightforward. Sometimes, clients expect us to implement ERP using Appian, which is very complicated. In such cases, I don't believe that Appian is a good tool for that.

When it comes to pricing, it's definitely not affordable. However, it really depends on the requirements that you're seeking from the solution. If you're looking for an on-premises distribution, it can be a bit expensive. But this is usually the case with on-premises solutions. That's why we have a cloud solution available, which is more cost-effective.

Additionally, the cost is justified by the use cases, and Appian is a good solution overall.

In terms of hidden or extra costs for additional features beyond the standard license, I don't think we've had any exposure to such scenarios, except for the resource kit. From a technical standpoint, I'm not sure if it's paid for separately or included in the license cost. As you may be aware, we've partnered with Appian, so I believe we have an official case here.

I suggest that those planning to use Appian take care of the practice lead because many resources claim to have solid and vertical knowledge of Appian. We are not sure why there is a risk of resources being unavailable during this trip. Additionally, we have a shortage of Appian resources, so finding a good practice lead could be a challenge. Overall, I rate this solution a nine out of ten.