Nintex Process Platform vs Pega Platform

• Nintex workflows provide a robust interface that's not only intuitive but easy to learn with little to no coding experience.
• Nintex forms are particularly powerful and provide a great alternative to InfoPath forms which is being deprecated.
• Upgrading between versions of Nintex is easy to do with their nwadmin tool and robust documentation provided on their support portal.
• The user adoption rate of their products is extremely high and doesn't require a selling point or an explanation of benefits in converting their existing workflows and forms.

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

• Forms: Some functionality about validation, or buttons need to be implemented using JAVASCRIPT. It would be welcomed to include more functions in this area.
• Forms: The parent-child relationship is another area to improve. Repeating sections don't have the required performance to make a strong relationship between two or more tables (Sharepoint lists).
• Workflow: Using an on-premise environment, there is not a good system to manage workflows: versions, insights, purge, etc.

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

• Nintex has an ROI report that analysis all workflows in your environment and time spent on developing the workflows . We have paid off our investment in the first 12 months according to this report.
• Once you have implemented it, you should probably have more than one person or have plans in place to get more people because the requests will start streaming in.

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