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 Platform
Score 8.5 out of 10
N/A
Pega Platform is a combined business process management and robotic process automation (RPA) platform with advanced workforce analytics from Pegasystems.
$0.45
one-time fee per case**
SharePoint Designer (discontinued)
Score 3.0 out of 10
N/A
Microsoft's SharePoint Designer was a tool for developing SharePoint applications that has been discontinued.
N/A
Pricing
Appian
Pega Platform
SharePoint Designer (discontinued)
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
Low-code Factory Edition
$0.45
one-time fee per case**
Standard Edition
$0.80
one-time fee per case**
Enterprise Edition
Custom Quote
No answers on this topic
Offerings
Pricing Offerings
Appian
Pega Platform
SharePoint Designer (discontinued)
Free Trial
Yes
Yes
No
Free/Freemium Version
Yes
No
No
Premium Consulting/Integration Services
Yes
No
No
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
—
**350,000 cases / year minimum. Additional cases available in blocks of 150,000.
—
More Pricing Information
Community Pulse
Appian
Pega Platform
SharePoint Designer (discontinued)
Considered Multiple Products
Appian
Verified User
Manager
Chose Appian
All 3 platforms we looked at met our requirements. The Pega Platform was rejected due to lack of ecosystem partners and consultant availability as well as price. The IBM platform was a very strong offering but a little less open on integration to non-IBM databases and …
Appian compares favorably with other vendors in the space. It is strongest with business workflow automation and to create custom business applications. The tool base for coding is extremely straightforward and allows for faster coding and deployment. Handles very complex …
Appian provided a better IDE for implementation, strategy to upgrade to newer versions, Appian had a simplified model to integrate with APIs and handle their responses as well as providing more robust BMP and RPA capabilities.
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]?
Perceived as easier to operate and significantly lower cost to implement when originally implemented. I do believe Pega has become more competitive in this regard.
Against programming languages like .NET and Java, Appian is faster to design and develop applications, but it lacks the flexibility in UI and advanced debugging tools. Against Pega, Appian is easier to use and less expensive.
The main advantage of Appian is the cost structure that is more suitable for starting a test-project to see how develop in Appian and most of all how Appian is accepted inside the company. In few weeks you can show the first results and start the journey on digitalization.
We have reviewed Appian against other BPM application/suite such as Pega, Empirica, and so forth. In the end, we found low code with the Appian product to be the most robust and scalable with good performance. Like all evaluation criteria that they have to be balance with cost, …
Good Support from Pega Technical Team, Continuous Improvement of the Platform and faster innovation and inclusion of new features
Verified User
Consultant
Chose Pega Platform
Pega offers a business-friendly toolkit for defining applications. Unlike traditional BPM tools, there is much fewer complications, the technical syntax to handle in modeling processes and hardly any hard-coded programming. A well-trained business user can be trusted to create …
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.
Pega Platform has introduced the low code feature, using app studio seasonal and professional developer can develop application easily and quickly. The initial application can be build by Business analyst and product owner who has less knowledge of Pega Platform, further application can be enhanced/extended by professional developer. We can develop end to end application and promote to higher environment. Easily we can perform parallel development using branch.
SharePoint does not provide, out of the box, a tool to create / update workflows from web. You have to use SharePoint Designer in order to create them. If you need to implement custom workflows for specific business processes, then SharePoint Designer is well suited. SharePoint Designer allows you to create workflows with task approval, email notifications, assign variables and update SharePoint Lists / Documents properties. In our company, we have created specific workflows for : - Purchase order - RH forms validation like annual employee review - Dematerialized existing forms and validation
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.
Quick development time. Much of the Pega "rules" are easy to configure and implement.
Visually friendly and modern. Much of the UI/UX elements in the system are continuously supported and updated, giving a nice feel to the apps.
Many of the configurations and rules Pega gives to the developers can also be delegated to business users. The organization and structure of the client's business can easily be adapted in the Pega platform.
2013 Workflows - Loops: You can build loops to work while a value (not) equals something, or N number of times. You can insert Parallel Blocks to do multiple things at once, or to watch for multiple things, and when 1 thing finishes, cancels the others and moves to the next step or stage.
2013 Workflows - Stages: Previously all we had were steps, which worked sequentially. With the Concept of Stages, we can create blocks of steps and based on the data collected during those functions, we can tell the workflow to go to a different Stage in the workflow based on a set of 1, or multiple, Conditionals in a transition area after each Stage. Giving you the power to develop multiple entire processes and skipping to the correct part of the workflow, rather than going through 20 conditionals to find out you needed to do action 31.
2013 Workflows - REST API: the "Call HTTP Web Service" is a very powerful tool, but hard to understand if you have never seen it done, or have a guideline. It works very similar to the requirements in PowerShell to connect and get and post data to SharePoint using the Rest API. You can also use this to manage permissions on List Items, Lists, Sites, and Site Collections. Best part is when developed correctly, it is SUPER FAST!
Intentionally Building Infinite Loops: I have built multiple review process from Managing Certifications to Updating Published Documentation, that monitors when an Item, based on provided approved metadata, when the "Author" needs to review the document within the given amount of time. They will get e-mails with links asking if changes are needed. If not, it is routed to the Approving Executive, and the Workflow Automatically updates the Metadata to push out the review dates to the next date, based on metadata provided on how how often the document should be reviews. By using conditionals in the transition of stages, it basically starts over, and goes into a parallel block to allow the monitoring of multiple values of metadata to move to the next stage. Very Powerful when you want to automate these types of process. It truly is a "Set It and Forget It" process.
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.
In the newest version of SharePoint Designer, they have gotten rid of the Design view which makes what used to be quick and easy changes much more code-intensive. This makes it harder for non-IT users and is more risker for all SharePoint Designer users.
SharePoint Designer workflows have a lot of functionality, but there are also some crucial limitations, such as not being able to put lookup fields in email subjects or using parenthesis to separate/group logical conditions.
Although this goes along with the Design view, there really isn't a good user interface anymore for adding conditional formatting and styles in views/pages.
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
Pegasystems has continued to demonstrate a strong partnership with our organization and investment in their product that aligns with our overall vision and need. Pegasystems has engaged us at every level, with the assistance of minor defects to the overall roadmap planning and alignment of our goals
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.
Pega Platform is enhancing its product and launching new features day by day which help to achieve customers needs. If I talk about the earlier version of Pega Platform (i.e. pega v5 and 6.3) there were many numbers of limitations in Pega Platform and if we need to do some customization then needed to write custom java and jave scripts to achieve the functionally. Now I can say Pega Platform is running with market trends and demand. Pega Platform is giving all the options which support the current technologies like decisioning capabilities, real time processing, mashup, process fabrics etc..
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.
It’s very slow sometimes, but that may be our servers. Also the Knowledge Library needs some work - again, not sure if it’s our setup or what- but I’m unable to search the body of an article for content, so I have to be very intentional with tagging, but it’s not ideal.
Support is good from Microsoft. They are quite responsive when we raise a ticket but SP Designer support will be ended by Microsoft in the near future as they have got new techs like PowerApps and Flow to achieve the same functionality SP Designer does and even more than that.
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]?
We did evaluate multiple products offerings with Pega Platform capabilities and observed that Pega PRPC rules engine and case management capabilities are better over so many BPM Tools. We also conducted a detailed study with developers to identify the best products out of Suite of BPM products. It's observed that Rules engines integration is very streamlined with forms in Pega whereas other tools multiple have powerful data model capabilities but lacks the ease of creating business rules.
I haven't used anything else like this. I use different products for workflows and forms, but they aren't listed in the listings for this page. Instead of using it for workflows or forms (deprecated 2 years ago), I use Nintex. For everything else, I have what I need in the Modern version of SharePoint online
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.
For one of the applications we worked on, we were able to reduce the processing time on a case from 2 days to 20 minutes by utilizing Pega
We were able to resolve the issue of the routing of cases to users based on a specific algorithm by use of Pega
Pega case management feature was extensively used in one of the application to establish a parent-child relationship which was very helpful for all the business users
For my needs, I have not found SharePoint Designer useful for my day to day maintenance of SharePoint. It is useful for viewing all the objects that make up the SharePoint site.
It is not as intuitive in regard to setting up Workflows. I have yet to use it to set up workflows in SharePoint. Maybe if I needed more complex workflows, it would be beneficial.
I like to use SharePoint Designer for moving around files within SharePoint sites.
