Pega Platform

Background processing

Casetype management

Reporting

Work delegation

API invocation

Specialization

Debugging of Java code if we write for custom requirement

It has an excellent process automation platform.

The reporting feature is very good.

It has connectors and translators to connect with other applications fairly easily

The setup process is bit complex and requires training.

Does not have good data scrapping abilities

Building environment tool itself so i can build large application less than a month.

Powerful and easy to peruse your career, if you don't have a computer science background.

Easy to maintain and quick update on version and patches.

its provides a less code if you have trouble writing code.

Sometime facing challenges post updating of patches.

Improvement needed in reporting capabilities.

complex solution both users and some part handled by the IT team.

It's very hard to find resources in pega.

Case management

Rules

Integration

Debugging tools needs to be user friendly

Process view can be better when compared to other apps

Integration GUI needs to improve

Adaptive analytics - Pega platform allows you to feed data from all your interactions into their interaction history so it learns from past behavior and it starts predicting the best course of action.

Pega BPM - Business process management engine allows you to specify various business rules on a WYSIWYG way so you can visually understand all the process flow.

Pega provides a robust list of use cases on their website where you can learn how other companies implemented the platform and the pitfalls they overcame. Very helpful to also attend their user conference, PegaWorld.

Pega is a very robust platform but it requires lots of technical help to set it up. It would be helpful if Pega created business templates with best practices to follow, based on all their industry experience.

Pega academy is a great resource but only available for clients. I wish this resource was available for those on the evaluation phase so they can learn more about what next-best-action marketing is.

Pega is a low-code platform which doesn't excite most of the developers as they normally love to develop in new and exciting languages. I wish Pega helped facilitate the transition for developers to low code platform. It's a culture change not always easy to accomplish.

Pega RPA has translators for specific platforms which makes it easy to integrate and automate. For example, .Net translators helps to interrogate applications based on .Net platform.

"Wait for Create" feature is not available in any other RPA tool, which is handy during RPA workflows.

Pega RPA has special features for Pega application which makes it a preferred RPA tool for them.

Pega RPA doesn't have centralized control room which is available in other RPA tools. It should be there for the centralized control of bots.

Pega RPA should have better help documents and tutorials. Help.Openspan.com doesn't contain enough examples to understand the product. This will ease the lives of developers.

It should have better recording and data scrapping features which are present in other RPA tools like UIPath, AA, and Blueprism.

Case Management

Easily configurable User Interface

Invoking Service APIs

SR's Hotfixes

Data management

Designer studio latencies

It has very good potential to be customized to fit your needs.

Browser base so it can run on any computer with a browser only. No installation needed.

Java base but no coding required for the most part except some advanced things that might require some coding.

Easy to update when a new version becomes available as long you do not have a lot of customization and you try to utilize the out of the box features.

Pega uses so much new jargon that you need to learn. For example, Harness.

So many drill-downs: every time you need to create something you end up with 5 tabs to drill-down.

For example, if you are adding a property with a when rule you keep drilling down to create everything and it can get a little more difficult to keep track of where you are.

It can be customized to do anything you need and it is difficult and not recommend.

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.

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.

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.

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.

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.

N/A

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.

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

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

Expensive

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