Pega Platform Reviews

We primarily use the solution in claims for our clients in the insurance industry.

The visualization of the business process and the collaboration aspects of the solution are its most valuable features.

The solution is more user-friendly than its competition, and more visual. Its level of inference is much lower as well.

The solution needs to invest more in its technology. For public and private clouds, for example, the development environment is slow. Saving events should take one to two seconds, max, and because you are making changes often, the slowness cuts down on productivity because we have to wait for things to save before continuing. 

The UI could be slightly improved.

The solution is stable.

The solution is scalable.

The technical support has been very good. They answer our questions in a straightforward manner.

The initial setup can be a bit complex because you don't just deploy the solution out of the box. It has many possibilities and when you are implementing the solution you are setting specific features to align with the requirements of the business. In POCs and real production environments as well you need to think about all of the different aspects and this makes the setup complex.

We handled the implementation ourselves.

We're a Pega partner.

I'd suggest those considering implementing the solution start small and maybe do a POC. That will give you a sense of what the solution would look like in production.

I'd rate the solution eight out of ten,

We are a strategy consultancy for someone who is looking for a Low-code No-code platform for the utilization of digitized service processes. We can determine if Pega BPM is the right fit for them because it can be deployed on the Cloud,on-premise, Kubernetes, and Dockers. We are in discussions with customers with many other solutions, such as OutSystems and Mendix. From a strategic point of view. We're not going to implement only one service tomorrow.

We mostly use European providers. We do not use hyper scalers because of privacy concerns, such as Google, Microsoft, and Amazon.

We use Pega BPM for simple service management processes. We are a consultancy that works for the government. We look at public services and how public services can be supported. These new types of workflow technologies where you to have end-to-end case management. They can be used for public services processes that are created on these platforms.

Pega BPM could improve the artificial intelligence capabilities because they are always valuable and case management for all types of industries is important. Additionally, the reporting performance management capabilities could be better because you want to have insights into how your processes are working, such as Cloud protection. The whole range can be better. However, the platforms are improving every year, they are on the right track.

In the next release of Pega BPM, they should add more ways to do the customer interaction fields in the portals.

I have been using Pega BPM for more than one year.

Pega BPM is scalable. If you have larger data models, for example, thousands and millions of transactions, they have their limits. Larger data models need to be improved. It's not only technically scalable, for instance, if one organization develops a solution built on ServiceNow or Pega BPM, how can you transfer the solution to the next organization that has the same platform. They have a marketplace on most of the platforms where third-party vendors can show their services. For a public organization, if you develop a small application, the next town could use it the same way. How to transfer easily from one to another one. It might not be a relevant case for private companies because you are in competition. There's no need to give away knowledge. However, in the public domain, it's a different case but it's very special, nothing in general.

The technical support of Pega BPM is very good.

If you work with any of those platforms such as Pega BPM, Mendix, OutSystems, or ServiceNow, they have different sweet spots. You should always think about what you really want to accomplish. What do you want to do with those platforms, you have to choose between Pega BPM or ServiceNow. You have to decide what is the right provider, and it is not one-fits-all. 

The platforms are used to be faster. You have citizen developers who can build faster solutions but in the end, if you have no governance, no strict rules on how to use it there can be problems. For example, to put out a fire somewhere, you can do it in 10,000 different ways. If you don't have strict rules, how to do it, you might end up with a crazy solution that you can't manage over time, such as the maintainability of those solutions or of the platform ecosystem in general.  You need strict governance or rules of what to do and how to do it. Otherwise, it will be like a crazy zoo of different solutions and you don't know what it is, how they work, or why they work. If everyone is able to use a solution but they are not using it in the same way it can be improper and this is why governance and rules need to be applied.

I rate Pega BPM a seven out of ten.

Pega BPM is good, it is not the worst solution you can find on the market. However, it depends on what you're looking for. It has to meet the use case that you are looking to solve. Other solutions, such as OutSystems and Mendix, they're more open-minded, you can do whatever you want to do, but they don't have strong case management. In my industry, it's more or less, very simple service processes.

We worked with different frameworks and components that Pega offers to build a complex process management solution for a large scale financial institution.

It helped streamline process management, but was difficult to implement due to the quality of vendors available.

getNext, because it removes some of the management overheads, as well as some of the inbuilt reporting capability.

The UI needs improvement. The product itself does not have too many issues, but implementing Pega solutions is a bit of a challenge due to the way code is handled, and in general the quality of partners available with Pega specialisation could be improved.

My primary use case is for process modeling.

There are several areas for improvement with this product. The performance of the application is very slow, the UI needs improvement, and the architecture needs to be simplified. In addition, it's impossible to know what's going on behind the scenes of this solution, and there's no tech support or useful documentation, so I have been forced to do my own troubleshooting.

I have been using this solution for two years.

The stability's ok once the solution is set up properly.

The solution is scalable in terms of load but not operation-wide.

The technical support has been disappointing - we don't get the support we need from it.

The initial setup was pretty complex.

