Pega Platform Reviews

Application development is very rapid. A lot of code gets reused while building the applications, which is something we highly appreciate. 

People are also very happy with the robotic process automation and the dashboards. They are very good.

Its implementation in the public sector was a bit complex. 

In terms of features, I have not come across any limitations in the last four or five years. I'm on the sales side. I work with customers, and my role involves reading a customer's mind and providing the best solution so that all pain areas are addressed. Pega has got very good features and tools. I didn't come across any limitation where a customer wanted something, and we were not able to provide that. Generally, whatever a customer demands, we are able to meet that demand. 

We have been using Pega since 2017 or 2018. It has been about four or five years.

Its stability is good.

I have not come across any scalability issues. The government customer has perpetual licenses. We are very populous in nature, and people come from the web as well from the mobile. They are able to process all those requests. I've not come across any issues.

Their support has been excellent because the person who heads the Pega practice is very senior. He was the sixth employee of Pega in the UK. He has an excellent relationship with the CEO, Mark Allison. Mark has been to our development centers because we have been expanding in the last three or four years. Our focus is banks. So, he has been visiting us. 

As an organization also, there has been tremendous support from Pega. We are a small but growing organization. We are not very big, but we are competing with the big brothers in the industry who have been there for over decades.

The finance part that people were doing was not too difficult. It was straightforward. However, when we implemented it in the public sector, it was a bit complex because of the disparities in the data structures and the maturity of the customer. They had different ERPs. So, it was a bit tough, but they appreciated it. We are a Commonwealth country. So, whatever works in India would work in any Commonwealth country. We have an education department here, and there are two categories: higher education and technical education. Based on merit and a lot of other parameters, such as caste, people have to be given subsidies, grants, and aid, which change with the political system. A new leader can announce that he wants to give laptops to all standard 12 students who have scored 90% marks. So, all such rules can be built very quickly. The SLA is for about five working days. We have to complete a new request in five working days. Most of the customers here want parallel development. Normally, we have six to eight teams working. Generally, we give a new Pega solution in about 100 days. After a solution is rolled out, we have a separate team with about 10 people, and they cater to 10 and 15 customers.

There is a team that looks into its cost. When it comes to licenses, we don't get involved with selling the licenses. We insist that Pega sells the licenses directly to the customer. This is the model we work with. We make money only through our implementation.

The licensing is on a yearly basis. Because of our special relationship, all the training certifications are free of cost. All our employees can do Pega certifications at zero cost. It is all on Pega.

We have a small team based out of London, UK. We have Pega and Appian. We don't have anything else. It is a very small team, and we only cater to financial institutions. We are trying to acquire a few Pega customers in the Middle East from the UK.

I am based out of India, Bangalore, and in India, Pega is just coming in. There are not many installations in the government as well as enterprise sectors. There is a private sector bank that is trying to move to BPM. They have not yet made a decision about what they want to procure, but they have been talking to Appian and Pega teams.

I would rate it a 10 out of 10. We have had a beautiful experience with them.

We use the solution basically to run any custom process that the client wants to have, or needs to run their business on. For example, the approval process or any kind of business process that can be run using the Pega Platform.

It's low code. That is very useful. A business value architect will have zero coding to do, and he can create a business flow on top of that. The technical developer can handle further things. 

Apart from that, the kind of APIs that they support is also very nice. It also has a lot of APIs out of the box. It can directly connect to Fitbit, it can directly connect to Google Maps, et cetera. That API exposure is also a good thing. They are very easy and very reliable to use, the APIs.

The setup was simple. 

It's a stable solution.

The solution has very helpful technical support.

It can scale pretty well.

A few things I would like them to improve include, first of all, that they don't have any open-source learning platform. To learn Pega, you need to be a partner. If someone just wants to learn Pega for the sake of learning, they won't be able to do so as they don't give access to that.

I would like to have an integrated process mining capability inside Pega. It will be like an entire digital transformation thing then. You don't need two or three sources. Similar to Signavio. Signavio runs BPM, it does modeling, and it is having process mining as well. In Pega, we have modeling, we have RPA, and we have BPM, however, we don't have process mining right now.

