Pega Platform Reviews

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. 

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

We primarily use the solution for customer experience. We also use it to create some workflows.

The solution provides us with a very good dashboard.

From a technical point of view, it would be helpful to have some advanced analytics to help with configuration. We have a lot of unwanted features and it would be good to configure it more appropriately so that we are using just exactly what we need.

I've been using the solution for five years.

In terms of stability, occasionally there are a few glitches to contend with. It's fine. It's to be expected. It doesn't affect our work too much.

The solution is scalable. If a person needs to expand the solution for their organization, they can easily do so.

Currently, we have more than 20 people using the solution.

We've never been in touch with technical support, so I can't speak to how they are or what the process is.

We previously used Appian. At the time, there was some product integration and it made sense for us to switch to Pega.

In terms of implementation, the solution's initial setup is a little bit complex. It's not exactly straightforward. The software implementation and deployment, for example, is very complex. In comparison to the on-premises model, the cloud is very quick to deploy. The configuration on the cloud is much more straightforward.

If a person is using an on-premises solution, they will need one person to manage it, but if the cloud is deployed, there's no need for anyone.

We're still in the process of evaluating other solutions. We're comparing other offerings to Pega.

We're partners with Pega.

I'm not sure of the exact release number, but we are using the latest version of the solution.

It's a good idea to get clarity in terms of what future upgrades the solution plans to implement. Then, compare it to the competition. It will give you a good idea of what is possible and what will be possible.

I'd rate the solution eight out of ten overall. It's been quite good and we've been quite satisfied with it.

The most valuable feature is the ease of deployment.

We would like to have a better ability to customize PegaRULES.

In Pega, it is very important to have good overall system performance. As such, the performance should be improved.

Better automation would be helpful because I would like to see all of the manual intervention removed.

I have about five years of experience giving applications support for PegaRULES.

We cannot say that any application is fully stable, as it depends on the particular requirements. For example, if we have application automation then we need to make it scalable, but nothing is 100% perfect.

This is a scalable product. We have perhaps 50,000 users across our clients who use it.

I do not generally contact technical support. Instead, our core idea is to determine the issues and resolve them ourselves.

It is easy to install PegaRULES. There are no major issues because we have the proper guidelines for release and configuration. The length of time needed for deployment depends on the requirements for each client.

We have a complete in-house team that performs the implementation and deployment for our customers. This includes creating new rules and definitions, determining which policies are required, managing the system, giving support, and release management. 

We are planning to move our system to the cloud within the next six months, so this is something that we are preparing for.

The suitability of this solution depends on the organization, but in general, I definitely recommend PegaRULES. When assessing the appropriateness of this product for a client, I would first study their requirements.

I would rate this solution an eight out of ten.

The marketing automation is very good. The solution is very convenient to use.

The solution would benefit from more integration capabilities.

There are some tools within the solution that are difficult to use.

I've been using the solution for 1.5 years.

The stability has been good. We haven't had any issues.

The scalability of the solution is very good.

We've never contacted technical support.

I've previously worked with Bizagi, and I find this solution has more features in comparison.

The initial setup is straightforward. Deployment typically takes a few days.

We handled the implementation ourselves.

We use the cloud deployment model.

We've been using the solution for a long time and it's been very good.

I'd rate the solution eight out of ten. There are some technical tools that are hard to use.

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.

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. 

We are primarily using the solution for or our authorization workflow.

The most valuable aspect of the solution is the various workflows.

I haven't been using the solution for that long, so I don't know if there are any features that are lacking.

We need more light retail BPM tools within the Pega system. However, Pega is mostly for big companies.

As our group is pretty small, we may need to look for a different solution that's more geared to smaller sized organizations.

I've only recently begun to use the solution. I've been using it only for the last three or four months.

So far, over the few months we've used it, the solution has proven to be quite scalable.

So far, we've found the solution to be quite scalable.

We haven't reached out to technical support yet. We've been only using the solution for a short time.

The initial setup is straightforward, The installation is not that complicated. One of our team members has deployed it onto the storage.

Our own teams handle maintenance. We have several teams on different projects.

We're constantly evaluating other products. We're looking at others on the market right now.

Most of our use cases are related workflow kinds of tasks like data workflow, user onboarding workflows, etc.

Although the solution might be too big for our purposes, as of now we are continuing with Pega because we don't know of any such tools which have the scalability, as well as the ease of use that this solution provides. That's why we are continuing with it right now.

Although I personally haven't used the solution for very long, I would rate it eight out of ten.