Pega Platform Reviews

The solution offers business process modeling when it comes to processing your models or maybe your workflows. 

Every company will have a process where it goes from case initiation to different stages based on the business need or business requirement. Pega helps get processes routed to different or next stages depending on the business rules and based on where it needs to be routed. 

Out of the box, Pega provides processes where the assignment will be picked based on some criteria or many other attributes. It's purely based on your business needs. It ensures the process is routed through the correct criteria from start to end and helps manage the entire flow, the process, and everything.

The solution offers many use cases. 

The case management is great. 

Pega provides a lot of advanced smart shapes wherein you can just create a case for using the smart case itself. You can integrate or maybe add any integration points you need there. 

A lot of Pega is out-of-the-box. You can use it as is or configure it in just one click.

The UI part needs improvement. 

Some integrations can make it unstable. They need to strengthen the integration aspect and make the process more seamless. 

It would be nice if Pega provided suggestions while users were on it. It already gives you some warnings, however, in relation to specific rules, it would be ideal if Pega could provide suggestions to help users make improvements here or there.

I've used the solution in almost every project I've worked on. 

We have hundreds of people using the solution in our company. 

The scalability is good in general. I would rate the ability to scale eight out of ten. 

Technical support has been good overall. 

I worked on a Vis ID tool and a BPM tool. It was for a short span of time. Pega was far better than that.

While it is not too complex to set up, you do need to understand the solution and know the rules. 

We have people in place just to set up the pipeline and everything. The Pega team has to work with the system team to set up everything and maybe one or two people are involved over there. From the core setup perspective, it's the role of a developer who has to do it. There's typically a lead and two or three developers that handle the setup and validate things once deployed. 

We did have some help from Pega during the initial implementation. Mostly, we handled the setup in-house. 

We have witnessed an ROI while using the solution. 

The pricing is quite good in general. I'd rate it nine out of ten in terms of affordability.

We've deployed the solution both on-premises and on the cloud.

It's a pretty good tool. If you're using it as an adjusted rules engine, Pega gives you the flexibility to integrate with different applications seamlessly. You can give the responses back as well. It has scalability. It makes it easy to maintain rules and you can delegate things seamlessly from Pega when you're doing that. 

I'd rate it nine out of ten overall. 

It's built on the base core product.

Pega provides a lot of out-of-the-box capabilities in terms of rules. You need not write anything. If there is anything that's specific to your company's need, then you'll go ahead and do a "save as" and work on those activities. That said, PegaRULES already provides most of the out-of-the-box activity for sending emails, sending correspondences, or most of the items that you do on general web applications.

Pega helps speed up and create rules around sending in correspondence as transmittal things, for example, PDFs, et cetera Pega gave us a lot of out-of-the-box rules we could just apply. It already converts from bytes to streams and PDFs to any other format, and it generates and gives reports to users. You need not worry about what Pega does inside, the back end. Everything is handled and you just benefit from the work it does behind the scenes. 

The rules Pega provides for almost all the areas are great. Pega provides a lot of flexibility or out-of-the-box rules. You do not need to write your own code. It's a low-code solution which makes it very easy to use. 

The setup process is pretty simple. 

It's not too expensive.

It is stable and reliable.

The solution can scale.

Technical support is helpful. 

The UI needs improvement. 

Some integrations can be a bit complex during implementation. 

Other than that, we have not come across any missing features. It's been very good across the board. 

I've been using the solution for nine years now. 

The stability is decent. It's reliable. I'd rate it eight out of ten overall. There are no bugs or glitches, and it doesn't crash or freeze. 

The scalability is good. I'd rate it eight out of ten overall. 

Technical support has been quite good overall. We are happy with the level of support we receive.

Positive

We previously used a VPN tool before. This solution is far better. 

The solution is fairly straightforward to set up. It's not overly complex. That said, some of the integration is a little complex. Apart from that, everything looks good.

It doesn't take too many people to deploy the solution. 

We have witnessed an ROI while using the product. 

The pricing is very reasonable. I'd rate it none out of ten in terms of affordability. It's not overly expensive. 

We have the solution deployed both on-premises and on the cloud. 

If anyone is checking out Pega or maybe trying to use the tool, I would say just go ahead and do it. It's a pretty good tool in the market, and users can easily deploy it to try it out.

