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
Pega Customer Decision Hub
Score 7.1 out of 10
N/A
Pega Customer Decision Hub optimizes customer lifetime value by providing an “always-on brain” to unify data, analytics, and channels into one connected experience. Customer Decision Hub collects data from every interaction as it’s taking place, combines that with the customer’s full interaction history to determine their current context, and then delivers nextbest-action recommendations. Pega aims to enable users to pivot between selling, serving, retaining, and nurturing in real time.
$97
Per User Per Month
Pricing
Appian
Pega Customer Decision Hub
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.
When evaluating Appian we were asked to compare it to other enterprise tools we currently use such as Atlassian's JIRA and Rally. It is really impossible to compare the two for the simple fact that within Appian you can build the workflows and data capture mechanisms that each …
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.
PRPC is a BPM and Case management suite from Pega Systems. Pega is a comprehensive suite which offers a unique theme of BPM development in the market. A no-coding approach based on rules with inheritance makes Pega a very powerful product but is very difficult to learn. Even, if we go to Pegasystems for training, we have to work on a project at least for a year to have some confidence. Areas where it requires improvements: 1) One of the first things that client's IT department questions about is proprietary BLOB column in PRPC, for them, it is a disadvantage, but as we all know BLOB is what makes the highly complex data model of any BPM application fit inside to a common schema which eliminates the help of a DBA. 2) Another area of improvement is: when using the wizards to generate rules (such as the connector wizards) you have to be careful about the level of coupling between the work object's data model and the interface's data model. This can also create maintenance issues. 3) The complete Pega suite of products have a long time to develop and deploy and it can be easily done using other low-cost software.
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.
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.
Pega Customer Engagement Suite is ready to use out of the box with several features, but custom development is always needed.
Although new features can be quickly implemented, they have to go through a screening Business analysis process, QA screening and SCRUM based development.
Pega eliminates the need for custom code, but there are rare cases where an specific requirement has little to no support from Pega, and implementing custom code can break OOB functionality and make the system unstable.
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
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.
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.
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.
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]?
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.