Pega Platform Reviews

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. 

Regarding the primary use cases of Pega BPM, I can say that my company deals with multiple domains, like the government sector, banking, financial institutions, telecom, health care, and multiple domains that require Pega BPM.

The most valuable feature of the solution, I believe, is case management, which sets it apart from the rest of the solutions in the market.

I believe that Pega's strategy when it comes to the UX part is not that great currently as compared to the other emerging BPM tools in the market. I look forward to seeing the UX part of the solution improved in a much better manner.

I have been using Pega BPM for nine and a half years. My company's customers use the solution. My company has a partnership with Pega.

It is a stable solution.

It is a scalable solution.

The solution's technical support is good. My company is able to acquire the required assistance from the solution's technical support team, and they also provide consultancy services. I rate the technical support a nine out of ten.

Positive

I wouldn't say that I have used any other solutions previously, but I was trained to use TIBCO, a low-code platform.

The initial setup of Pega BPM is neither easy nor complex, so it falls somewhere in the middle. Pega has provided options for automation for the setup phase, but still, its setup phase is not as direct as some of the other tools in the market.

Pega BPM has set a path for its setup phase, wherein you need to go ahead with Helm chart automation since Pega is a very wide solution, and infrastructures can differ for different companies. Pega doesn't offer something specific, like Terraform. In other technologies, the product gets installed with one click or just a few clicks, but with Pega, a person has to work a lot on the infrastructure part as well.

The solution is deployed on the cloud and on-premises. My company provides the solution on Pega Cloud, technology-specific clouds, client-specific clouds, or on-premises.

The complete implementation process for Pega BPM would take a minimum of two to three days, prioritizing the infrastructure first and then the product.

Two people, one from the infrastructure end and one from the product end, which is the technical support person from Pega, would be needed to complete the deployment of the product. There is also the need to have Pega's partner who does the installation, making him or her the third person involved in the deployment.

The price of Pega BPM falls on the higher side of the spectrum if I were to compare it with other solutions in the market. What sets Pega BPM apart from other solutions in the market is that it has many features, including the use of AI and modern gen AI, which currently is not something you can experience in any other tools in the market. The aforementioned details contribute to making Pega BPM a leader in the market.

I would say the people who have realistic business process management kinds of use cases can go ahead and purchase Pega BPM blindfolded since it serves as a great case management tool, better than any other tool in the market. Pega BPM provides great visibility to its users, especially when you are involved in designing, where it will show you the number of stages, steps, processes, data, and even the people or parties who were involved, making it a great tool for case management. Presently, Pega BPM is heading towards the inclusion of more AI, owing to which it can be considered as one of the leaders in the market. The CRM part of the solution is one of its key selling features.

Though the solution's UX is good for developers, when you have to deliver the product to the customer, you don't get too many options for customization that can help you create an appealing view.

I rate the overall solution an eight and a half to nine 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.

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.

I mainly use Pega BPM to look at conversations and try to create a better experience for the customer.

Pega BPM's most valuable feature is the use of CDX to solve problems.

In the next release, Pega should include process mining.

I've been working with Pega BPM for three years.

Pega BPM is stable - I haven't seen any glitches because of usage or anything like that.

Pega BPM is scalable.

Pega's technical support could be better.

Neutral

The initial setup was complex.

It was easy to learn, adapt, and go through Pega BPM's low code builders. I would give Pega BPM a rating of nine out of ten.

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.

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.