I'd rate it nine out of ten overall. 

Our use case for Pega BPM is BFS process management. Earlier, we were facing some challenges such as using the end numbers of applications, but now we are careful. Decision-making took too much time in the past, but now that can be done within a few hours or a few days. For example, when managing a claim, that used to take almost five days to a week. Now, that would only take two to three hours in terms of resolving issues. The processes are much faster now in Pega BPM, in particular, almost ten times faster.

The most important features of Pega BPM are case management and claims management, and soon they'll also be offering claims processing.

I also love Pega BPM in terms of performance. It's also one of the very few user-friendly solutions in the market. It may take some time to learn Pega BPM, but once you get a proper handle on it, tracking and managing processes become very easy anytime, anywhere.

Pega BPM also has very good documentation you can use to learn the solution. Pega has a community portal that has complete information and explanations, and if you're facing a challenge, you can post your challenge on the community portal and get a resolution at the same time.

Currently, there isn't any feature I want to be added in the next release of Pega BPM because Pega always adds new features that my team welcomes and looks forward to learning.

One area for improvement in the solution is the long learning curve, but after that, you'll find Pega BPM easy to use.

I've been using Pega BPM for almost four years now.

Pega BPM is a stable solution.

Pega BPM is a solution that's easy to scale.

I haven't contacted the Pega BPM technical support team yet, but when an issue arises, and I would need to contact the team, hopefully, there would be a good response and availability from them.

Pega BPM is my first BPM solution, so I have no experience with other similar solutions.

Setting up Pega BPM was very easy for the team. Deploying the solution is so much faster and takes up a lesser amount of time than other solutions. For example, if a competitor takes a month to completely deploy, Pega BPM deployment will be completed within two weeks, or almost half a month.

I would rate the setup for Pega BPM four out of five.

We implemented Pega BPM in-house through our BPM team.

In terms of the pricing for Pega BPM, other solutions may be cheaper, but it doesn't matter if Pega BPM has a higher price tag because what's important is that it's the best solution, and that is what people look for.

If I would rate the pricing for the solution, I'd give it three out of five.

You have to pay extra for additional features in Pega BPM.

The business process management solution my team uses is Pega BPM, particularly the older version 7. My team is planning to onboard the new version of the solution, version 8, soon.

Maintaining Pega BPM is sometimes expensive, but it's manageable. It takes money to maintain the solution, but it's a good product based on the service it provides to customers. Pricing doesn't matter because what matters to any client is that the solution should be very good and should provide accurate results. This is the main reason people go with Pega BPM.

My company has a team dedicated to maintaining the solution.

Five to six people currently use Pega BPM within the company.

For now, I don't have any suggestions for people looking into implementing Pega BPM because for sure those people have research teams that do the research and implement the solution according to market research. They know exactly what type of solution is needed based on research.

I would recommend Pega BPM to new users of BPM solutions or local platforms, but research is still required before implementing the solution.

My rating for Pega BPM is nine out of ten.

My company is a partner of Pega BPM with clients it provides services to. My company also provides implementation support to clients.

I am currently using it in my current organization. I have recently joined a new organization that also uses Pega, but in my previous organization, we used Pega for a couple of use cases where we set up automated workflows and other things.

We were doing straight-through processing and had everything set up. And we had RPA, and BluePrism bots there that we wanted to decommission, we set up Pega to do so.

We had issues with RP as a technology, as well as numerous challenges with some critical processes. Now, what used to always fail, too many bots and too many handoffs, both human and automated, is where we thought we would build APIs and integrate Pega.

When we were implementing in 2012, we also used Pega phones. It was a complete front office to back office interaction that was created, followed by case management. But I'm not sure, if you say case management as a feature, there's also knowledge management, which is present, but case management is what I've used extensively. 

Overall, the ability to integrate with multiple applications and effective case management is the most valuable.

If it could also be integrated with robotics, it could help with a lot of things, even if we don't have APIs, we could still talk to other applications. If it could invoke a bot, for example.

It currently has OpenSpan, but OpenSpan is a different thing entirely, as you call it in robotics order. 

If the BPM and robotics could be integrated more easily, then I believe both could be used.

It is not at all integrated. OpenSpan operates in a completely different manner, and Pega operates in a completely different manner. Part of it is called Pega robotics, but it has nothing in common, in my opinion.

