Pega Platform Reviews

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 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.

I've been using Pega BPM for insurance underwriting, claims management, and pricing.

What we like about Pega BPM is their case management feature which we find powerful. We also like its workflow capability.

The licensing model of Pega BPM is tricky, especially for first-time customers, so it's something that they could improve.

The technical support team for this solution could be faster in resolving tickets.

I've been using Pega BPM for five years.

We are satisfied with the stability of this solution.

We have been able to use Pega BPM in different lines of businesses for the past few years, so we find it scalable.

We faced some issues so we had to contact technical support. We raised the ticket and it was resolved. It took a week, but it was resolved.

We implemented Pega BPM with the help of a consultant.

This solution's licensing model needs to be improved.

It's a yearly subscription, but there are no extra costs apart from the standard licensing fee.

I'm using one of the latest versions of Pega BPM: version 8.

It was the IT side, with the help of a consultant, who handled the installation of this solution, so I didn't have much visibility into whether it was easy or complex. It was done over a period of seven to 15 days.

The number of end users using Pega BPM in our organization is 35 to 40.

Deployment of this solution did not take many people: just two people, but for maintenance, we have three people, so deployment and maintenance requires a total of five people. All of them are engineers.

We use Pega BPM almost on a daily basis. We currently don't have any plans of increasing its usage.

I'm recommending this solution to other people, particularly if it is a good use case for them.

Pega BPM is the first business process management software we were able to try. We had an old tool we were using, but it was not a BPM software. 

My rating for Pega BPM is eight out of ten.

The use cases vary. The solution is useful for various types of processes such as client onboarding, opening and processing accounts, policies and quotes, claim registration and reimbursement, underwriting, etc.

The solution offers excellent workflows. 

The amount of processes a user can access is very broad.

The integrations within the solution are excellent.

The solution has the ability to manage different versions of rules.

Overall, there isn't a feature on the solution that isn't useful. The solution is excellent.

There are some UX shortcomings within the solution. However, it's my understanding that they have addressed them and in the next three months they will come out with a new updated version. They will be moving away from HTML5.

I've been working with the solution for fourteen or more years.

We have some clients that have up to 2,000 active users at any given time.

The solution is meant for large-scale enterprises.

It has been used in the insurance and finance industries as well as manufacturing, healthcare, and government. Many governments have started using it as well, so it is being used all over.

We've been in touch with technical support many times. They are quite good, overall. 

The only thing is sometimes responses get delayed because they need to go to the logs, they need to go through all the steps, what someone was trying to do, and what was not working. It's quite intensive. It takes time. Otherwise, it is simply good. Great.

I've previously had some experience with Appian. They are actually quite different solutions. It's hard to compare them.

The implementation is not the quickest. An organization needs to get a good partner from Pega who will be doing the implementation. If a partner's doing the setup the correct way then it all goes well.

We are a Pega partner and assist clients with the implementation.

We have a business relationship with Pega.

We handle both on cloud or on-premises deployments according to the client's needs. Many financial institutions prefer on-premises, because of the data security. However, even some of the banks have opted for cloud as well.

I'd advise other organizations to get a good partner and take time to compare other options and to do a roadmap. Not every product is suitable for every scenario, so it's important to do a bit of research first.

I'd rate the solution eight out of ten.

We use the Pega BPM platform for helping companies establish, expand, or solidify their business process management and workflows.

We do the licensing of the product, and the capabilities of the platform have allowed us to flexible in the type of organizations we work for. Our strengths are in corrections and investigation into the organizational process. We also have our own IT and have existing models that we use for the insurance industry, inventions industry, and others. These models allow us to have a starting point and build out to fit a unique organization's needs. We do a bit of work for the government as well. For the clients, improvements should be an enhancement to business processes, workflow, and efficiency.

A lot of our customers are working with a digital confirmation. The enhanced features in Pega are appealing to our customers as they can use it on designs, digital agility, omnichannel or customer experience. The rapid renew structure allows better implementation over other solutions and aids clients in serving their customers. Because of the features available, we are filling a need we see for our customers. It works with team frameworks and allows them to take proactive decisions with their product lines, data integration, data crunching and some other features that are helpful for customer marketing.

In terms of improvement, we would see a benefit in Pega having better availability on the cloud side. Their presence on the cloud is not as strong as their competitors. Pega and the partners both have needs to enhance their cloud footprint compared to what it is now.

There is room for improvement with RPA as well (Robotic Process Automation) to automatically take action for users. 

The product is also extremely stable. It has a very strong case management base. This holds a lot of complex business to business information and that makes it so implementations and use can be simplified and promptly provided to the customer. The key is that the business department has to understand the product and its purpose in the right manner. I think Pega is one of the most stable applications in the environment of business technology, use, and implementation.

The product is extremely scalable. Scalability comes with two criteria: choosing the number of users and how it will be implemented in the businesses. Some organizations have 40-50 users on Pega and others have more than 1000 users. As far as the scale of use is concerned, there are absolutely no issues. 

The kind of variety and scale that Pega can handle — the different types of business, different types of application, the different types of integration — is absolutely amazing and don't think that any of its competitors come close.

The technical support is extremely good. By technical support, this refers to technical support that we as partners get from Pega. But the support comes in two parts. When we implement Pega, we take ownership of supporting our implementation on multiple levels.

We talk to Pega one-on-one for service requests and we have no reason to complain. That being said there are still some issues here and there, but they are infrequent.

We have been using Pega BPM since our inception based on capabilities. Our expertise has helped us carve out a nice niche with the marketplace.

The Pega BPM is designed in a manner which allows for the product to be implemented by experts and then for control to be handed over to the business users. If the business users are not prepared, the flexibility and ease of use for the business users can't be guaranteed. If the Pega platform is implemented in the right manner, the organization needs to integrate the right skills, the right implementation, and best business practices. 

Unlike other software solutions, Pega is not about having a whole army of developers working to put a solution together. Once the core platform is set, the application can be taken further with even junior developers implementing more controls.

The resources involved in the implementation actually support the organization and the product when implemented well.

As we do the implementations we do not rely on outside teams. We are the outside team with a high level of experience with the product.

Of the business tool available on the market, as of right now, Pega is not the cheapest. But when you choose Pega, it is possible to realize a greater return on investment. The return on your investment is more important. The implementation is a big investment as is the commitment of the organization, but the return is greater.

I would place Pega BPM at around an 8.5 out of 10 because of the cloud and RPA issues. However, Pega is an excellent choice. It is efficient and does what it is supposed to do. It is extremely important to choose the right product and implementation partner. What the customer should be looking for in terms of an implementation partner is the quality of resources that they have, it is not the quantity. 

The Pega resources are classified into solution updates, frequent solution updates and new solution updates. An implementation partner needs to have a core team that brings the solution together. The emphasis is on the people who take the implementation forward.

It is very important to see if the implementation partner has the right interface and the right experience. Organizations themselves need to look at developing a certain amount of internal Pega support. This means choosing a partner or provider willing and able to impart their skills and knowledge. The client has a lot of control on their side. Its good to be able to rely on a strong business implementation partner.

Real-time operational case management and live reporting of key arrival and departure information, including live operational data feeds from both internal and external data sources on web and mobile devices.

Decreased time for plane departures and landing, supported analytical insight for planning of three to six month forecasting, and helped with operational decision planning and support.

Pega Cloud and Pega BPM, because they allowed us to develop and quickly release with confidence using cloud technologies. We limited disruption on core operational systems while proving the business and technology requirements.

Pega Cloud early adoption and use for cross enterprise capability was new to many. The early adoption meant version 2.0 of their cloud service may require refactoring and redesign of some services.