- The Pega platform has enabled us to quickly develop end to end tracking of back-office processes along with a myriad of integration points to legacy systems to automate a number of manual steps.
- Out of the box reporting and dashboards have saved time for our business partners in adapting to the new processes and managing to metrics in real time.
- Prototypes of the workflow are invaluable in gaining a quick validation of the workflow with end users. With Pega, we are able to build those models very quickly.
- The features themselves are not difficult to use, but I think Pega oversells the simplicity to non-technology organizations. While workflow can be built with minor training, having the proper data models and class structures established are critical to long-term success.
- Out of the box, error handling can be confusing to a novice developer in Pega. Pega can handle exceptions automatically but the default “broken queue” concept can get messy and ultimately result in work that sits unnoticed by end users and creates extra work for the support team.
- Experienced Pega engineers are in short supply and therefore more expensive than most other developers.
- 1. to build an approval workflow for Account Payable and Account Receivable
- Business Problem - Automation of approval based on pre-defined rules, routing hierarchy, escalation matrix and on-time reporting
- 2. to build a Collection framework
- Business Problem - Automation of collection processes without manual interventions, the notification system.
- Pega provides frameworks for various domains. This speed-ups the development process.
- Routing, Notification, Assignment, Escalation - these are inbuilt features in Pega. Without minimal configuration, these can be used to solve business problems.
- Pega's responsive user interface helps to create software products for different devices.
- Pega has a very rich support community.
- Handling big data, like a file with 10GB of data.
- Integration with NoSQL databases.
- Customize reporting.
- Using Java8 features like Lambda functions or Stream APIs.
- Integration with popular web services, like Amazon S3, KMS, DynamoDB etc.
- Well Suited - Domain specific problems, especially where task routing, assignment, notification & escalation are involved.
- Less Suited - a framework to handle large data, for example, if you want to process a CSV file with 10GB size with 10 million rows.
- Pega is a robust and reliable product for development and production management. Its core strength is scalability and ease of reusability of code with int he application and as well as leveraging the application into a different line of business/channels.
- Easy Management of multiple teams who are developing code at the fast pace. The deployment process is so quick in Pega7. Pega development enforces and suggests the involvement of business teams from starting and in each phase. It offers good tools to showcase the changes.
- Now Pega evolved even bigger by introducing and including the Decision Strategy manager and robotics which are cutting edge technologies now. Pega offered REST APIs and development of services is quite fast and supporting the wide range of protocols.
- Pega can improve user interface features. Most of the cases business expect different kind of user interface and styles which is a kind of time taking in comparison with other areas and sometimes may not possible.
- Pega can introduce more features in Reports. Reports performance can be improved. It would be great if business and developers are given with more features to customize the reports.
- The learning curve is not very high which helped in quickly integrating newbies to the team and train them.
- It has a lot of deployment ready features e.g : a ready to deploy cross platform UI with minimal customization, engines to handle business rules and a robust data handling engine.
- New state of the art features like IOT integration and analytics are added benefits.
- It is a solution which can be quickly customized for a market-ready product but there is are limitations on that. To go beyond a certain limit needs professionals which are hard to find.
- Pega platform allows us to build a totally customizable UI
- Pega allows us to build logic that replaces decisioning, removing a lot of manul touch
- Pega has proven relatively simple to intergrate other tools with because of its open API
- We had a major issue with the calendering function in Pega. I wanted my technician appointments visualized in a calendar, chronologically, and in a way that they could drag and drop appointments in order to manage their time. I was told by Pega that there is no such capability today, and we could manage appointments only through a very manual, reassign screen.
- Pega's filtering capability on custom dashboards is very limited. When one of my agents does a custom search, and then opens a ticket from the results, when they go back to the results, all of the results have dissapeared and they have to search again. We should be able to click 'back' and have the results saved.
- It allows a fast delivery of new requirements thanks to the perfect integration with Agile and DevOps
- Allows multiple parallels developments in "independent" areas, so multiple requirements can be implemented avoiding long development time.
- Extreme modularity, its rules can be personalized or differentiated by the environment, user profile, localization and so on using few and simple configurations.
- CPQ can be extended with a more powerful eligibility/compatibility features.
Earlier it was all paper work and complex processes which Brokers had to undergo for processing premiums and claims but with Pega application coming into the picture all these are processes are simplified and automated.
- The big advantage is we don't have to have to build the system from the scratch like any conventional programming.
- Case Life Cycle Management - which allows any business user to capture and process the full scope of work in their operations, be it document handling, approvals, decision making, etc. These tasks can all be built into a process flow to automate as much as possible.
- Design-once, deploy-anywhere user interface-saves a lot of effort.
- Less coding, adopts changes and quick developments.
- Should focus on improving the search engine on PDN training.
- Very costly tool for small scale companies.
- Pega’s Strategic Apps, CoBrowse and OpenSpan offerings appeal to mid-market customers, but Pega is not aggressively promoting Pega 7 and Pega Express as stand-alone iBPMS platforms to the mid-market
- Versioning: We can create a new version of a rule whenever case behavior needs to change. Pega maintains a history of changes to a rule, allowing system architects to review the change history and undo changes if needed. Since each rule describes a specific case behavior, the rest of the case is unaffected. For example, a system architect updates a UI form with instructions and removes a critical field. You can review the history of the form and revert back to the version before the changes were made, without changing other rules in the application.
- Delegation: We can delegate rules to business users to allow business users to update case behavior as business conditions change. The business user updates the delegated rule, while other parts of the application remain unchanged. For example, expense reports that total USD25 or less are approved automatically. You create a rule to test whether an expense report totals USD25 or less and delegate the rule to the Accounting department. The Accounting department can then update the rule to increase the threshold for automatic approval increases to USD50, without submitting a change request for the application.
- Reuse: We can reuse rules whenever an application needs to incorporate existing case behavior. Otherwise, you must reconfigure the behavior every time the behavior is needed. For example, you create a UI form to collect policyholder information for auto insurance claims. You can then reuse this UI form for property insurance claims and marine insurance claims.
The application manages end to end life cycle of claims.
We have multiple applications built in Peg, for claims management and fraud management.
- Pega is a Business Process Management tool. It can be used to manage the business flows, and enables us to quickly build end to end applications . It can also be integrated with legacy systems.
- It can be used to automate lots of manual tasks, by using its back end agents features. It can also get updates from other systems and process claims without any manual intervention
- Pega has out of the box reporting and dashboards which can be used to manage the metrics.
- Pega has to come up with ways to integrate with cloud, which is ubiquitous now. The tools should change to adapt it.
- Pega has to improve in providing detailed documentation for all its features. There is very little documentations on some features like high availability.
- Pega has to come up with ways to implement A/B testing. In the current world there is no time to deploy and rollback.
- Building business process applications which have assignments, routing and escalations.
- Best suited for customer care applications.
Less suited for
- applications which have the system of records in some other system (ie) For claims application the claims details has to be in pega, if the info has to be fetched from some other system it makes the application slow.
Pega Platform Review: "PEGA rules the internal customers but needs to impress external customers now."
- Case management
- Rules-based decision making
- Automating repetitive business processes, but being smart to identify changes and also update decision-making rule dynamically.
- Managing incoming and outgoing communications.
- User interface
- Version updates
- Using Pega as a data management tool for the enterprise data
1. Business Process Automation
2. Rules-based Decision Making
3. Managing middle-office/ back-office operations
Not suitable for: Customer facing application and management.
- Pega Platform architecture combines process flow definitions, data handling, case management and other functions in model-based development.
- A non-coding approach based on rules with inheritance helps Pega more attractive product
- Pega's "data pages" capability is a highly flexible data structure.
- Pega's another advantage is that we can design it once and deploy it anywhere
- Like IBM BPM Pega doesn't have integration capability. We expect a good array of products which suits needs of various requirements. IBM's strength is its integration capability.
- There is a scope of improvement of ruleset and version control management.
- Its terminology is somewhat difficult to understand for a new developer
- Pega is the Best BPM tool when working with large projects whose user radius is across the globe. It is flexible, scalable.
- It allows a fast delivery of new requirements, easy to deliver in Agile model
- Best data processing capabilities
- Less customization
- Easy to transform business requirements into Workflows and rules
- No support for minor customizations from Pega team .Ex: I need a calendar icon which can display holidays. They could not support me with this.
- Documentation about new enhancements in pdn is not complete.
- Reports are not enhanced for a long time. We need more scalable features in Reports.
- Latency issue
- Fast development and delivery, very good for Agile projects.
- Pega Support Community is a great forum to learn new concepts.
- It's very scalable and flexible.
- Pega needs to improve in terms of training on new upgrades of Pega.
- The Pega team themselves do not provide history and description for its rules. No proper documentation.
- Machine learning, RPA should be better .
- Should have better automatic unit testing (AUT).
- Reporting needs improvements.
- Decisioning. Pega exceeds expectations to provide solutions to complex business requirements and integration.
- Scalability. Pega is designed to support any size of process management and can quickly grow and adapt for future business needs.
- Rapid Change. Pega solves the problem of implementing a new requirement in an existing system. System Architects can add, remove or change any type of process on the go.
- Pega is so big and complex that implementing a rather easy requirement can be overwhelming .
- Pega requires a lot of knowledge to implement any kind of requirement. There are several levels of certifications in order to properly use the tool.
- Some basic programming knowledge is not enough to learn to use Pega. Some features even go against general programming rules.
- Exceptional handling/fools-proof code for faster results
- Built-in reports
- Faster building of code modules which can be built separately and joined together
- SMA, tracer, clipboard tools which make the debugging process much easier
- Easy building of User Interface
- Advanced shapes like email and work object status auto updations
- Multiple records of data retrieval from the DB causes slowness
- AES built in reports or customization of those reports are limited
- Limited out of the box functionalities
- Special UI components addressing is difficult
- Workflow management. Easy development and maintenance of customer processes
- Integration. Readily available adapters to connect to commonly used systems.
- Time to Market from initiation phase.
- Solution frameworks available for specific industry needs, and can be tailored to meet custom requirements
- B2C engagements
- AI, ML
- Easy development of very high end UI
- Easy to configure and implement out of the box solutions
- The built-in functionality is amazing
- Code sharing and reuse is built into the product
- Inheritance is two-directional allowing for reuse
- Better access to the database for hosted solutions
- Lower cost for smaller applications and businesses
- The upgrade can be easier
- Provide guardrails when code will prevent upgrades
- Claims management. Pega does this particularly well by offering a rich out of the box experience requiring very little custom coding.
- UI building. Pega makes this aspect of software development very expedient by making it a drag and drop experience with auto-generated code.
- I would like to see more How-To guides in the help system itself, in particular, How-Tos for integration rules
- Fast delivery, the release cycle is 2 weeks
- Less coding, easy to learn and handy after few months training.
- Stable and easy to get support, Pega provides PDN, it can be used for technical question/answers, any problem can be sorted out by raising service report
- DCO is powerful, Business and Teck team can both using the same platform
- I would hope Pega can provide more features for mobile apps.
- The Pega foundation is robust and does not require you to build a product from scratch. The greatest advantage is the drag and drop development and Pega takes care of compatibility related issues.
- Pega UI supports skinning, responsive and adaptive design.
- The good part is Pega trains developers through proper certifications and it is well recognized in the industry.
- UI components should be improved to match other frameworks in the industry
- design.pega.com showcase components like radio segment, but there are no OTB components like that to use. It gives a feeling like something is available in Pega, but it is not.
- Pega should also allow easy custom development without worrying much about upgrading the software in the future.
- With flexibility comes complexity. Pega is very flexible so it requires trained IT pros.
- Pega has great community support.
- Pega has good courses that teach you how to develop.
- Learning curve is somewhat steep, however, once mastered everything becomes possible.
- Pega integrates with Avaya - thus making customer popup info, when a customer calls, an achievable task.
- Pega is suitable for medium to large enterprises.
- Pega is a process-driven platform that will enable us to build our checklists into our processes. That way we can automatically follow our established routines and don’t worry about non compliance.
- Pega has a very robust and configurable engine that enables us to build logic into checklists and questionnaires.
- Validation can be built into forms and checklists.
- Develop all functions to be available on an offline device. I recently found out there are some missing options while working in offline mode on iOS device.
Pega Platform: "Easy and quick to build complex apps, can sometimes be limiting or frustrating to work in."
- Quick development time. Much of the Pega "rules" are easy to configure and implement.
- Visually friendly and modern. Much of the UI/UX elements in the system are continuously supported and updated, giving a nice feel to the apps.
- Many of the configurations and rules Pega gives to the developers can also be delegated to business users. The organization and structure of the client's business can easily be adapted in the Pega platform.
- Not all software is bug-free and Pega is no exception. Notable problems arise when upgrading between versions of already existing apps. Pega does its best to support apps but can be slow to respond.
- Small circle of users. Pega is a niche technology and much of its methods and functions strictly apply to Pega itself. There are not nearly as many resources to refer to compared to some of the bigger name technologies.
- Often restricted to the platform. Many of Pega "rules" are restricted, as there are approved "guardrails" Pega wishes developers to stay within. Clients may want one thing but Pega may not support it and it can be difficult navigating around the limitations Pega itself puts in place for these.
Pega platform is used as a development tool to deliver BPM software in our organization. It is used in one SBU not in the whole organization. It is used to develop solutions related to domains such as Healthcare, Insurance Banking and Finance. In addition, it is used to build fleet management system and logistics related system.
Following Pega Best practices and having Pega expertise benefits in developing large scale software solutions in long term. This toll can manage large data sets with reports, It encourages developer to build with the end product in mind. Performance issue handling, Exceptions handling and even including comments is monitored at development time.
There are in built frameworks in Pega platform that provides the ability to develop and deliver solutions faster. Developing UIs in Pega is easy. Developer need to drag and drop inbuilt Pega layouts and can apply necessary CSS and styles using Pega skin. So, UIs can be customized to meet customer needs. These responsive UIs are easily accessible from mobile, tab and desktop with minimum and/or no configuration.
- 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.
- Need more learning materials. For Beginners who have previous programming experience with another language takes more time to learn.
- If the developer is met with an issue in pega platform , they have to rely on Pega supporting team to fix it.
- Customization is available but is not encouraged. Pega does not support faults that occur in customized solutions.
Developing attractive UIs is difficult in Pega.
Pega Platform Scorecard Summary
Feature Scorecard Summary
About Pega Platform
According to the vendor, the Pega Platform transforms business stakeholders into citizen developers with a no code, visual app development experience, while empowering professional developers to architect applications with a model-driven approach in a low code environment. Pega aims to maximize productivity, re-use, and scale for the enterprise while delivering meaningful apps 6.4x faster, reducing development costs by 75% and driving ROI by 321%.
Pega Platform Screenshots
Pega Platform Integrations
Pega Platform Competitors
For the latest information on pricing, visit https://www.pega.com/products/pega-7-platform/pricing
Pega Platform Support Options
|Video Tutorials / Webinar|
Pega Platform Technical Details
|Deployment Types:||On-premise, SaaS|
|Operating Systems:||Windows, Linux, Mac|
|Mobile Application:||Apple iOS, Android|
|Supported Countries:||Global Support|
|Supported Languages: ||All major languages; localization available|