The solution is used to automate internal operations. We had industrial and equity-based financial clients.

The product improved our operational efficiency. The deployment takes one or two weeks. The rollout takes two to three weeks.

The solution’s turnaround time for development is better compared to other tools. The solution enables fast development. The traceability of the processor is good. There is much more governance and regulations on the processers. The tool reduces the time of the processes by 30% to 40%. The solution’s low-code aspect has greatly impacted the development and deployment speed.

One of the major reasons we are using the product is that we can reuse the modules. The developers can reuse all the modules. It enables us to make subsequent developments in less time. The prebuilt modules can be deployed within two to three weeks. The tool is very flexible. Compared to other platforms, the Appian product team was agile in quickly customizing things for us.

It is difficult to set up the on-premise version.

I used the solution for more than three years.

The solution is very stable. I've never faced any downtime. The response time is also great.

It is easy to scale up the product for a large number of users. We can scale up to 100 users within 20 to 30 minutes. I rate the scalability a nine out of ten. Our customers are enterprise businesses.

The technical support is not excellent, but it is good.

Positive

The initial setup of the cloud version is quite easy. I rate the ease of setup of the cloud tool a nine out of ten. It is difficult to set up the on-premise version. I rate the ease of setup of the on-premise tool a five or six out of ten.

The tool is quite costly. It's not affordable to the general public and most companies. People would prefer a low-cost version that comes with reduced functionalities. The solution would be more accessible to the users if the vendor provided it at half the cost. I rate the pricing eight and a half out of ten. The price is quite high.

I haven't faced challenges with new implementations. If an organization has a long-term goal of automation and wants to explore automation, Appian is a good choice. The product is quick, agile, and very robust. It provides everything we need. It's not like the other platforms where we have to buy multiple things on top of the actual product. It is a holistic automation tool. Overall, I rate the solution a nine out of ten.

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.

Appian is a good workflow solution. So, I use it for workflow and low-code application development.

Workflows can basically be embedded in any domain. For example, we use Appian as a workflow solution primarily in chunks. We have a couple of use cases that we have built.

From a personal marketing perspective, it basically supports the end-to-end building of an awesome product, wherein you can use it primarily for data orchestration, and then for building process workflows, and then for building approval workflows. 

So, you can set it all together. You can bring in the data through Appian, and then I use this to integrate with different solutions, different products, and different platforms that exist in the company. It brings them all together. It can then be automated. We have a couple of new steps available to us.

For one of the clients, we've used this to build a complete end-to-end claim cycle, where we built a portal that integrates into various systems. 

We get emails that get processed. From there, a claim is received. It goes through the entire claim designation lifecycle. It goes through different people, different approvals, and then finally, there's some integration with the payment system. 

Once the claim is approved, the payment happens. And it is one seamless process. And then if any litigation is required, it can be directed to the finance team and so on. So, there is an end-to-end claim cycle that has been automated using Appian.

So, this is just an example of a workflow we've optimized using Appian.

From a feature perspective, Appian has quick development, given it's a low-code platform; you can quickly use it to build a solution.

And then, if we need to make changes, we don't need to do a lot of coding.

With low-code, we don't need a lot of coding, and then from the plumbing perspective, there is a complete CI/CD pipeline that exists within Appian that can be leveraged for open deployment. 

We can manage versions, do field deployment, and manage all these smaller incremental changes that need to be done. It's self-sufficient, from my perspective.

From a product perspective, it's good. There are some restrictions with respect to using external components within Appian. 

So, for example, if we do not have a particular feature available, there's a long cycle of getting approvals and all of that. That does not offer flexibility, which definitely can be improved on.

Another area of improvement is pricing. 

I have been using it for two years now. 

It is a stable product. I would rate the stability a ten out of ten. We have not faced any challenges with respect to the platform in the last two years. 

Since it is on the cloud, it is easy to scale. 

There are around 200 end users using this in our company. The usage depends on the end user. 

Appian is scalable, especially from an integration standpoint. It offers low-code integration capabilities, eliminating the need for external integrators. 

It comes with many components and connectors that facilitate system integrations.

The customer service and support are very responsive. We haven't faced many issues, but when we have, the support team has been very helpful.

The Appian community is strong and open. You can often find solutions or discussions relevant to your issues. Consulting with community members through platforms.

The initial setup is straightforward and easy to use.

Deployment is quick.

We did it in-house. It depends if you have the skills in-house, it can easily be done.

So, there are not many things that you have to do. The solutions can be built in Appian itself, there's a pipeline that exists. You just have to kind of tag the components that need to go into deployment and use them to deploy easily.

It is a little bit expensive when compared to other platforms, it is somewhat expensive.

The license is not very cheap. It's on the expensive side.

The licensing is on an annual basis.

Overall, I would rate the solution a seven out of ten. 

I would recommend it, especially if you're looking to quickly develop workflow solutions with low-code integrations. Among similar platforms, I'd place Appian in the top tier.