I've been using the solution for three years.

It's quite stable. This means we haven't encountered any issues. And even if there are issues, their support is very responsive.

The product is quite scalable as it's a low-code platform. 

The solution adjusts well to different devices. They have this adaptation that if you open it on a tablet, then the screen will adjust accordingly. If you open it on a PC, the screen adjusts it accordingly in Pega. Android as well.

There are more than 25,000 people on the solution.

We've worked with technical support in the past. Whenever there's downtime or whenever something is not working, we need to get in touch with the Pega technical team.

Neutral

I'm also aware of Appian. Even if Pega says that it's a low-code platform, when I compare it to Appian, Appian is more low code when compared to Pega.

The initial setup is very simple and straightforward. 

You need to pay for licensing. It was quite expensive. I'd rate it four and a half out of five in terms of how expensive it is. 

My organization is a service provider for Pega. We're implementation partners. If we use it completely depends on what the client wants and needs.

If you are using it for the first time, you probably should have a consulted implementation partner as well. That said, it is easy to use. It shouldn't be a problem. It's very flexible.

I'd rate the solution eight out of ten. We generally don't encounter any issues as far as Pega is concerned. Whenever there's an issue, there's a quick resolution. 

PegaRULES is used more for business process management. Perhaps in a bank or any other organization. If you want to automate anything, you may require a tool, which is, simply building the same thing in Java. 

People choose Pega because it's a flow-oriented tool that is already predefined and you can plug and play.

I can say that less development effort is required for developers, allowing them to focus on business problems rather than technical issues. It corresponds to every BPM, so it serves the same function.

Pega also sells the same so that you can integrate with legacy applications or with different applications that may or may not have AP capability. You can use UiPath in between with PegaRULES integration.

There are a lot of features, which most people prefer.

Case Management is the most valuable feature of PegaRULES, which is not found in other BPM tools.

Containerization should be improved in relation to Pega because Camunda is deployable in the containerization deployment process. Pega is trying to move in that direction, but that will have to improve slightly.

I have been using PegaRULES for 15 years.

Pega has multiple models, and I believe a few teams are cloud-based. Our organization is mostly moving to the cloud, but not entirely. However, we use on-premises deployment.

PegaRULES is extremely stable. It is still dependent on developers. 

Initially, I believe we will require the services of architects to set up the cloud structure and design. Everything must be thoroughly reviewed. Developers will need to follow suit. In terms of stability, I would say it's a solid application. How you use it is determined by how you built it. You must exercise caution when developing the application. If teams attempt to build the Pega without the necessary experience, performance issues and other issues may arise. That design must be correct, and it must be reviewed and monitored. I believe it will be able to stabilize this application.

It can also be scaled up. It is determined by the scope of the data, but it can be scaled up to meet the requirements of the application. It's in hardware and adding hardware to an extra. It will follow the data availability features. Pega will support the ability of Java applications to scale up based on stability. I don't know much about that particular hardware side, but I can say that it can scale up to meet the needs of the user. It is dependent on the application or how large these applications are. It can be scaled to any size.

The number of users is dependent on the project. There are large projects that may involve 10,000 or more users. In a few applications, you may see only 1,000 or 500 users or something along those lines. It is dependent on the application and who is using it.

I have contacted technical support, and they are very good.

The technical support for Pega is excellent. They were able to assist us and even guide us if we had any issues. If you contact Pega technical support, we'll find a solution right away.

I would rate them a five out of five.

Positive

We mostly use Pega products.

Pega provides documentation. The same documentation can be followed during their own deployment process.

In my opinion, it's not complicated in terms of deployment; but it depends on how your applications will be deployed. It's the same method. 

Pega will also assist you in this regard. It simplifies the deployment process and makes it easier to set up others.

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

If everything works and is ready, the initial setup can be deployed in half a day.

In terms of the price, if I were to compare Pega to other tools, it would be more expensive, but it would also provide you with the same features.

If there are applications that scale up to the enterprise level, we would go with Pega, and if it's a smaller application with a smaller workflow, or if they can't afford to invest that much money, they'll go with less expensive tools such as Appian. Camunda is open source, we have people working on it.

The licensing fees are not that much.

