Appian vs. SAP Build

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.

Incentivized

The SAP Build Process product is best suited for managing pipelines and scrum boards without limitations. Implementation of the software is also simple, and unlimited users can connect the software with third-party systems to push codes. The software integrates well with other products, making it easy to build and deploy pipelines. The only issue with the SAP Build Process is the cost of implementation, which is far higher than that of other similar products.

Incentivized

• 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.

Incentivized

• Its drag and drop editor is even simpler than the very popular WordPress
• No code feature to build any type of website
• Not a lot of technical expertise is required to use this tool
• The client loves it as they can themselves use it for quick tweaks

Incentivized

• 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.

Incentivized

• The only one I can think of that has made me not continuously use SAP Build is the cost of this tool. I see it a bit higher compared to other tools that provide the same functionality for cheaper or free plans.

Incentivized

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.

Incentivized

Although coding would be helpful for improved automation and debugging, it is not a problem for any user to create a workflow and automate things as they wish. We spend way less time on training and developing workflows ourselves. There are also features such as a screen recorder. We have guides internally to teach how to automate better.

Incentivized

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.

Incentivized

There are, for example, great blog writings about automation cases and examples. The studio version is updated often. There are also useful OpenSAP online courses.

Incentivized

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.

Incentivized

Very boring; hard to get through quickly, but rather effective in demonstrating the use of the platform.

Incentivized

It was really seamless. SaaS in the true definition of the word. We logged on and started using the product. Very easy.

Incentivized

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]?

Incentivized

Compared to Mendix, we decided not to go for low code application building and in the other parts of Build, Build is stronger and better integrated with SAP. On the hand of Coding, using Build Code, gives us Joule, which understands SAP better and also have a tighter and more secure coupling with SAP services.

Incentivized

• 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.

Incentivized

• It has reduced the time to develop an app since it has an intuitive interface and allows peer collaboration.
• Produces quality apps through the integration of different plugins, hence improving quality.
• Has made it easy to developer to design apps in their own design.

Incentivized