I have used Pega BPM for quite some time. I started using Pega BPM in 2012, it has been for 10 years.

However, because I was leading at the time, I didn't have much experience with the tool. There was one client at the time, where my role was to lead a 60-person team. 

We actually did massive implementations. We used that finance framework to create a lot of workflows, at least three to four workflow applications that were quite large, as well as a lot of integrations and such. 

We did use it extensively from 2012 to 2015. We are still using it.

Pega BPM is definitely a stable product.

Pega BPM is scalable.

I am not sure how well it will work because we have a lot of requirements that I see today, we have a lot of emails, that we want to set up, all of these as workflow. I am still trying to understand and see how all of these emails will be converted to case management and email listeners, how much it can be scaled, and whether it'll work properly or not when the volumes increase because we have a huge demand right now. We also have to see how Pega will support us.

We haven't reached the point where we can scale to maximum capacity to see how the product performs. However, we can currently see that the product is scaling based on our requirements.

Because I am new to the organization I don't know how many users it has. But, in the previous organization, I believe there were many business units that used it, including the front of house and back of house. I wouldn't have a figure in mind.

At my previous company, I was one of the business units that used it. I wouldn't know, but from my business unit's perspective, the front of house was probably 200 people.

It is used daily, and we get through our smart forms, we get the inputs, and then the back office creates the interaction, and the back office works on it.

They have a very good support system.  You must have your contacts in place, and they must respond to you based on the escalated level. It's fairly consistent.

I would rate the technical support a four out of five.

Positive

So far, I have primarily used Blue Prism and Automation Anywhere for RPA.

The initial setup was difficult because, as previously stated, there were numerous integrations. However, we had excellent support from the ECS team, the Pega team, and the platform setup. 

Once we got it set up, I would say we were pretty stable. Once done correctly and set up properly, it should be more stable than an RPA solution, in my opinion.

I would rate the initial setup a four out of five.

The initial setup was done in-house.

It was in-house when I did my setup. It was not a cloud setup, but rather an in-house setup. We did an upgrade, and everything was done in-house.

I would rate Pega BPM an eight out of ten.

Pega BPM is used by us for customer onboarding, support, and care.

Case Management, as well as Workflow Automation, are Pega's most powerful capabilities. 

By creating a visual layout of the business process, designers can easily go and implement the business process. And from there, you can pretty much do it in concur. You can concentrate on each area of the business process and create user input tasks with defined role-based access controls on each of those user input tasks.

Pega's low code development is entirely based on object-oriented and application development. However, I believe it can be used in a low code application, such as development platform features such as tracking and dropping some user components. It has that support, but not to the extent that other platforms do, such as the app in or out system. They make it very simple to create UIs without the need to use HTML, CSS, and JavaScript together to create pixel-perfect UIs. I believe Pega could improve in this area.

I have been working with Pega BPM for more than five years.

It's fairly stable and in performance as well.

We didn't have to put much effort into upgrading our platform and adding more resources. I would say that the platform is obviously very robust and capable of scaling to large enterprise-scale recommendations.

In our company, we have more than 300 people who use this solution.

Technical support is very good. They usually respond quickly to inquiries, whether they are about infrastructure or products.

The initial setup is straightforward. You can now create your business processes and begin designing forms for end users. On Cloud, it is pretty straightforward.

Maintenance is dependent on the size of the program or application. You would need at least two people. However, the number of people would vary depending on the size of the application and the program.

Some of the key pain points were addressed by the applications that were developed, primarily in terms of user satisfaction and implementing them in the business process. 

The return on investment was not a consumer web application where the product would be rolled out to the general public and revenue would be generated. 

It was designed primarily for internal business users, With the main goal of the application being to improve business processes and bring all offline processes online to have a digital footprint of those business processes, making tracking easier.

I am not aware of the cost. But, considering the licenses, user licenses, and infrastructure, I'd guess around a million USD.

I would rate Pega BPM an eight out of ten.

I believe they simplify the application development. It is still complex. The learning is not easy, it takes time compared to other products on the market. For the learning curve, I would reduce two points.

If you search on Google, basically you will see a lot of use cases that you can implement. Wherever you have a kind of automation, a case management, a kind of logic, a kind of an exhaustive process flow where a particular task will flow from one group to another. In all those situations, Pega can be a very good fit. Nowadays, Pega provides machine learning, automation intelligence, DevOps, et cetera. Whatever is as per market standard, those are there in Pega.