I would rate PegaRULES an eight out of ten.

Our use case of this solution is for clinical case management. I'm the senior vice president of the company and we are customers and end users of Pega BPM. 

The solution has assisted us by automating our workflow. It supports the process management of medication therapy engagements with patients. 

We appreciate that this solution supports the size and scale that we need.

This is a very expensive product and there is a lack of availability of the Pega skill sets, the resources. 

I've been using this solution for 10 years. 

The solution is stable. 

The solution is scalable, we have around 1,000 users and don't have any plans to increase that number. 

We deployed ourselves and I don't recall any issues. The solution is not maintenance heavy and we have a few people responsible for upkeep. 

Licensing costs are very high. 

It's important to check all options and ascertain that this is the appropriate solution for you. There are other features that products like Camunda provide,   but as you need to scale and get more sophisticated in your process management, Pega becomes a better option.

I rate this solution eight out of 10. 

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.

Pega is an Intelligent Automation Platform that has evolved from a BPM perspective. This allows teams using this solution to address complexities without having deep knowledge in a specific development area.

One of the areas of this solution that could be improved would be to improve the low code features of the application itself. We would also like to use the same platform to build any application, even if it is not necessarily defined as a functionality needed by a BPM.

The RPA tool within this solution needs further enhancement to compete with other RPA tools in the market. They are focusing more on the overall platform rather than working on the RPA. Document AI tools could be an added functionality, for example. Alternatively, customers will need to purchase another RPA tool to complement the whole solution if they have very advanced RPA needs across their business.

I have used this solution for one year. 

This is a stable solution. 

This is a scalable solution. 

The technical support is good.

The initial setup was not that complex but also was not that simple.

We often recommend this solution to our customers. It is a wonderful solution. There are not many professionals working with this tool which is important to note.

If the core need of a customer is for BPM and automation, this is a suitable solution. If their needs exceed a BPM solution, such as modernizing different kinds of applications, there may be other suitable solutions. 

This is a good solution from a technical perspective and is based on a very reliable and scalable platform.

I would rate this solution a nine out of ten. 

We have two different projects right now using Pega BPM. In one we are doing a migration of applications regarding claims, and the process requires orchestration between different providers that this company needs to organize the work. When you have a claim and you need a repair for something, we need to organize the work that we send to the provider. One, for example, is doing water claims. Another one could be about car claims. These are our main processes right now for Pega BPM. 

The other project is regarding onboarding customers in a bank. We use Pega to orchestrate the different aspects we need to complete the onboarding for our customer.

One project is on-premise and another one is on cloud, but we started using the Pega cloud and right now we are migrating to Azure Cloud,

Yes it has improved the KPIs. For example, in the insurance project, the time required to complete the project with Appian was around a month and now with Pega it is around two weeks. We still have a lot that is manual, but we reduced the time of the process.

The best part of Pega, for me, is that they let you reuse a lot of the aspects in the product.

The main problem with Pega is that it is quite complex, so it is very difficult for the developer to learn. Sometimes it is like a black box where you can't develop other things. When you try to modify something on the product it is quite difficult. Also, when new people try to learn how to develop in Pega, it is quite difficult to learn, and it's a big product. I think that is the problem.

Maybe they could try to make an easier implementation. I don't know how. Maybe with more information on the Pega platform, in the Pega academy, or modifying the application to make it easier to implement. 

I started using Pega BPM 11 years ago.

Pega BPM is stable.

Pega BPM is more scalable than Appian. We can have more processes running, more data in the server, and the performance is better.

Both of our projects are in production right now, but in one of them the customer will require around 3,000 users. With the other project it will be around 300 people.

Right now, there are two or three people running this kind of project, so we will need more people for that.

The plan for Pega in both projects is to continue for around five years more - so we have a lot of work there.

We don't have too many problems. It's true that we have more ticket service requests with Pega, but they answer quickly, so I think that is good.

In one of our projects, we previously used an application called .NET by Microsoft and the solution was so slow. Well, I think it was created 20 years ago so the modification on that application was too slow because the code is much longer and you have to read more lines of code so it was not easy to modify the processes on that application. It was for that reason that we tended towards Pega, looking for more agility on the modifications and giving control to the business people to modify different business rules for themselves.

