Appian vs Pega Platform

• I have observed after version 17.1 we have a lot of good features in Appian that improve usability (UX). This adds real value in this competitive Digital space.
• You can understand business use case and convert it to a logical process automation.
• Process Modeller has improved a lot and providing smart services use adds more value.
• Service integration helps us to seamlessly integrate with third-party systems

Read full review

• Reusability
• Pega’s Situational layer cake architecture is capable of organizing application to suit enterprise needs. An enterprise can have a complex organization structure located around the globe. Because of Situational layer cake architecture reusing common policies and procedures is easy while allowing for differences between products, regions, channels and customer segments.Whereas with some application development platforms, separate copies of the application should be created to suite different business context.
• Faster application delivery
• With Pega developers can reuse common policies and procedures, replicate functions and industry specific frameworks and utilize pega UI elements to develop applications. IT is easy to deploy.Therefore developers are capable of delivering application earlier compared to some application development platforms. Pega reduces time taken to deliver an outcome.
• Pega upgrades
• Pega platform is upddated to adapt and work with latest technologies.
• Proprietary users support and maintain Pega platform continuously. Pega customer support is always willing to enhance product support.

Read full review

• Appian is continually improving the product but having to learn new features every 3 months (upgrade schedule) can be a challenge.
• Graphical user interface could use some additional improvements but it has come a long way already.
• Sites could use some additional modifications. Currently, the News Feed is not available on a site.

Read full review

• Pega’s Strategic Apps, Cobrowse and OpenSpan offerings appeal to midmarket customers, but Pega is not aggressively promoting Pega 7 and Pega Express as stand-alone iBPMS platforms to the midmarket.
• Pega doesn't support powerful data or process modeling capabilities as compared to the other tools.
• Pega doesn't support full extraction, transformation and loading capabilities as offered by other industry-leading tools. Pega support doesn't solve tickets correctly on-time.

Read full review

• Our objective to reduce customer effort when dealing with government by 25% was exceeded. In the process of applying for an alcohol licence renewal alone, we saw approximately 80% reduction in time and effort for the business customer - and that was just a prototype! Imagine the possibilities when this is taken into a live environment!

Read full review

• With our framework, we have been able to build new applications in 10% of the time/cost. Example, we built an application that took 8 months and 1.2 million k in a traditional .net environment and was able to build a similar application in 60 days for about 100k
• Collaboration with the designer shaves weeks off the requirements gathering
• Standard reporting is a launchpad that allows the users to accept the system without waiting for MIS reports to follow application build which often would usually delay use for 60 to 90, but not with Pega

Read full review