IT Central Station is now PeerSpot: Here's why

Appian OverviewUNIXBusinessApplication

Appian is #4 ranked solution in BPM Software, top Process Automation tools, top Rapid Application Development Software, and top Low-Code Development Platforms. PeerSpot users give Appian an average rating of 8.4 out of 10. Appian is most commonly compared to Camunda Platform: Appian vs Camunda Platform. Appian is popular among the large enterprise segment, accounting for 72% of users researching this solution on PeerSpot. The top industry researching this solution are professionals from a computer software company, accounting for 25% of all views.
Appian Buyer's Guide

Download the Appian Buyer's Guide including reviews and more. Updated: August 2022

What is Appian?
With Appian, your organization can rapidly build, deploy, use, and scale problem-solving apps. And with the flexibility of on-premises and cloud portability, you'll always address your unique challenges the way that makes the most sense for you.

Appian was previously known as Appian BPM, Appian AnyWhere, Appian Enterprise BPMS.

Appian Customers
Hansard Global plc, Punch Taverns, Pirelli, Crawford & Company, EDP Renewables, Queensland Government Department of State Development, Infrastructure and Planning (, Bank of Tennessee
Appian Video

Archived Appian Reviews (more than two years old)

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
Appian Architect at a computer software company with 5,001-10,000 employees
Real User
Offers flexible local integration that we have used extensively to integrate with our Legacy system
Pros and Cons
  • "Appian also has very flexible local integration."
  • "They should provide more flexibility so designers can create a more picture perfect device."

What is our primary use case?

We use Appian for client on-boarding, anything onboard related, really: loading institutional clients, tracking that information in a single reporter, doing the follow-up, creating the plan parables for them, and developing for them.

In my organization, there are about 150 users who are currently using Appian on a daily basis. We use Appian very extensively. Every day, there are more than 100 unique logins to the system.

What is most valuable?

Appian also has very flexible local integration and we have used that extensively to integrate with our Legacy system.

What needs improvement?

The user interface is good, but it's not perfect. They should provide more flexibility so designers can create a more picture-perfect device. There should be more features on mobile UX development as well. 

Currently, it's easy to use and It gets the job done, but it's not flexible in regards to creating the mobile application from scratch. You have to play within the framework and the rules of the UX; however, that's something that not many customers like. Customers want a flexible mobile application development platform. I think Appian should make a lot of improvements with respect to their mobile application development by providing more flexibility for designers in order to allow them to create their own UX components and control the display of the data onscreen. 

I would like to see more flexibility in terms of the UI. I know that it's not designed to be a big application that allows you to do multiple things, like creating the second year stream of the pie, for example. I feel like Appian has been so instrumental in making their entire product local, and have really improved the user interface design, but the user interface design is limited to authenticated users only — although there are some limited pieces available on the login page. I would like Appian to extend their local capabilities to the login page as well so that we could create an available application that can be targeted to any customer. For example, if you flipped it, you would see information about various products and other information, something that could be very realistic if only Appian would allow these capabilities to be extended to the login page.

For how long have I used the solution?

I have been using Appian for more than 10 years.

Buyer's Guide
Appian
August 2022
Learn what your peers think about Appian. Get advice and tips from experienced pros sharing their opinions. Updated: August 2022.
622,949 professionals have used our research since 2012.

What do I think about the stability of the solution?

The stability is good. We have been using Appian for our strategy and tactical solutions and it has held up very well for us. The team was able to adapt to the changes of the new version  very quickly and were able to implement the application without any complexities or jumping hurdles relating to development. There were no issues for us. Appian has been meeting just as many of the requirements in my department as the stakeholders have. The stakeholders are happy with the UI and ease of the application. The overall usability has improved and everyone is happy with Appian. 

What do I think about the scalability of the solution?

We believe that the scalability of Appian depends on the expertise of the Appian designers. It completely depends on the skill of the designers — how they design the applications determines the scalability of processes and data. In other words, the platform is very scalable. It stores the data as memory so the data allows us to retrieve the information rapidly; but again, we had already done the data management so the team was focused on data retention and data management. They set up their architecture in such a way that the system and the application can be scaled very quickly, so we are not seeing any problems with the scaling of Appian. 

How are customer service and support?

My team mainly interacts with Appian cloud support who regularly provides them with solutions and advises them about any existing platform issues.

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

We previously looked at the Pega system; actually, one of our departments is currently using Pega system, but we wanted to diversify our technology base to provide a better experience for our stakeholders. My CIO recommended we make an investment because these two platforms are leading BPM tools offering similar functionalities, including BPM, EI, and case management. So we were calculating the pricing, trying to figure out what the return on the investment would be if we went with one platform or the other and what it would cost us in terms of losses between Pega and Appian.

How was the initial setup?

The initial setup was straightforward. The team was able to set it up quickly, build up the applications and deploy it within six to ten weeks.

What about the implementation team?

We have an in-house team that is comprised of Appian architects, designers, consultants and professionals who are trained on the Appian platform.

What other advice do I have?

I would definitely recommend Appian. It has come a long way and it's a good product. It's entering into the area of a local application development platform. Appian is continuously making product updates every quarter. 

I would give Appian a rating of nine out of ten.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Deputy Director at a tech services company with 51-200 employees
Real User
Flexible, easy to set up, and simple to integrate with other applications
Pros and Cons
  • "We appreciate the drag and drop functionality and the easy to access plug and play features."
  • "The solution could use some more tutorials to help brand new users figure out how to use the product effectively."

What is our primary use case?

Our plan on using the solution will be to basically utilize it for business process management, and for case management as well. We want to use their local platform offering and some of their niche markets, to see how they can provide dynamic case management all in one place. 

What is most valuable?

One of the features that we felt was valuable to us was the business case management and how seemingly easy it was to use.

The combination of business process management, dynamic case management over the local platform has vastly improved.

We appreciate the drag and drop functionality and the easy to access plug and play features. 

They seem to be introducing a lot of automation into their product, which is exciting for us. They're apparently partnering up with different companies to offer robotic process automation in the future.

The initial setup is very easy.

You can easily integrate other applications into the product.

What needs improvement?

We're still researching the platform. I don't have a strong opinion on what might be missing. They seem to be constantly upgrading their products.

The solution could use some more tutorials to help brand new users figure out how to use the product effectively.

For how long have I used the solution?

We're not really using the solution so much as testing its capabilities and discovering its resources. We've been doing this now for about two months.

What do I think about the stability of the solution?

The solution has been pretty stable. I haven't had any downtime whatsoever, or any disruptions or anything of that nature. There hasn't been any lag in service. It's been good.

What do I think about the scalability of the solution?

The solution is very agile. It's very easily expandable too. You're able to integrate different applications or different interfaces with this platform. It's actually quite flexible, I should say.

That said, at this point, we don't plan to increase usage. We're still learning about the product. We hope, in the future, if we take it on, we will be able to expand it.

How are customer service and technical support?

Due to the fact that we haven't had any issues yet, and we've been using the solution for a short amount of time, we haven't needed to contact technical support. If I need to in the future, I will. However, at this point, I can't speak to their level of service as I've never used them.

How was the initial setup?

We did not find the initial setup complex. Our engineers, who handled the implementation, found it to be quite straightforward.

The deployment process was fast. I can't recall the exact number of hours it took, however, it was not a drawn-out process.

Maintenence seems to be minimal, however it would be helpful if there was someone on staff to maintain it as needed.

What about the implementation team?

Our engineers handled the implementation. We were able to do everything in-house. We didn't need assistance from consultants or resellers.

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

The solution offers a monthly subscription model. That's what we use. I recall it being about $90 a month. They do have different tiers. 

Which other solutions did I evaluate?

We're currently doing a case study on this specific solution. We didn't look at other solutions.

What other advice do I have?

We don't have a business relationship with Appian. We're just customers.

We're most likely using the latest version of the solution.

I would definitely recommend the solution and invite other companies to try it out. They even have the trial edition. That way, you can test the solution before having to purchase the application edition. If you decide to go forward, it is $90 per user per month. They have the enterprise edition as well which is a bit more. 

The solution is that it's available on different devices as well, which makes it very flexible and easily adaptable to a lot of different environments, including Windows, Linux, Mac, and Android.

The product also caters to all sizes of companies, whether you are small or large.

I'd rate the solution nine out of ten.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Appian
August 2022
Learn what your peers think about Appian. Get advice and tips from experienced pros sharing their opinions. Updated: August 2022.
622,949 professionals have used our research since 2012.
Net Appian Developer with 11-50 employees
Real User
Faster development time with more robustness when compared to traditional coding

What is our primary use case?

We use this solution for the integration of systems and data in our organization.

How has it helped my organization?

Development time is much faster than traditional coding solutions, and it is more robust.

What is most valuable?

The Cloud offering is a nice feature.

The process models provide self-documenting systems.

What needs improvement?

They are continuously improving the platform. Three months ago I would have suggested they make smart service creation easier (using their API to create components), but they have done that.

My only request is that they decrease the license costs.

For how long have I used the solution?

We have been using this solution for one year.

What other advice do I have?

This is a great product.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
NanfaKumswa - PeerSpot reviewer
CTO/Owner at AVAILSYS LTD
Real User
Helps speed our time to solution with less demand for resources
Pros and Cons
  • "Since implementing we have had a faster time to solution, with fewer resources needed."
  • "We would like to have more granular control for interface styling."

What is our primary use case?

Our primary use for this solution is Business Process Automation.  Appian is good for enterprise process automation as well as general purpose low code development.

How has it helped my organization?

Since implementing, we have had a faster time to solution, with fewer resources needed per project compared to other tools.

What is most valuable?

The most valuable features of Appian are the Low Code, robust Process Design, Run-time Management, Deployment, Interfaces, and Mobility.  The business rules capability are advanced and the integration capabilities are second to none.  We also find security to be more robust than pretty much all other application platforms we've worked with in the past.

What needs improvement?

We've used a good number of Business Process Automation tools in the past and none of them have given the value for money we are seeing with Appian.  Appian enables us spend the least time designing beautiful and robust interfaces that automatically render in Web browsers and native mobile apps securely without any additional effort.  With very little learning curve, an Appian designer will start designing very complex and dynamic interfaces that consume data from everywhere.

We would however like to have more granular control for interface styling in future releases.  Appian releases updates to the platform every quarter.

For how long have I used the solution?

We have been using this solution for one year.
Disclosure: My company has a business relationship with this vendor other than being a customer: We are a solution partner to Appian.
PeerSpot user
Uriel Zamora - PeerSpot reviewer
Technical Service Advisor at PPG Industries
Real User
Quickly develop applications for end-to-end process automation
Pros and Cons
  • "Process culture is making noise inside the organization because now, everybody knows that their time is being monitored."
  • "The documentation needs to be improved."

What is our primary use case?

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.

How has it helped my organization?

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. 

What is most valuable?

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

What needs improvement?

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.

For how long have I used the solution?

One year.

What do I think about the scalability of the solution?

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

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

I used IBM BPM 8.5.7 prior to adopting this solution.

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

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

Which other solutions did I evaluate?

We evaluated both Pega and Activiti before choosing this solution.

What other advice do I have?

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.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
PeerSpot user
BPM Consultant at a healthcare company with 10,001+ employees
Real User
Supports back-end workflows but not recommended for the front-end
Pros and Cons
  • "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."
  • "There is a version coming out every six months with performance improvements."

    What is our primary use case?

    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.

    How has it helped my organization?

    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.

    What is most valuable?

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

    What needs improvement?

    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.

    For how long have I used the solution?

    One to three years.

    What do I think about the stability of the solution?

    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.

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

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

    What about the implementation team?

    The setup is straightforward. No complaints, no issues.

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

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

    Which other solutions did I evaluate?

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

    What other advice do I have?

    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.

    Disclosure: My company has a business relationship with this vendor other than being a customer: Partner.
    PeerSpot user
    it_user865488 - PeerSpot reviewer
    Project Manager and Technical Leader at Exus
    Real User
    Low-code characteristics lead to fast development cycles
    Pros and Cons
    • "Call Web Service Smart Service - Web service integrations with other systems are super simple and fast to create, supported by low code menus."
    • "Write to Data Store Entity - Saving data in SQL databases is done easily using entities. Entities (CDTs in Appian terminology) define relationships and target schema tables via XSD files."
    • "Even though the company has made great improvements in online documentation, featuring rich material which includes case studies of real-life use cases, the material could definitely be better in quality and coverage of use cases."
    • "A point of improvement would be the SAIL forms. The built-in tool used to generate forms does not have debugging support (to view local variables as they change on live preview, and step-by-step valuation) which is a big drawback for form development. Moreover, the script language used to build SAIL forms does not support inheritance or lambda expressions (functions as arguments of other functions), which makes the code base more verbose."

    What is most valuable?

    • Process Designer - If properly used, the executable flow itself helps you understand the business flow.
    • Call Web Service Smart Service - Web service integrations with other systems are super simple and fast to create, supported by low code menus.
    • Write to Data Store Entity - Saving data in SQL databases is done easily using entities. Entities (CDTs in Appian terminology) define relationships and target schema tables via XSD files.
    • SAIL interfaces - Writing code that creates forms requires coding skills in Appian SAIL, a proprietary language. The forms are mobile-ready and components can be reused in forms and reports.

    What needs improvement?

    Even though the company has made great improvements in online documentation, featuring rich material which includes case studies of real-life use cases, the material could definitely be better in quality and coverage of use cases.

    Another point of improvement would be the SAIL forms. The built-in tool used to generate forms does not have debugging support (to view local variables as they change on live preview, and step-by-step valuation) which is a big drawback for form development. Moreover, the script language used to build SAIL forms does not support inheritance or lambda expressions (functions as arguments of other functions), which makes the code base more verbose.

    Last but not least, I am missing a team collaboration solution. Only one person at a time can work on objects. This is not a big issue really, because, if you follow the Appian best practices, all objects are pieces that fit single-person workloads.

    For how long have I used the solution?

    One to three years.

    What do I think about the stability of the solution?

    The platform is super stable in BPMS and rules execution. 

    Issues can appear in the following ways, related to development and design choices:

    1. The underlying database is facing locking or performance issues. The instability of the database is very quickly propagated in the flows and forms executions (Appian engines/application server) and the platform can become non-responsive, experience deteriorating performance, or create numerous exceptions in running processes.
    2. If the platform is used for data-intensive tasks, especially in deep nesting of data manipulation rules, the performance can quickly be affected and may also lead to exceptions.
    3. If you don't follow the Appian best practices, and your application is scaling up, then on pick times the performance will be bad or exceptions may occur. This situation can be avoided by identifying potential issues by running the health check diagnostic tool.

    What do I think about the scalability of the solution?

    Scalability is very good, but there are limits imposed by the underlying hardware and the JVM's heap size. Notably, even with a configuration having multiple application servers, the Appian engines installation is always one. However, the capacity of the topologies is very high and will not be an issue for companies with up to 10 applications per installation and up to 4000 active users per day. Appian provides a sizing document and Professional Services to help with decisions on the subject.

    How are customer service and technical support?

    Technical support is considered good, and various levels of support can be selected.

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

    Prior to Appian, there was a Java-based BPMS solution, but Appian was valued for its low-code characteristics that lead to the fastest development cycles in the industry. It was also valued for the scalability, the flexibility on development, the level of support, and the increasing developer base.

    How was the initial setup?

    Appian has two offerings for its customers, on-premise and Appian Cloud (PaaS). In the case of PaaS, setup is very minimal and straightforward. For the on-premise product, the initial setup is pretty straightforward in most cases but requires a level of systems expertise, especially if you are setting up a high-performance production machine.

    After some initial use, tuning the database is advisable. For mission-critical applications, an initial round of stress testing may be a good idea for identifying potential bottlenecks in your applications. Setup can also be tricky if you try to migrate from very old installations which used a different topology. If this is your situation, you may need support from Appian Professional Services.

    Which other solutions did I evaluate?

    The alternative we evaluated was Pega BPM.

    What other advice do I have?

    If licensing cost is not a problem, then Appian is definitely a go, either as a stand-alone platform or with the PaaS offering in the Appian Cloud. When it comes to speed of development, system integrations, BMPS workflows, and digitization of manual processes, Appian is possibly the best choice there is.

    Disclosure: My company has a business relationship with this vendor other than being a customer: Gold partner.
    PeerSpot user
    it_user633939 - PeerSpot reviewer
     IT senior consultant
    Consultant
    Defines activity ownership, streamlining productivity; we can also see process bottlenecks
    Pros and Cons
    • "The Application Designer is very user friendly. There are also lot of plug-ins that you can use and, for the most part, they are free."
    • "The reporting is not as good as in similar products. They could also improve the dashboards."

    What is our primary use case?

    We use for this solution for organizing and distribution for supermarkets, for coordinating the disposition of expired goods in the supermarket.

    It is also used internally, to structure the budget; also for task scheduling and tracking.

    How has it helped my organization?

    It has improved the organization by defining activity ownership. When we give ownership to the right user, processes go very fast. Before it wasn't very good. It was slow. Now, with this application, you can see the bottlenecks, where the business processes is slow. There is a lot of information from it. 

    What is most valuable?

    • I think the interface is a good feature because it's simple to use and you can quickly develop the users' interface. 
    • The Application Designer is also very user friendly. 
    • There are a lot of plug-ins that you can use and, for the most part, they are free.

    What needs improvement?

    Something they need to improve is, it is difficult to catch errors. When there's an administration error you can't catch the error, and it is there until the administrator addresses it. This is a problem because if you are the developer, you try to catch the error but you can't. The process will stop. There is a workaround but it would be pretty cool of you could catch the error before. 

    Another limit is the reporting. The reporting is not as good as in similar products. They need to improve on that side.

    They could also improve the dashboards.

    For how long have I used the solution?

    One to three years.

    What do I think about the stability of the solution?

    No issues with stability.

    What do I think about the scalability of the solution?

    We haven't encountered any issues because we use small processes. We have not had any problem with the amount of work or data it can handle.

    How are customer service and technical support?

    Their technical support is good. There is a community which will, for the most part, answer problems. But if you have a big problem and you need support from Appian, they are a little slow, but they are good; they provide good answers.

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

    We didn't have previous solution.

    How was the initial setup?

    No it was not complicated. It was simple.

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

    It's good value for the price.

    Which other solutions did I evaluate?

    I only saw demos of Pegasystems and IBM. We selected between Pega, IBM, and Appian. Appian was cheaper than the others when we saw these three solutions. As of now, I don't know about the pricing.

    What other advice do I have?

    Be sure to use the product in the correct way and don't ask the product to make up for experience in BPM.

    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    PeerSpot user
    it_user577641 - PeerSpot reviewer
    Regional Sales Director at a tech services company with 51-200 employees
    Real User
    Helps ensure accountability throughout the organization, knowing a task is assigned and completed
    Pros and Cons
    • "What stands out are the speed of the product, the quick, easy development, and visual diagramming."

      What is our primary use case?

      We use Appian for HR onboarding and a couple other places in the company.

      In particular we use it for workflows in HR onboarding. Any time that we're hiring new people, we have an application that assigns different tasks for computers, for making sure they're set up on insurance, their emails; all of that stuff is assigned to them prior to starting to work.

      How has it helped my organization?

      Accountability is probably the most affected. Knowing that a task has been assigned, that you're following a specific process, and that the task has been completed, gives you that accountability throughout the organization. It enables us to know that, when we bring new people on, they're ready to start right away.

      What is most valuable?

      It's being able to manage the workflow, to assign tasks, to have notification that a task has been completed. It's basically what any BPM solution is going to provide.

      What stands out are the 

      • speed of the product
      • quick, easy development 
      • visual diagramming. 

      Those are the features that really stand out.

      What needs improvement?

      I don't know that I would have any specific areas for improvement.

      For how long have I used the solution?

      One to three years.

      What do I think about the stability of the solution?

      It's very stable. We have not experienced any problems with it.

      What do I think about the scalability of the solution?

      Considering that organizations like the US Army use it, worldwide, globally, it's able to scale up from supporting an organization of 50 to an organization of thousands. There is no issue with scalability.

      How are customer service and technical support?

      I have not had any reason to call tech support, but my peers that I've talked with, who have interfaced with tech support, say it's fast, it's responsive. They get the issues resolved immediately.

      Again, we haven't had any problems with tech support whatsoever.

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

      We had used a homegrown solution. We do custom development, software development work, or that was our legacy. Maintaining that homegrown solution over time just proved to be ineffective. Appian provided a much better solution at a lower overall cost.

      How was the initial setup?

      It's very straightforward. If you've got somebody who comes from a workflow background they're going to understand it, and find it very simple. It's very intuitive. We didn't have any issues in setting it up or getting started with it.

      What was our ROI?

      I think that most companies do not do a good job of really looking at the return on investment. They typically do not have a good feel for what their costs are, going in, of manual processes or of a homegrown solution they've developed.

      Being able to calculate an ROI, I've seen that to be very difficult for most clients that I've dealt with. I think that's an element that's missing a lot in technology today. Make sure you evaluate your total cost before you're ready to make a decision.

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

      I think that if somebody is really serious at looking at business value, then by all means, the product is well worth the value. You get representative business value for the price that you pay for the product, and for the implementation of the product.

      Which other solutions did I evaluate?

      We evaluated several different options. Pegasystems is one. I'm not sure about K2, but there were multiple options available. If you look at the industry reports there are numerous solutions listed. We felt that Appian, for the value and for the ease of use, and for the mobile capability, was the best solution.

      What other advice do I have?

      I would give it a nine out 10. I don't think any product is ever perfect, but I think that Appian is one of them that comes closest to that mark. When you consider the capability, what it can do, consider the price, consider the different advantages that it has, I think it's a superior product. It's one that we use. We're very pleased with it. Most customers that I've talked to have been very, very pleased with their selection.

      I understand that you can go with an off-the-shelf product that's going to get you 70%, maybe 75% of the capability you want. You're going to have to tweak it and do some elements of custom work that are most likely going to drive the cost up. You need to consider that, versus a product like Appian that allows you to really tailor the solution to fit your particular environment. I think that's the best advice I would give somebody, is to make sure that you're looking at it honestly before you go down that road.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      PeerSpot user
      it_user629871 - PeerSpot reviewer
      IT Advisor to Banks at a financial services firm with 10,001+ employees
      Real User
      We are creating workflows in an agile manner
      Pros and Cons
      • "The tech support is quite good."
      • "The agile manner that we require to create our workflows. This is probably the most critical part of our solution and the time it takes to start processing the solution."
      • "It needs better integration with our existing application ecosystem."
      • "We would like to see more reduced latency. We would like to make sure that the scale-out factor will be much more as workloads come in."

      What is our primary use case?

      It is mostly for our API, BPM, workflows, web services, and enterprise integration.

      How has it helped my organization?

      We have been focusing on building all of our digital and mobile applications with a lot of earlier code, as the platforms were legacy. We had to write code from scratch, because it was not possible to use the existing code. For most of our digital applications, like payment systems or digital payments, the use case was for our mobile apps.

      What is most valuable?

      The agile manner that we require to create our workflows. This is probably the most critical part of our solution and the time it takes to start processing the solution. This is also quite fast. It is important for us to develop the solution in an agile manner.

      What needs improvement?

      Newer features, especially in terms scalability. It has to become more scalable than what it is today. It is not a issue today. However, going forward, due to the growth in the number of users and the workloads, it will have to be more scalable.

      It needs better integration with our existing application ecosystem.

      I would like more connectors for calls and integration features. Typically in enterprise banks, we have 200 to 300 plus applications. Training and documentation on how to integrate this would help.

      For how long have I used the solution?

      One to three years.

      What do I think about the stability of the solution?

      We would like to see more reduced latency. We would like to make sure that the scale-out factor will be much more as workloads come in. The scale-out should be improved as we grapple with more workloads and users.

      We feel the latency could further be reduced, but the access time for the throughput time or the general access time could be further reduced. 

      What do I think about the scalability of the solution?

      We do not see any issues with overall scalability right now.

      How are customer service and technical support?

      The tech support is quite good. Maybe it is not as good as large enterprise vendors, especially when it comes to more technical troubleshooting. Overall, the response is okay, since most problems are solved. Though, if there are major issues, then break times possibly increase. If they could focus on that, it would be helpful.

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

      We have been using tools from IBM, Oracle, CA (formerly known as Computer Associates), so mostly these enterprise tools at the same time are very complex and not very agile. The learning curve is much more than we found with the learning curve for Appian, so it is a trade-off between the agility of using a tool versus the complexity. To a large extent, more functions can be serviced through the tools previously mentioned from a enterprise perspective. However, most of the functions that we have are requirements for our services that we run through Appian, therefore we see this coverage as okay

      How was the initial setup?

      It was between straightforward and complex. There were a few issues in terms of configurations, but overall, getting the system started was quite fast. There were a few configuration parameters that we had to change, for which, it took us a couple of days more than expected. The way to start this tool is quite quick, so we did not face any issues with it.

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

      Product pricing compared to some of the earlier vendors, like IBM, CA, and Oracle, is quite well-priced. Although, we do feel that as we increase the number of users and the workload increases, we will have to spend more. 

      We will have to have a dialogue or negotiate a price for future use. To start with, it is a reasonable price. As we go ahead, we will have to make sure the costs are inline with our expectations as we grow our user base and workloads.

      In terms of licensing, instead of user-based, you should go more on a workload basis. It could be helpful, since we feel that we will be growing the workload part of it more than the user part of it. I think they give us a good price on workload characteristics and it would be a better option.

      Which other solutions did I evaluate?

      We already had IBM. We evaluated Oracle and CA. We found this product to be good price-wise as well as quick implementation-wise. From IBM, at that time, we evaluated WebSphere, APM Manager, and Workflow Manager. So, it was centered around their WebSphere, Lombardi product. 

      What other advice do I have?

      How to integrate with their application ecosystem is probably a priority. Once you get a product like this, it is important to have that integration upfront rather than later on to work on. Otherwise, you will grapple with a very complex application ecosystem for large enterprises. These features must be provided for, understood, and the expectations of the enterprise integration bus, service, or whatever you do should be well covered by the solution, so you do not face problems down the road.

      Most important criteria when selecting a vendor: We make sure it is a recognized and credible name/vendor. We typically look at the top four or five vendors on independent research ratings, then we form a committee so we do not take personal decisions. We have a committee, we arrive at a consensus, then we put up our selection criteria. This revolves around the technical aspects, the credibility of the vendor, the coverage of the vendor, and the cost as well as where do we see the future roadmap of the vendor.

      Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
      PeerSpot user
      Team leader at a tech services company with 501-1,000 employees
      Real User
      It ​reduces development time in half making us more efficient
      Pros and Cons
      • "It ​reduces development time in half making us more efficient."
      • "There is no need to worry about vulnerabilities in the system, because Appian built a secure system​."
      • "It would be nice if you could create your own customized apps when the business needed them.​"
      • "​Appian is easy to set up, but JBoss is complex. JBoss is the application server for running Appian."

      How has it helped my organization?

      It reduces development time in half making us more efficient.

      What is most valuable?

      • It is fast and efficient.
      • Mobile

      All enterprises focus on these features in their work.

      What needs improvement?

      • Apps development
      • BPM

      It would be nice if you could create your own customized apps when the business needed them.

      For how long have I used the solution?

      Three to five years.

      What do I think about the stability of the solution?

      No issues.

      What do I think about the scalability of the solution?

      No issues.

      How are customer service and technical support?

      I would rate technical support as an eight out of 10.

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

      I previously used .NET Framework. I switched because I think Appian is better for enterprise.

      How was the initial setup?

      Appian is easy to set up, but JBoss is complex. JBoss is the application server for running Appian.

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

      There are two solutions depending on your situation: an on-premise solution and a cloud solution.

      Which other solutions did I evaluate?

      Oracle BPM. Appian was better.

      What other advice do I have?

      It is more efficient and reduces time. There is no need to worry about vulnerabilities in the system, because Appian built a secure system.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      PeerSpot user
      Real User
      SAIL enables creation of complex, responsive UIs, including UI logic and appearance
      Pros and Cons
      • "SAIL (Self-Assembling Interface Layer), a scripting language provided by Appian. It is the equivalent of JS and CSS. It allows creation of complex UIs which are also responsive. With SAIL, we have a single language for both the UI logic and its appearance. UI components can be built as reusable components and used in multiple UI interfaces."
      • "Process Modeling enables creation of business process workflows. You can create complex business workflows in a visual manner, and it is also easy to debug/monitor."
      • "Offline capabilities and responsive capabilities could be better. The mobility features of Appian platform are still evolving."
      • "Native mobile capabilities or hybrid mobile app capabilities are very limited. Things like offline sync, offline storage, access to smartphone device features, etc. are not supported by the Appian platform yet."

      What is most valuable?

      SAIL (Self-Assembling Interface Layer), a scripting language provided by Appian. It is the equivalent of JS and CSS. It allows creation of complex UIs which are also responsive. With SAIL, we have a single language for both the UI logic and its appearance. UI components can be built as reusable components and used in multiple UI interfaces.

      Process Modeling enables creation of business process workflows. You can create complex business workflows in a visual manner, and it is also easy to debug/monitor.

      What needs improvement?

      Offline capabilities and responsive capabilities could be better. The mobility features of Appian platform are still evolving.

      Native mobile capabilities or hybrid mobile app capabilities are very limited. Things like offline sync, offline storage, access to smartphone device features, etc. are not supported by the Appian platform yet.

      For how long have I used the solution?

      Three to five years.

      How is customer service and technical support?

      Excellent.

      How was the initial setup?

      It is Java based, can be deployed in JBoss or WebSphere container.

      What other advice do I have?

      I would rate it eight out of 10. It certainly is the best for enterprise application development.

      Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
      PeerSpot user
      it_user747780 - PeerSpot reviewer
      Vice President - Appian Lead Designer at a financial services firm with 10,001+ employees
      Vendor
      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
      Pros and Cons
      • "Appian is a very low code platform. It's very easy to learn and use."
      • "It has it's own built-in UI components and doesn't provide much flexibility to customize or extend those components."

      What is most valuable?

      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.

      How has it helped my organization?

      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.

      What needs improvement?

      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.

      For how long have I used the solution?

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

      What do I think about the stability of the solution?

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

      What do I think about the scalability of the solution?

      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.

      How are customer service and technical support?

      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.

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

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

      How was the initial setup?

      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.

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

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

      Which other solutions did I evaluate?

      Oracle BPM, Pega, and D+H.

      What other advice do I have?

      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.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      PeerSpot user
      Gregg Lipson - PeerSpot reviewer
      Senior Business Analyst at a university with 1,001-5,000 employees
      Real User
      It has greatly improved efficiency and effectiveness as well as making continuous improvement possible
      Pros and Cons
      • "It has created executable requirements and speeds up the SDLC process greatly."
      • "Form creation and SAIL proprietary language still basically require programming. The claim a BA type can do everything is hogwash."

      What is most valuable?

      Being able to model requirements in BPMN 2.0, get agreement from business and IT, and then have Appian BPMN 2.0 compliant engine execute the diagram. This has created executable requirements and speeds up the SDLC process greatly.

      How has it helped my organization?

      • Transparency of process flows, including number of instances of the process in-flight
      • Identification of bottlenecks,
      • Average time to completion of tasks and process, etc.

      The employee onboarding process went from a mass email saying who is arriving for their first day, and just hoping all the things necessary got set up: phone, computer, badge, desk, login accounts, role specific access and accounts, etc. The Appian platform took from a blind mass email to full transparency with reporting, and greatly improved efficiency and effectiveness, as well as making continuous improvement possible.

      What needs improvement?

      Form creation and SAIL proprietary language still basically require programming. The claim a BA type can do everything is hogwash. They should be honest and say a developer is needed for web service integrations, etc. and complex forms; and a BA type can do the rest - requirements, architecture (collaborating with architects), design, process model, testing, deployment, and support. That is incredible powerful, but to say a developer is never needed is a lie.

      For how long have I used the solution?

      Two years.

      What do I think about the stability of the solution?

      Very few.

      What do I think about the scalability of the solution?

      No.

      How are customer service and technical support?

      Poor. Very helpful at times and willing to go above and beyond, but very expensive, so overall poor.

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

      Yes. IBM, Oracle, and Activiti open source. A different organization I was with selected Appian.

      How was the initial setup?

      Complex: Data strategy and authorization to push data to the cloud was a big hurdle. How organizational data is going to be pushed to Appian, updated by Appian, and pushed back to the organization with or without approval steps needs to be planned and executed strategically.

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

      It is expensive, but powerful. I would recommend comparing against cheaper licensing products and open source.

      Which other solutions did I evaluate?

      No.

      What other advice do I have?

      Have 20% of a programmer as a resource, plan the round trip data integration, and get all approvals needed.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      PeerSpot user
      it_user735246 - PeerSpot reviewer
      Senior Software Engineer at a financial services firm with 10,001+ employees
      Real User
      Enables quick development of code resulting in quicker turnaround time for automation
      Pros and Cons
      • "Low code development: Code can be developed pretty quickly which leads to less turnaround time for automation of business processes."
      • "Architecture of product and scalabiility issues."

      What is most valuable?

      • Low code development: Code can be developed pretty quickly which leads to less turnaround time for automation of business processes.
      • Ease of use: Any normal developer can pick up the development techniques pretty quickly.
      • Regular updates: There are regular updates, as per market and as per client's requirements.
      • Professional support: If you are stuck somewhere during the entire project lifecycle, the support team is ready anytime, so that timelines are met properly.

      How has it helped my organization?

      This product has helped in automating a lot of flows in a lot less time, which has actually reduced manual errors and enhanced quality assurance.

      What needs improvement?

      Architecture of product and scalabiility issues.

      For how long have I used the solution?

      For three years, from version 7.8 to 17.2.

      What do I think about the stability of the solution?

      Not much, but sometimes very minor issues on tier 0, 1 applications.

      What do I think about the scalability of the solution?

      Not much, but again if high usage is not anticipated while gathering the requirements, the tool becomes slow sometimes, which is not good for tier 0 applications.

      How are customer service and technical support?

      10 out of 10.

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

      No, I didn't use any.

      How was the initial setup?

      It's straightforward, like any other normal tool installation or deployment.

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

      I have no idea about this, as my senior management has been dealing with this.

      Which other solutions did I evaluate?

      Not before; but after I evaluated Pega.

      What other advice do I have?

      It's good to implement this product for automation.

      Disclosure: I am a real user, and this review is based on my own experience and opinions.
      PeerSpot user
      Randy Dillon - PeerSpot reviewer
      Digital Transformation Architect/Consultant at a tech services company with 1-10 employees
      Consultant
      BPM done right is a huge value proposition for almost any company, and with Appian's low code rapid development model, the ROI can be huge.
      Pros and Cons
      • "Rapid development with low-code makes it easier to quickly get apps implemented and the time to break-even and ROI is much faster."
      • "The biggest areas of improvement would be in facilitating team development, DevOps, and integration with typical tools used in enterprise development (Jenkins, Subversion, etc.)"

      What is most valuable?

      The most valuable features of Appian are:

      1. Rapid development with low-code makes it easier to quickly get apps implemented and the time to break-even and ROI is much faster.
      2. Easy to build case management, with Records and Related Actions facilitates case or document-based applications instead of, or along with, process-based applications, opening up whole new types of applications for Appian development.
      3. Built from the ground up with a cohesive architecture to be the leading social, collaborative, most usable BPM platform. This makes the product feel integrated and intuitive to use, rather than having to seemingly (or actually, in the case of some competitors) go to a separate product to do certain things. In the end, it shortens implementation time and opens up the product to less technical designers because it's easy to use.

      How has it helped my organization?

      Most notably, it allows us to quickly automate processes and case management work, often cutting the manual time required in half or more. End to end time is also noticeably improved, as is the user experience of the people using the new applications.

      What needs improvement?

      The biggest areas of improvement would be in facilitating team development, DevOps, and integration with typical tools used in enterprise development (Jenkins, Subversion, etc.)

      For how long have I used the solution?

      More than four years.

      What do I think about the stability of the solution?

      Stability problems are usually only experienced when architecture and development are done by people who don't know the tool and its best practices very well.

      What do I think about the scalability of the solution?

      Scalability problems are usually only experienced when architecture and development are done by people who don't know the tool and its best practices very well.

      How are customer service and technical support?

      Technical support is usually pretty good for the easier problems.

      Really complex issues tend to take too long to resolve, but many times that's only because there isn't the experienced person to take it from providing information to actually closing out the fix. If a problem results in a development fix, that is typically pretty quick, too.

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

      I personally used Lombardi and IBM BPM prior to Appian.

      The main reasons for switching were:

      1. Too many off-shore consultants taking all the consulting work, developing shoddy apps while driving down the rates, and generally giving BPM and the product a bad name.
      2. IBM steadily providing release after release that introduced more bugs and making the tool itself less usable.
      3. Appian was clearly becoming the better product and their market share was on the hockey stick slope up, whereas IBM's was falling quickly.

      How was the initial setup?

      I don't typically get involved in the server setup, but my understanding is that it's relatively easy, especially compared to IBM's.

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

      I'd advise to not just look at the cost, but the overall value of BPM and of Appian specifically.

      BPM done right is a huge value proposition for almost any company, and with Appian's low code rapid development model, the ROI can be huge, while the break-even point should be accelerated tremendously.

      This assumes that you use qualified and knowledgeable resources to do the work, and they don't come cheap either, but in the end, they are less expensive and provide more value than cheaper resources who are not qualified.

      Which other solutions did I evaluate?

      See above regarding Lombardi/IBM BPM. They are the other market leader, but while Appian is trending upwards, IBM is on its way down.

      What other advice do I have?

      See above under the pricing/licensing advice, but I can't emphasize enough to make sure you get quality resources who really know the product well. They will understand how to best use Appian to drive the huge ROI that should come from a successful implementation. I also recommend that all technical resources, from the Architect/Team Lead down to the most junior, have a business focus along with their technical knowledge. Only by understanding how the business wants to use the technology can they make good on the promise of BPM and Appian

      Disclosure: My company has a business relationship with this vendor other than being a customer:
      PeerSpot user
      PeerSpot user
      Tech Consultant at a tech consulting company with 51-200 employees
      Consultant
      Best user-focused Business Process Management and Automation

      Valuable Features

      Robust forms builder that allows a developer to build once and the deploy to all browser & native iOS and Android apps automatically.

      Room for Improvement

      The UI of the application has been completely overhauled within the past couple years, but the tools for developing the new interface have not yet been updated.

      Use of Solution

      4 years

      Customer Service and Technical Support

      Customer Service:

      Excellent. Smaller companies like Appian tend to value customer service as a competitive advantage.

      Technical Support:

      Excellent.

      Disclosure: My company has a business relationship with this vendor other than being a customer: I previously worked for the vendor and now perform Appian consulting services independently.
      PeerSpot user
      Mario Treviño Salazar - PeerSpot reviewer
      Mario Treviño SalazarSolution Architect for New Products and Services at a comms service provider with 1,001-5,000 employees
      Top 10LeaderboardReal User

      I received a demo from the supplier and I was surprised because the supplier was able to make a small demo in about 30 minutes and the demo worked in a web browser from a computer and also in a Smartphone (the same demo worked for the two interfaces).

      Buyer's Guide
      Download our free Appian Report and get advice and tips from experienced pros sharing their opinions.
      Updated: August 2022
      Buyer's Guide
      Download our free Appian Report and get advice and tips from experienced pros sharing their opinions.