Appian is a low-code development and business process management platform. It features drag-and-drop design for app building, automated work processes, unified data management, and cloud-based deployment.
$0
Bonterra ETO
Score 6.4 out of 10
Enterprise companies (1,001+ employees)
Case management software that consolidates data, caseloads, and service delivery programs, helping users to save time and serve more people. Bonterra ETO is purpose-built for organizations looking to improve their program and case management. ETO is built in accordance with industry security standards and includes tools that helps users to focus on advancing their missions, as well as: Reduce time spent entering data into separate systems to increase overall data…
N/A
Pricing
Appian
Bonterra ETO
Editions & Modules
Appian Community Edition
$0
Application - Input-Only
$2
per month per user
Application - Infrequent
$9
per month per user
Application - Standard
$75
per month per user
Platform
Custom Quote Priced per user with unlimited apps.
minimum 100 users, no maximum
Unlimited
Custom Quote Priced per development with unlimited apps.
unlimited
Platform
Custom Quote Priced per user with unlimited apps.
Minimum 100, no maximum
Unlimited
Custom Quote Priced per development with unlimited apps.
Appian works great for automating manual processes and integrating multiple systems through its toolset. It gives great flexibility for establishing rules for approvals, routings, escalations, and the like. Because of the low code toolset, it's very easy to deploy and make changes as needed as processes evolve and as the organization learns to utilize the system better. Minimal maintenance is required to support the applications build on the platform. Some of the automated testing integration with tools like Jenkins is limited so that may be an issue for some.
ETO Social Solutions should be avoided until they start caring about the problems generated by their software. In regards specifically to the ARMS suite utilized by the entire state of California, until the ETO software learns how to speak with SOMS, and unless it can be customized by knowledgeable people who consult with front-line users. It is not appropriate to provide the state legislature with bad data. I have 6 years of experience with it and I have multiple sources of agreement from fellow users throughout the state.
Allows at a glance workflow documentation which assists in the need we have for information readiation.
Drag and drop interface for workflow development greatly speeds our apps time to market.
Using the advanced features of Appian, we are able to create working sites in a fraction of the time it would take to do so using "traditional" development.
ETO's customization allows for the use of so many different and unique applications.
The ability to build extremely customized reports also allows us to get very detail oriented results or very broad building wide stats.
The additional added features such as workflow, referrals, and ETO Engage are useful in their own way and add more ways to better track and record data while simplifying some end-user processes.
Search issues when type ahead and database search are used in the same field.
Buttons implementation where user is require[d] to click on the button description - if clicks on the button outside that text - button will not work.
Problems with using certain off-the-shelf performance tools like WebLoad or Neoload. That is because of different dynamic variables being used internally in Appian - which these tools are unable to correlate. We are still investigating using other tools like Jmeter to overcome dynamic correlation problem for performance testing.
The user interface is not intuitive and exceptionally difficult for non-tech savvy people to learn.
The system is not as customizable as we were led to believe at the initial purchase.
The system does not interface well with other systems. Organizationally we are moving towards data integration, and we will likely replace ETO because of this limitation.
Considering the limitations of the system, the cost is quite high. We've seen only marginal benefits of this system over pen and paper, and the ROI is not promising.
The initial build process was very frustrating. We didn't understand what the developer was billing us for. Something like simple touchpoint forms was billed for more hours than it would seem to require.
A system like this should be both fully mobile compatible and have offline functionality.
We would benefit from more nuanced security settings.
We recently renewed our license with Appian. We are convinced that its flexibility, relative ease of use, the support they provide, there mobile advancements and their general willingness and desire to see us succeed all contributed to our reason to renew our agreement with Appian
Social Solutions has been great for our organization. It has allowed us to not only report on data, but to dive into it to see trends and give snapshots of the current status of our neighbors. Social Solutions has been helpful in getting us to see additional ways we can use our data and ways that it is easier for front line staff to use this tool
Appian is a low code environment, because of this, a very good visual interface is required. Appian is providing a feature-rich dashboard [that] we can use for building the dashboards and other interfaces. Appian also provides patches and releases to enhance these features. A developer can start off development just by going through a basic course from the Appian learning community.
As a technically savvy person with experience learning new database software systems I find ETO relatively straightforward now that I've been trained in it's use. However, many of our staff are less technically savvy and the learning curve for ETO can be grueling for many, who require frequent troubleshooting and support from me. Additionally, there are small quality of life improvements that would increase usability even for me - such as allowing multiple tabs to be open simultaneously or being able to use the browser's "back" and "forward" buttons.
Routine maintenance is announced with plenty of lead time, and the few times I've been unable to log in to the system properly a simple refresh was all that was required to fix.
Mostly really strong now, although I understand that for some years before switching their hosting service to AWS performance was a real issue with ETO and we had frequent problems with pages timing out or other glitches stemming from performance issues. With AWS that is mostly a thing of the past, although it is still a major issue with the reporting tool which is unable to run reports on the entire database due to performance limitations, instead requiring admins to define universes prior to running queries.
Appian is one of the leading low code business automation platforms that support RPA, decision rules, case management, workflow automation, and machine learning all in a single bundle. But it is also harder to implement and replace the traditional business process.
We love the first tier customer support folks! They're friendly, helpful, and knowledgeable within the scope of their position. The experiences we've had with their supervisors have also been mostly good and again they seem to be doing what they can within the scope of their positions. This is what prevents me from selecting 1. Unfortunately, none of these wonderful folks can offer real solutions when things are actually broken. They verify there's a problem and send it to the black hole called "the developers". After that, we don't hear anything useful and we figure out how to live with/work around the problem ourselves. (Requests for updates typically get "still with the developer" responses.) This is highly frustrating given that most of our issues are basic system issues (functionality that worked then broke after an update by Social Solutions, servers not syncing, report universes not flattening automatically, etc.). All we want is for the system to work as designed and to be fixed in a timely fashion when it doesn't. Apparently, that's too much to ask. (And no, we don't expect it to happen instantly, programming and quality control checks obviously take time.)
As analyst I participated in a developer boot camp. At times it was hard to keep up but most of the time it made sense. Trainer took the time to explain and slowed pace down to answer questions etc.
Really good trainer and exhaustive curriculum covered, but ETO is a complex enough system that you don't *really* know how to use it until you've been in the trenches for a few weeks. For instance, I took a Report Writing training and emerged with some fluency in the reports interface and a vague understanding of the process, but immediately encountered a legion of instance-specific idiosyncrasies that would have been totally impossible to address in a webinar training for a dozen folks from different orgs working in different instances.
Hard to say, as I was not with the agency at the time. However, based on our use of the software ~5years later I can say that there were no catastrophic design choices made during implementation that have become unduly burdensome as we've scaled up.
Appian has enormously transformed and keeps on updating the product every quarter to meet the latest needs of the world with new innovations & technologies being integrated within the platform. What gives more pleasure than a product that keeps on continuous[ly] improv[ing]?
When we made our decision several years ago Social Solutions had just acquired Apricot. At that time it was recommended to use ETO based off our revenue stream. However, it seems like Social Solutions has put in a lot more time and effort into Apricot over ETO and it seems more modern and user friendly. I think it is worth a second look once our contract expires
The core product scales well, and we've grown quite a bit as an agency during our use of ETO. However, there are some real pain points particularly around creating new programs and managing report universes that require extensive offline checklist resources and a full-spectrum understanding of how changing settings in one part of ETO can have downstream impact in other areas. This can introduce a "chilling" effect on proposed changes to the system, where there is strong incentive to leave things as-is to avoid unforeseen consequences.
I believe it has negatively impacted our release dates. There may have been a misunderstanding as to the learning curve, even though it is "low code."
The look and feel of the applications created using Appian have uniformity and it's easier to have "reuse" between applications.
There is less developer control when it comes to features. I think this mainly has to do with the amount of plugins available. I would think there should be many more available plugins. But again, our use case is probably different than most others.
I would say that at this point the overall ROI has been negative as we aren't getting much more out of our data by the switch we made to ETO, but the cost is much higher. I anticipate that will change as we get better at using ETO.
Most users that have switched to ETO in our organization prefer it to what they were using before and some are more appreciative of the value they can get from the data.
