Appian vs. Microsoft Visio

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

Visio is by far and away the best tool that I have used to do Value Stream Mapping sessions with the warehouse I support. It has all of the shapes needed built in to be able to represent all areas of the processes. I also like how you are able to make the drawing as big as needed and when printing it out of Visio you have the ability to use the necessary paper size. The biggest complaint that I have with the software if how it can be cumbersome for non-Visio users (that is, people without a license in the orgnaization) to interact with the Visio Map. We normally have to dedicate one Visio SME to be able to make the changes that Process SME's find since they do not have access to the software.

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

• Microsoft Visio is excellent for organizing thought processes related to our more complex research.
• The diagrams created with Microsoft Visio are ideal for graphically displaying the internal organization of work and research groups through flow diagrams.
• Microsoft Visio is a great tool for managing our students' activities by creating flowcharts that help us graphically visualize the steps of their group work.

• 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

• When navigating through swim lanes, the user must be careful between switching from the point to the connection features as it can be difficult to remember which mode you’re in.
• When drawing “decision points,” it can be difficult to type words like “yes” or “no” between the connection lines.
• The exporting options aren’t ideal. They are hard to create in PDF format.

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

We use Microsoft Visio to keep our diagrams updated and to that end we will need the subscription to keep using the software. Otherwise we will be left with PDF versions of the diagrams.

Incentivized

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

I have always struggled with some basics, such as connection points, object alignment, font consistency, arranging layers and their order (bring forward, send backward), and managing overlap. I usually need to create an initial rough draft and then do a separate cleanup pass to bring the diagram up to my quality standards. If I skip that step, the result generally does not look very good. And once a diagram becomes busy or the file gets large, Visio has been unstable for me in the past, including occasional crashes that caused non-recoverable edits.

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

Overall, I feel that Microsoft's support is weak. They are now such a behemoth that their model of putting documentation online for their users to sift through is totally outgrown. Given the amount of money you pay for these licenses, Microsoft should provide easy one-on-one support for their products via email or chat. The idea of paying their rates for support incidents is ridiculous. If you have an enormous amount of time on your hands, use their support websites and you will eventually find a solution most of the time.

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

Even though it’s a more expensive solution, Vizio is built for the enterprise. Therefore, it integrates perfectly with our existing Microsoft stack, and quite frankly, because it’s such a more mature product, it provides exactly the functionality we need and expect.

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

• Reduces the amount of time I need to create process flow diagrams. In the past I would use Powerpoint or Word which required a lot more effort and time and never looked as good. Visio just takes that headache away.
• Only negative is that I personally believe it should always have been part and parcel of the Office suite, thus giving more users the opportunity to use it rather than specifically having to justify its separate purchase within our organisation. Different now with Office 365 of course!

Incentivized