The pricing is good.

Before choosing, I evaluated Colfax, Oracle, and IBM.

The platform as a whole is very rich - you can do a lot of things with it with minimum time and cost. I would recommend Pega as a BPM solution but make sure that your contract states you will receive support, otherwise you may not get any. I would rate this solution as seven out of ten.

We use it for some insurance companies for underwriting.

The workflow designing and integration are the most valuable features. Also, the UI design was pretty easy. 

All the features that are related to case management are pretty outstanding.

It's called a local platform but on the other hand, it needs a lot of experience. It's not all that easy to click and plug and play. If you really want to use all the features out of this platform, you definitely need a lot of experience and a lot of training to get there.

Because the platform offers a lot of different features, it's rather complex and makes it very valuable for many different use cases, but what I would improve is that you can't tell all the people that it's a local platform, which suggests that it's for everybody, even for those people that do not have any clue about IT. They are using a lot of functionalities that try to help those developers and usually they make good jobs, but there are some situations where this automation will cause a lot of stress and trouble. This is something that creates more work at the end than if you just started from scratch. 

It depends on the use case but in general, it's stable. We have two use cases where we use a lot of different tasks and if you have more than 1,000 use cases then there seems to be some problems with the stability. It may depend on other features like load balancing and those kinds of things. 

It is definitely scalable.

Technical support is quite good if you don't have very special requests or defects. It depends mostly on your own code. But if it's on the general code that is provided by Pega, it's quite easy to set up a question to the Pega team and it's usually answered within a couple of hours, sometimes even faster. 

There's a lot of information that can be found in the Pega community which is quite helpful.

The initial setup is quite easy. If you use the cloud options, you get the full stack delivered and you do not have any hassle with setting up certain features or certain information. If you just install it on your local machine, it is also going to work pretty well. 

It's more complex if you set it up in a local environment on the local server, then you have to check a lot of different things and especially all the things that are related to securities.

I think the pricing reasonable. On the other hand, Pega has a clear focus on future companies. So, they say, "Okay, this is for our main customer focus," and this is, in my eyes, a bit of a pity because I think the technique and the software are really mature and could be very helpful for other companies as well that are not a main focus of them. 

My advice would be to have a focus on what the main purpose of the VPN platform is. Are you really looking for a VPN platform, something that is gathering all the VPN processes in the whole company, or is it just for reporting some processes like a customer process and connecting it to an SAP process? 

If you are planning to use Pega as your main platform, then it's a really good choice. On the other hand, if you have different software in your company like microservices or other big platforms like SAP, then you really should think if adding Pega as another big solid piece of software is really a good idea or if you just look if you can find other ways to integrate the other pieces of software for the purpose.

I would rate Pega BPM a nine out of ten.

I would like to have a lightweight version of it; something like Appian. In the very beginning, you just had Word and Excel, and you were fine with that. Now, you have a complete suite starting from SharePoint and Teams, etc, but you don't need all the features because you have a specific purpose and for this purpose, you need the best software. But nevertheless, you don't need, for example, all these RPA stuff, which is heavily promoted. These are all things that you just buy-in and are reflected in the price. It would be helpful if they offered a lighter version. 

We developed an an underwriting platform for an insurance company. In this project I mainly worked as a senior developer. I have more than four years of PEGA experience in both technical and business consulting. My company is an official PEGA partner.  

The new PEGA underwriting platform replaced the former underwriting system and helped to integrate other legacy systems and functionalities in one application. It also helped to save licence costs for other legacy systems.

PEGA provides many OOTB functionalities which can be configured for your purpose.
What I really recommend are the following features:

* Case Management (incl. extensive Audit Trails)
* User Interface (based on HTML5 and constantly improving)
* Integration (pre-configured functionalities like REST, SOAP, API)
* GetNextWork (configurable algorithm to route the most critical task to users)
* Multi-Channel-Ability (start your case from whichever device and continue on other channels)

PEGA claims that they provide a LOW-CODE-PLATFORM which is easy to use - even for "citizen developers" (i.e. business employees).  bla bla. If you really want to use all the features out of this platform, you definitely need a lot of experience and a lot of training. In all of my projects there were many obstacles to solve which weren't simple and which could not be solved by "citizen developers" but only by Lead System Architects with 5+ years of PEGA experience. You can compare PEGA with SAP - if you really know how to use both of them, it can make the difference. If you are only interested in developing automated micro services / processes, than there are far better options.  

I would like to have a lightweight version of the solution, something like Appian or Outsystems that is much more focussed on process core features. If you set up your first projects and you see that you need more functionalities, than it would be great to upgrade to the PEGA platform.  

For me PEGA is sometimes like the MS Office package. In the past you had the core functionalities like Word and Excel, and you were fine with that. Now you have a complete suite starting from SharePoint and Teams and whatever, but in most cases you don't need all the features because you just have a certain purpose where you need the best software. 