Pega has lots of industry solutions as well which are targeted for specific industries such as financial, healthcare, or insurance. The product helps you to build faster. 

Pega is a niche product and any workflow management kind of use case, or maybe automation kind of use case can be implemented using Pega. The only thing that you need, is the right skillset. Pega is a very customizable product. You need to know the product very well to implement it to a proper standard. 

Pega has been on the market for quite a long time. I'm working with Pega for the last 15 years and they always have a lot of new features.

The way it is adapting to new changes is quite useful. The way it is changing itself to survive in the industry with other BPM tools and being competitive every time. 

With Pega you can deliver some things pretty quickly. You can deliver a prototype for what Pega calls a Minimum Viable Product or Minimum Lovable Project, MLP, very, very fast. 

The solution is stable.

You can scale the solution if you size it right at the outset.

It's very customizable.

You can use it for many industries.

There are lots of very useful features. They're constantly adding more items to the product.

There are lots of great automation and machine learning aspects.

The initial setup can take a while. You need to have the right people in place to handle it effectively. 

It can be pretty expensive and is better for larger enterprises. 

I've been working with Pega probably for the last 15 years.

It's a stable solution. 

The scalability is pretty good. Whenever we work in Pega, we propose this product to any customer based on their needs, how many tech resources they have, how many concurrent resources there will be, what their daily inbound volume is, et cetera. Based on that, we get the hardware sizing from Pega. If you do the right kind of estimation and start with the proper infrastructure, you will be able to basically ensure robustness, high availability, almost zero downtime, and everything can be shipped. 

Pega tech support is there technically and they do help us a lot. In the recent past, we have seen a little bit of trouble here and there, where tech support is taking a long time to fix some issues. Usually, if we route Pega with proper channels, then we can manage good support. 

They have a good tech support process and they also provide a good academy resource. Someone new to Pega can get a lot of documentation and material to learn the product.

I am from a Pega background and I do not know much about other competitive products in the market, so my feedback or whatever I'm giving, that is maybe a bit biased as I have been working with Pega only.

The initial setup takes time. You have to gather people with the right skills. If you have that then it won't take that much time at all. Basically, the main selling point of Pega is it can reduce your entire timeline drastically. The constraint is you need to have the right kind of people. 

Pega is a huge tool, and honestly speaking, nowadays, there are a lot of sections in Pega where there is no single user who knows the entire feature set. It's a big and complicated product. You need to have the right blend of team members to set up, to have an easy initial setup. In those instances, it might take six to eight weeks. After that, I have seen people delivering some base prototypes and a walking model in a few weeks.

We help our clients set up the solution.

Nowadays, standard open affairs configuration is there. If you ask me how much time it'll take to build it, it's maybe a few hours or maybe two to three days. When we talk about the entire project, we need to take care of a lot of things, not just the build part. Usually, there are integrations necessary and we have to have a lot of testing in place to manage different combinations, load testing, performance testing, and security testing. Most of the time clients ask for all these things. That adds to the setup timeline, however, the build is not included in that constantly changing time.

This is something every enterprise has to handle separately with Pega. As a vendor, we are not supposed to comment on pricing.

We use both cloud and on-premises deployments. In earlier days, Pega used to support only on-premises. Nowadays, it's supporting the cloud as well.

I definitely do recommend the product. Pega is a competitive product if it's not a small enterprise. Small companies usually avoid this product as there are a lot of open source products that are less costly there in the market. 

Based on the features I can recommend it. 

I'd rate the solution nine out of ten.

I use Pega BPM to automate business use cases and integrate third-party application data into applications designed on Pega Platform.

Previously, our HR onboarding application ran in silos, so everything was happening separately. Pega BPM allowed us to consolidate all the data in one place, from which we could define our business workflow. This means that we have the entire flow running in one application from start to end with the help of third-party application data.

Pega BPM's most valuable features are case management, integration, the convenience of using REST APIs, and the ease of changing things at the UI level.

Pega BPM could be improved by including token-based authentication and extending its integration options. In the next release, Pega should live up to their claim to be low-code/no-code and make their platform more simple and UI-based.

