Appian vs. Plone

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 larger your organization, the more appropriate Plone will be. This is not to say that Plone is a worse choice for small websites, only that the minimum investment for a Plone site is certainly higher than for other platforms. If you already use Plone for your site and are looking for a redesign or an overhaul, I would only advise switching to a different platform such as WordPress or Drupal if your organization is downsizing. For any other situation, Plone is the natural choice for your growth.

• 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

• Plone is a folder-based system, organising content in a similar way desktop-users are doing for the last two decades. No need to teach non-tech customers some relational-database like paradigm for content management.
• Plone is secure. It is the most secure CMS you can get your hands on.
• Plone is flexible, and makes fast development easy.

• 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

• Not everything is configurable or editable by Plone, and when you need to adjust or add custom pieces in, you need to deal with Zope. Zope has an ugly, confusing and difficult UI and structure as a backend.
• Using 3rd party products is difficult to do - there are a few different ways to get them installed, all of which take a bit of luck to get right.
• Building custom products for Plone is not fun. You've got to deal with an archaic framework to tie in that is not well documented (there is documentation about many things, but not great documentation and there are a lot of holes in the documentation).

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

We have critical systems running on Plone so will need it in the future.

Free to use since its Open source, so we don't have to worry about licence costs.

We know how to use and develop Plone and it has no limits.

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

Compared to the amount of Plone sites, users and customizations we have in our organization, the amount of support requests and training needed is really small.

The new user interface in Plone 6 is even better, it is super fast, has lots of different blocks for enhancing the page, has flexible layout system and is easy to extend with more features.

Our Plone sites are very robust. We have critical systems on Plone and we have been running sites on Plone for over 20 years with very little unexpected downtime.

Plone is very intensive in its operations, and if not configured well it can be slow. However it is designed and built with speed in mind and with proper use of coding, templates and caching can perform extremely well under high loads. It is capable of scaling to very high load availability environments with no specific coding requirements.

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 not too many Plone companies in the world. But the ones who are, are high level professionals

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

I have been participating Plone training and the trainers have always been professional. Materials were good and the instructions clear

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

Incentivized

Well organized, professional training with good materials and instructions

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

Drupal: Plone is cheaper, so with Drupal is more complex to reach the required ROI. However, Drupal has a lower learning curve WordPress: For our necessities it has a more expensive learning curve than plone. Joomla, is easier to use. However, it have some issues on security and web content where Plone is much better

Incentivized

Plone has no limits. We have massive sites and can run them just fine

• 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

• The impact Plone has had at the University of Oshkosh is as follows: this software allows student workers to learn about IT departments and CMS's in a user-friendly way. It gives many students great jobs that look great on their resumes.
• Since there are great training manuals for Plone, there is increased employee efficient in the workplace. Training doesn't take long, and if there's ever a question, the Plone manual is a great tool to refer to.
• If an employee using Plone quits, its easy to find someone to replace them with quick training and great resources.