CONCLUSION: The PEGA platform is an outstanding product for those companies that are really willing to use it as a BPM PLATFORM throughout the whole company. The many features and OOTB functionalities makes it very valuable for many different use cases. Those companies that are willing to setup a BPM program for a couple of years will definitely benefit from PEGA.

More than four years.

The stability really depends on the use case. We have two use cases where we use a lot of different tasks. If you have more than 1,000 tasks then there seem to be some problems with the stability. But it may depend on other features like the load balancing and those kinds of things. This isn't my core business but I've heard from others.

Technical support is quite good if you don't have very special requests requirements or defects. It depends mostly on your own code, but if it's on the general code provided by Pega, it's quite easy to set up a question to the Pega team and it's usually answered within a couple of hours, sometimes even faster. There's also a lot of information that can be found in the Pega community which is quite helpful.

The initial setup is quite easy. If you use the cloud option, you get the full stack delivered and there's no hassle with setting up certain features or certain information. If you install it on your local machine, it also works fine although it's more complex. If you set it up in a local environment on the local server, then you have to check a lot of different things and especially all the things related to security and that can add some hassle.

Compared to what you get - the costs are reasonable. However the question is, if you really need all features? Pegasystems has a clear focus on big companies. Although the software is really mature and thus could be very helpful for SME companies, the high licence fee will be an issue for most SMEs.

My advice is to suggest people focus on the main purpose for the BPM platform. Are they really looking for a BPM platform, something that gathers all the business processes throughout the company, or is it just for reporting processes like a customer process and connecting it to some SAP processes or some CRM, or whatever. 

If you decide to use Pega as the main platform, then it's a really good choice. On the other hand, if you have a different software in your company like micro services or other big platforms like SAP, then you really should think carefully whether adding Pega as another large solid piece of software is really a good idea, or whether you can find other ways to integrate the other pieces of software for the purpose.

I would rate this product an eight out of 10. 

The most valuable features of Pega are the integrations that come out of the box. You have extra force in doing some common tasks like OLS, solving situations, or reporting.

What I found useful is irrelevant when our customers often could not afford a full Pega solution. I'd like to see them introduce some cheaper or more affordable solutions.

Some of our clients are still waiting to upgrade from Pega 6 to Pega 7. Only a variety will upgrade from 7 to 8. Overall, Pega 8 is a good platform with improvement.

What should be included is some UI features and maybe some integrations. This includes documentation on how the UI works. For example, some way for the Pega out of the box tools to support UGS. That would be very wise.

My issue is that the UI is hard to see in some small details. You can't do fast work with it all the time. Sometimes a customer has some requirements that you go outside of this box. It gives you the Pegs UI tool which has some limitations about styling and customizing the UI.

For some customers, it meets their requirements and for some, it doesn't. That's my view for organizational use. Maybe they could provide better technical support. 

When you are trying to do some minor attachments, you shouldn't be required to use the UI. However, you can just use the solutions that are already in there.

I like Pega BPM and the way that Pega is in harmony with all of these solutions.

Scalability is a good part of Pega. Big applications are slow. They always have something in a test-mode or something to be improved. Some other Pega features are not too good in my experience.

We are not using Pega in my organization. We are providing solutions to our customers based on the number of users. One of the issues around Pega I've had experience with are applications that confuse the users.

While Pega technical support is okay, it also depends on the issues you need help with and who your contact is with Pega. When you have a solution license, you don't get the support.

You need to go to some other sites, ask questions and hope that somebody will answer them. Pega has a solution where they provide support if you have some issues. You can find a solution with a person who has some experience at Pega for support.

We managed to resolve all of our issues and the overall experience was quite nice.

Setup is the flexibility of Pega from my point of view. There have to be some complex things that make issues on any project. Pega needs some additional features here.

I worked as an integrator and consultant. I did the setup on my own.

My main advice is to look over the solutions for each customer base to understand the main features in Pega and what should be done or shouldn't be done.

In my experience, I've met some people who say that Pega is quite expensive and hadn't even the slightest idea of how to use it and these features.

My main advice is just to get acquainted with Pega as a solution. I will give it a score of eight out of ten. It's quite good.

Pega BPM can be deployed on-premise and in the cloud.

All the scalability issues are addressed with Pega BPM because you can create enterprise-grade solutions with the architecture it has.

Pega BPM has a use case in every sector and area, such as manufacturing, insurance, vendor suppliers, and vendor collaboration hubs.

The most valuable feature of Pega BPM is its architecture.

Pega BPM could improve the UI, it is poorly designed to have a good UX experience.

I have been using Pega BPM for approximately six years.

Pega BPM is stable.

Pega BPM is enterprise-grade and scalable.

The support from Pega BPM is very good.

Using Pega BPM on the cloud is simple. Within five minutes you can have your own Pega BPM instance.

The licensing model from Pega BPM is too complex and is more expensive than other solutions, such as SAP. The overall price of the solution depends on the use case.

My advice to those before purchasing is the UI capability is not good and the cost of the implementation generally is higher in the implementation.

I rate Pega BPM