I've been using Pega BPM for almost two years.

Pega BPM is stable.

Pega BPM is scalable.

The initial setup wasn't complex, but you have to define your class structure and architecture properly. Deployment took around a month. Also, Pega says BPM is low-code/no-code, but that's not true - you need intervention as you can't design the application without some knowledge about it.

We used an in-house team.

Pega is expensive. If your company has a good amount of money to spend, go for Pega as it has many things readily available out of the box. But if you're looking to save money, you may be better going for an open-source platform.

I also evaluated WaveMaker, but Pega has features that aren't available on WaveMaker.

Pega BPM is a very good tool if you have the budget to spend on it and you need to automate any business process wherein you get the data from multiple sources. I would rate Pega BPM as six out of ten.

We support clients who use this solution. We have had a client who used Pega in London at their headquarters and in their data center operations in India. They installed Pega in the UK, but they wanted to run the applications from the data center in India. They wanted to give access to all the business users across the world in more than 12 different countries. 

The client used SAP for their business system, Pega for the business process management and UiPath for automation.

The robotic process automation has increased the confidence of business users. 

The cost of licensing could be improved.

I have been using this solution for 5 years. 

There are multiple components within support. This first component is the functional support from an BPM perspective that is module related. The second component is technical support for when clients want any customization of their BPM product along with any workflows.

The initial setup is straightforward. For an implementation project, we usually have a team of 10 BPM developers along with the BPM technical architect and the BPM technical lead. The implementation projects runs over 18 to 20 weeks, while an upgrade project, requires eight to 10 people over 12 to 16 weeks. If it is a support project, we use a team of six people over a period of one year.

Normally, we don't own the licenses. Customers have their own licenses and we work on their environment.

As an IT services company, we provide different solution options to customers. We offer SAP BPM, Pega, IBM BPM and Oracle BPM. The first and foremost consideration is that the customer needs to be comfortable with the solution that we offer. 

There is a feature to accelerate the development so that business analysts can directly create their user stories and assign the task to the developers. It's called DCO.

Pega is claiming they're into low code but as per Gartner Magic Quadrant, Pega is not there now. Appian, OutSystems, Mendix, Salesforce, and Microsoft Power Platform are the major leaders in the market as low-code platforms as per Gartner Magic Quadrant. Pega has to improve if they would like to gain their position in the low-code space. They would have to improve major functionalities that these low-code vendors and low-code platforms have like their mobile compatibility. A citizen developer can easily make B2C mobile apps.

Pega has to come up with a lot of improvements in these low-code areas for the citizen developers who can easily create mobile apps with minimal coding or no coding. With other competitors like Appian, OutSystems, and Mendix, you can do it using visual modeling.

The price could also be improved.

I have been working with Pega for about six years as a solution architect.

Pega is a stable product. If you're solving a business problem for case management, Pega is the best for case management solution, but the product architecture is entirely different. It's rule based. It's not popular for UI or UX management.

Pega's technical support is not as friendly as Appian. 

I would rate Appian higher than Pega. The price of Pega is a bit higher than Appian and the software isn't as friendly.

The price could be lower.

I would rate this solution 8 out of 10.

The rule engines work well.

It is a stable product.

The solution could be more scalable. 

It has some DevOps limitations.

The product could be more robust and faster compared to what they have right now.

Pega is also stable. It is also an old product. They have DevOps limitations if we compare it with Appian. That said, from the tool perspective, Pega is stable and reliable.

It is not as scalable, as, for example, Appian. However, I don't have extensive knowledge and therefore can't speak widely on the scaling process. 

I've never contacted technical support. I'm not sure if they are helpful and responsive. I've never talked directly with them. 

I've also used Appian.

I have limited experience with Pega. I don't have extensive knowledge about the Pega, however, there are a few things, which may be the reason to prefer Appian over the Pega. The engines, the rule engines, internally, on Appian or Pega work. However, in terms of how they process your request Appian is more scalable and more robust.

The setup is also good. It also provides the cloud, so it's not an issue from that perspective. I did not use it very extensively, however, they do have a cloud, so it's fine in terms of implementation.

I can't speak about the exact costs. I don't deal with that aspect of the solution. 

I don't have that much experience on the Pega, however, from what I have experienced, there's a little bit more that can be offered. I'd rate it a six out of ten.