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
Agentforce Health
Score 8.3 out of 10
N/A
Salesforce Agentforce Health (formerly Health Cloud) is a patient and member relationship platform designed to deliver personalized engagement, and provide a complete view of the patient.
N/A
Pricing
Appian
Salesforce Agentforce Health
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.
Unlimited
No answers on this topic
Offerings
Pricing Offerings
Appian
Agentforce Health
Free Trial
Yes
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
Yes
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Appian
Salesforce Agentforce Health
Features
Appian
Salesforce Agentforce Health
Low-Code Development
Comparison of Low-Code Development features of Product A and Product B
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.
Salesforce Health Cloud is great if your organization has the expertise to integrate with your EMR system. All the functionality of service cloud plus healthcare related synergies to help with easy to use appointment reminders and further health suggestions are a huge plus.
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.
They can have standard pages or components which can directly be used to book or record the appointment with the practitioner.
[I believe] there is nothing more that [Salesforce] Health Cloud can improve as already everything comes under automation, from [booking] to service issues, everything is automated.
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.
It is a wonderful platform with some limitations in it's ability to easily connect with Epic. If your system has the experience and ability to build the connector, you will have great success and a robust platform to do all you need.
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]?
When it comes to Health Cloud in other CRM we have to create the related object and fields and we have to set [up] a complete architecture for the healthcare business to run over the CRM. But here Salesforce is proving a managed package, which is Health Cloud, has the framework already built we just [have to] use the standard functionality and get our task with automation done. This has definitely reduced the effort of developers as well as the agents who are working on the Health Cloud. [Even] a person with very little coding skill can use this CRM and get [their] task cases, etc. automated and [the] perfect solution can be built with low efforts.
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.