MS SharePoint / SQL vs Pega Platform

• Flexible - able to make any changes we would like vs traditional service desk system.
• ROI - We were already using SharePoint for internal intranet, so we are simply getting more use out of licensing we had already committed to.
• Easy to use for end users.

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

• It is hard to setup and nightmare
• It requires a of infrastructure, thus it could be costly because of requirement and licensing required for everything to run smoothly
• If it is not setup and organized properly from the beginning it could be maintenance nightmare
• It is hard to have "test" environment to do patches or similar

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

• I've installed SharePoint in many different industries and each industry has seen greater collaboration among their teams both locally and nationally. The ability to collaborate more efficiently has reduced the need to have employees centrally located.
• Companies which have used SharePoint in a end user training portal have had great ROI, since they can create the content once and share with all their users who subscribe to their training service. The web content management aspect of SharePoint is a very helpful feature.

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