The initial setup is complex.

When you are doing a project in Pega, it is more complex than the processes that you are normally going to implement. When the product is complex to learn it's more complex to develop.

The deployment time is not too much. It is about the same as with Appian when you have the configuration down, no more than one or two hours.

Normally when we use Pega we are thinking about a more global application that you can use in different countries or for different areas.

It requires a Pega architect from the company.

The pricing with Pega BPM is a huge problem because it is quite expensive for the Spanish customers. It is higher than other BPMs.

My advice to anyone considering Pega BPM is that they have to think about that they want to do on it because not everything is possible. It is similar to Appian, so really think what you want do you in Pega. If you are thinking about moving an application towards innovation on Pega, it's not a big solution to do it. If you're thinking about something more, it's a good product. Don't spend money on that because Pega is more expensive than other products.

The main lessons regarding Pega are that you need people who know how to use it because it is a complex product. If you create the application from the beginning, you are going to need a lead system architect to do it, because if you don't do it correctly, the use and the good points that Pega has could be an issue for you. The main point here is that you need people who know Pega really well in your team.

As a product I have to say that I think Pega BPM is the best right now, and the only problem that we have with Pega is the people. So if I focus only on the product, on a scale of one to ten, I have to say Pega is a nine.

The product is so good. The only problem is that the people who work on it need more knowledge.

The workflows are the most valuable features, particularly for us, because we were attempting to automate processes by utilizing workflows to provide a hands-off comparison between the bot and the human.

Also, the out-of-the-box reporting, visibility, and dashboards are extremely useful. 

There was a lot of room for improvement on the RPA front because the product was still in its journey for more than one year. The product was still in its early stages of development. We spoke with the Pega team and provided our feedback.

On the BPM front, I believe it is pretty standard and an industry leader. 

We have experienced a few technical challenges, particularly triggering the workflow through file drops and accessing files. Those difficulties are more of a cloud versus on-premises issue because everything was on the cloud, and they were unable to retrieve files from on-premises folders. As a result, we had to resort to workarounds.

I believe they could work on more integration of their RPA and BPM so that it becomes seamless for anyone, and then it becomes easier for a human versus machine interaction using the same BPM. They said at the time that it's on their roadmap and should be coming soon if it hasn't already. But those are the things that, in my opinion, would make a better BPM, where it would function as an enterprise orchestration layer, collaborating with humans and bots in the same way and delivering the business process.

We completed a couple of BPM projects using Pega BPM.

I have been working with Pega BPM on and off for the last two years, and I have completed two BPM implementations in the last three.

It's a scalable product. There are no challenges with the scalability of Pega BPM.

Technical support was good. Especially for us, their product team was with us, as was their support team, and all of these workarounds were only possible with their assistance.

I worked on Newgen BPM two years ago.

We work mostly with BPM but we did a PoC on RPA. The RPA was unable to work.

The initial setup is simple because it is in the cloud. We haven't spent much time setting it up, it was up and running for a few weeks.

In terms of business flows, our implementations were not overly complex. We were able to launch it in an Agile mode, and we were able to deliver, in two or three sprints spanning four months. Every four to five weeks, we were able to release small flows to enable certain business functionality.

Pricing is a little on the high side. One of the challenges where a certain lower level of cases was unable to justify the cost. If your process is not that complex, and it is very simple, then the implementation timeline is obviously short, but licensing becomes a little costly, and it sometimes does not cross the business use case. 

The benefits you receive are not worth the price. 

They should have a solid foundation of business processes in place before embarking on this journey. If the case is small or the process is not complex, they should use a smaller and simpler BPMS. The primary reason is the cost. However, if they are considering it at the enterprise level or for a more complicated process, Pega is, in my opinion, the best option.

I would rate Pega BPM an eight out of ten.

For an upcoming project, my manager told us to look at all the different capabilities between the Pega, Appian, and the Camunda. We don't know the use case yet. We need to know the use case, however, at this point, we are just exploring different tools, BPM tools.

The integration is good. It can be capable of different integrations. 

