Experience enables seamless automation and elevates process efficiency while embracing innovative technologies
What is our primary use case?
A common use case for Appian is intelligent automation, where companies wanting to transform and have the latest technologies such as robotic process automation, fintech, AI, and artificial intelligence under the same platform use Appian to automate their business workflows.
There could be multiple industries that could benefit from this, including investment banks, retail companies, manufacturing companies, and healthcare companies. There's a variety of use cases for implementation.
What is most valuable?
The features of Appian that have proven to be the most beneficial are its capability to create processes and integrate with external systems while ensuring data consistency across all the systems.
The latest features of Appian are quite useful around the UI/UX design and the artificial intelligence integrations.
Appian is aiding in leveraging AI technologies in multiple ways: one way is for developers, as they make development efficient and quick by enabling developer co-pilots across various phases of the application, which helps design Appian quickly and provides suggestions along the way.
Another way is through AI Skills, which can be integrated anywhere in the process model to leverage artificial intelligence for tasks such as extracting data from documents, summarizing information from documents or long paragraphs, and building custom prompts with Appian.
Appian also utilizes AI for business users, providing a feature called process each view, enabling business users to create their own dashboards, reports, and gain insights from their data and processes using artificial intelligence. It's multi-fold and always growing.
What needs improvement?
Appian could improve in terms of how it approaches external use cases.
Appian is a great tool for internal use cases where the users are company employees, but it has room to improve for use cases where the users are public facing, where anonymous users could come to a site and run a business workflow or interact with some data.
For how long have I used the solution?
I have approximately nine to 10 years of experience working with Appian.
What was my experience with deployment of the solution?
I have faced challenges while integrating Appian with existing systems, as there might be challenges around the integration systems not being stable or having many exceptions.
However, if the integration systems are stable and their process of integrations and the APIs are well documented, there are no challenges to integrate with Appian; it's fairly simple.
What do I think about the stability of the solution?
The stability of Appian would rate as nine, as it's a stable environment.
What do I think about the scalability of the solution?
Appian is scalable. On a scale of one to 10, Appian rates as a nine for scalability.
How are customer service and support?
The technical support for Appian rates as 10 out of 10 because they have a great support team.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
I have experience with Appian, not SAP solution.
How was the initial setup?
The initial setup of Appian has two ways of setting up the environments: one is on-premise, and the second is cloud environments.
The cloud environment is very easy to set up, as the Appian Cloud support team does everything for you end to end, and you will have the environments available where you could have the platform in about 24 hours, which is very quick.
This is preferred by about 95% of clients, as they would have Appian on Cloud.
The remaining 5% opt for Appian on premise due to data privacy issues or compliance challenges, where they manage the infrastructure themselves, which requires a couple of weeks for an infrastructure administrator to set up Appian on their own service.
What about the implementation team?
I'm a reseller and a partner, and my relationship with Appian is that we implement Appian for our customers.
What was our ROI?
The majority of our clients see the return on investment in about one year after implementation.
They see return on investment in terms of cost savings, time savings, more efficient processes, and more efficient employees.
What's my experience with pricing, setup cost, and licensing?
The price of Appian, on a competitive landscape, is a little bit on the higher side for companies, rating maybe a 6.5.
What other advice do I have?
I would recommend Appian to especially large to medium, medium to large companies looking to automate their business processes, as it's a great tool. I would rate the whole solution as a strong 9.5.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Manages databases effectively with seamless foreign key creation and data manipulation
What is our primary use case?
I use
Appian for creating applications, including
BPM applications.
What is most valuable?
Appian allows us to manage the entire database. I can create tables, perform database-related activities, and create multiple tables. I can directly create foreign keys, connect tables, and manipulate data using expression rules. This feature replaces data workflow from on-premises.
What needs improvement?
Since I have just started using Appian for three to four months, I haven't explored every part of it, so there might be areas that need improvement that I am unaware of.
For how long have I used the solution?
I have been using Appian for the last three or four months.
What was my experience with deployment of the solution?
The deployment process is very easy. I create a package for the component I work on and deploy that package to another environment.
What do I think about the stability of the solution?
Appian is a stable product and works very well.
What do I think about the scalability of the solution?
Initially, without much coding, I can easily handle five thousand records. However, for more than five thousand records, I have to manage with some coding.
How are customer service and support?
Appian has a community where I can put my questions. I haven't had a chance to contact the support team directly.
How would you rate customer service and support?
How was the initial setup?
My experience with the initial setup is normal as I didn't get a chance to work on it. I started directly with creating features after the initial setup.
What other advice do I have?
I would rate Appian nine out of ten. I would definitely recommend it to others. Being an initial user, I haven't had a chance to explore it much. I rate the overall solution nine out of ten.
Creating user interfaces is highly productive when these interfaces are integrated with the original database
What is our primary use case?
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.
How has it helped my organization?
Appian is managed and upgraded regularly.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been using Appian for two to three years. We are the using V24 of the solution.
What do I think about the stability of the solution?
The solution's stability is better.
I rate the solution’s stability an eight out of ten.
What do I think about the scalability of the solution?
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.
Which solution did I use previously and why did I switch?
I have used SoftEther VPN.
How was the initial setup?
I rate the initial setup a seven out of ten, where one is difficult, and ten is easy.
What about the implementation team?
The platform was set up by third party.
What's my experience with pricing, setup cost, and licensing?
The solution is expensive.
I rate the product’s pricing an eight out of ten, where one is cheap and ten is expensive.
Which other solutions did I evaluate?
We evaluated Outsystems. Appian is much proactive to create solutions applications.
What other advice do I have?
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.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)