There is a Pega Decision Hub, which is just a text-based analytical site. Based upon the text-based analytics and it can decide and trigger a case.

There are a lot of new features in Pega that are great.

I like case management in Pega. For the case management applications, so it's really fast to develop and it can scale and be extended based upon the business requirements.

The initial setup is pretty straightforward. 

The documentation and training available are great.

Pega is coming out with Pega Express, which is kind of a low-code development platform. The business rules can be built in a Pega Express Portal, which is more specifically built for business users and not technical users. That way, even non-technical people are able to build their own business processes easily.

The local development approach is good in Pega, however, cost-wise, it's getting expensive. That needs to be addressed.  

With Camunda, containerization is the most helpful feature. It can containerize and it can have its own deployment process. Pega may be adding that feature in a future release, however, right now, that's lacking and needs to be addressed.

I'd like to see Pega support microservices architecture, which it doesn't do right now.

We have been using the solution for more than six years.

The scalability is excellent. It can scale as much as you need it to. It's one of the great aspects of the product.

I've never directly contacted technical support. I can't speak to how helpful or responsive they are. We have our own internal team that can troubleshoot.  

That said, we used to connect with Pega on issues and it's my understanding that support tickets can be addressed very quickly. Support-wise it's very extensive. 

I also trained in Appian. 

The initial setup is straightforward. There is no complexity. There is documentation around the installation process and upgrade process as well. Pega will also provide you with good training materials in the Pega Express Portal, which is helpful for teams who are planning for new developments. That way, they can learn easily and understand everything.

It's a great product, Pega, however, cost-wise, it is a little expensive compared to other BPM tools. That's where I feel that they can improve.

Now, we are exploring other software, like Camunda. We just want to see the different designs or decide which tool is better for our application.

We are a customer and an end-user.

We have been using Pega for more than six years, and at this point, we also want to just explore the other BPM tools. It's kind of for considering cost efficiency also. We are looking at the cost of the development effort or the scalability of the tool. While I like Pega, I'm just exploring the other BPM tools with respect to Pega.

While it depends on the application you are using, if you're planning for an enterprise application that can interact with different applications, Pega would be a good option.

Sometimes if you have a smaller workflow, for example, if you're just introducing a smaller workflow in an existing application and you just want to leverage only that workflow-related feature, you don't need Pega. You can just have any workflow tool, like Camunda or Appian. Cost-wise, Pega may cost you more.

If you're planning to leverage all the features in Pega, like case management and low-code, no-code and RPA, robotic process automation, and other high level or case management, if you are planning to leverage all these different kinds of features that are available in Pega, just go with Pega. And if you're just planning to leverage only a kind of workflow, you don't need to go with Pega. You can just go with other BP flows or BPM process models like Camunda. 

There are a lot of features that you can explore in fault tolerance and error handling, exception handling, et cetera. There are other items as well if you're in the development stage, and something like Page will likely be helpful. I don't know of other tools that will support anything to that extent.

There are still some limitations in the solution. I'd rate it at an eight out of ten, as there are still some improvements that can be made. 

The solution can be used to quickly manage and monitor processes in your organization. 

I have found the solution to be flexible and they provide good support. 

In general, we use web services to integrate this solution with our other tools. It is the main approach we use with this solution and it integrates with all tools that we need. If you want to integrate with other solutions such ThreatFire or similar, it is possible as well. 

The previous versions had good training documents but the updated versions need to improve the documentation.

I have been using the solution for approximately five years.

The solution is stable.

We have a customer that has over 6,000 users using the solution.

The solution provides very good support. They have the experience, knowledge, and are always helpful. 

I have used previously used Camunda, jBPM, and IBM solutions.

The version for private use on your workstation is easy to install. However, if you want to prepare a platform, it is not easy. All good solutions are not easy to install and tend to be complex and because of this, I would not say this solution is any more complex than any other good solution.

The amount of technical team needed depends on the project. For small implementations, we use one to two people and for big projects, we can have over 30 developers.

The solution could be less expensive according to my customers. However, I think the price of the solution is fair.

This solution is one of the best tools on the market right now. I would recommend it to others.

I rate Pega BPM a ten out of ten.