Pega Platform Reviews

The company has a strategic partnership with Pega. I was the general sales manager. 

This is a customizable product. It's low code and can be restored quickly if needed. 

The solution is expensive and it put many of our customers off. After a while, the company was no longer prepared to work directly with customers which created problems. 

I recently stopped using this solution because I changed jobs but I had used it for 18 months. 

The product is stable. 

The technical support is very good. 

Positive

We helped our customers implement this solution because the company had its own in-house dedicated team. 

This product is quite expensive. 

This product is suitable for pretty much any size of organization. I rate this solution eight out of 10. 

Our primary use case for this solution is for case management systems.

This product makes it easier to connect to multiple applications because integration through API or web services is very easy. That is one thing that has helped. The development time is very quick.

The most valuable features are case management and integration services.

The unit testing needs to improve, as well as the user interface.

In coming releases, I would like to see something in Artificial Intelligence (AI) and Machine Learning (ML).

This solution is quite stable. We deploy applications every month, generally to production, so we see that the product is quite stable, with no complexities. Overall, we're happy with the stability.

The scalability is good. In some areas, we had some trouble, but I think it was the way it was designed and not the product itself. So, we feel that it is good.

The technical support is quite good. They come back very soon, so we're happy with the support.

We did not use another solution prior to this one, so we started with Pega.

The initial setup for this solution is straightforward and not very complex.

The time for deployment depends on the complexity of the application.

We handled the implementation in-house and have people with experience in Pega.

I cannot share the financial details, but what I can see is that the users are happy because they get the solutions faster. That, for me, is a big benefit because I can show my product to the customer quicker than with any other solution. It makes me more efficient.

The licensing fees are based on the number of users.

I don't think that we evaluated other solutions. We were happy with what the tool was offering and chose it.

This product is pretty easy to work with. Sometimes you need experts, and it can be difficult to find Pega experts. Otherwise, it's a good tool to work with.

I would rate this solution an eight out of ten.

We primarily use the solution anywhere we have to manage processes. I have a large portfolio of clients in financial, health care, life sciences, etc., and I use the solution for all of them.

Pega is currently number one in BPM and case management solutions, according to Gartner and Forrester. I like that it’s mostly a no-code platform. It’s also more of an enterprise-level solution. It looks like a front end stack. There are dozens of applications that are just moored to each other. However, Pega feels like one solution.

The interface is quite simple and easy to use, even for beginners.

Pega currently is trying to add chatbots to their systems, and it's still quite immature. This part definitely needs to be improved. The RPA also needs improvement. Pega has its own RPA, via an acquisition a couple of years ago. They bought OpenSpan and tried to rewrite it to Pega's platform. It still has some gaps. For example, they have no machine learning. If they want to be more mature in the market, they probably need to consider working on improving that.

The solution is stable across all deployment models.

It's very simple to scale the solution, especially if it is on the cloud. It's your own environment. You can just make your own limitations as to how fast you want to create your own new environments. Right now, we are handling 20,000 users.

The initial setup is quite simple. How long deployment takes depends on what you want to implement. It can be as little as 50 minutes if it's something very easy. It's like moving bricks. You are not typing any code, rather you are creating processes. When you're developing it, the length of time needed depends on how many bricks or processes you have to move, or create, so to speak.

In terms of how many people you need to maintain the solution, It depends on what type of support was chosen. It can be your own maintenance, or it can be maintenance from other suppliers or the vendor. It also depends on the number of applications you have as well.

We are using both public and private cloud and on-premises deployment solutions. We're using product versions seven and eight and have previously used product version six.

We’re a Pega partner.

I would rate the solution ten out of ten.

My primary use case is for process modeling.

There are several areas for improvement with this product. The performance of the application is very slow, the UI needs improvement, and the architecture needs to be simplified. In addition, it's impossible to know what's going on behind the scenes of this solution, and there's no tech support or useful documentation, so I have been forced to do my own troubleshooting.

I have been using this solution for two years.

The stability's ok once the solution is set up properly.

The solution is scalable in terms of load but not operation-wide.

The technical support has been disappointing - we don't get the support we need from it.

The initial setup was pretty complex.

The pricing is good.

Before choosing, I evaluated Colfax, Oracle, and IBM.

The platform as a whole is very rich - you can do a lot of things with it with minimum time and cost. I would recommend Pega as a BPM solution but make sure that your contract states you will receive support, otherwise you may not get any. I would rate this solution as seven out of ten.

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

The solution would benefit from more integration capabilities.

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

I've been using the solution for 1.5 years.

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

The scalability of the solution is very good.

We've never contacted technical support.

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

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

We handled the implementation ourselves.

We use the cloud deployment model.

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

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

We primarily use the solution in claims for our clients in the insurance industry.

The visualization of the business process and the collaboration aspects of the solution are its most valuable features.

The solution is more user-friendly than its competition, and more visual. Its level of inference is much lower as well.

The solution needs to invest more in its technology. For public and private clouds, for example, the development environment is slow. Saving events should take one to two seconds, max, and because you are making changes often, the slowness cuts down on productivity because we have to wait for things to save before continuing. 

The UI could be slightly improved.

The solution is stable.

The solution is scalable.

The technical support has been very good. They answer our questions in a straightforward manner.

The initial setup can be a bit complex because you don't just deploy the solution out of the box. It has many possibilities and when you are implementing the solution you are setting specific features to align with the requirements of the business. In POCs and real production environments as well you need to think about all of the different aspects and this makes the setup complex.

We handled the implementation ourselves.

We're a Pega partner.

I'd suggest those considering implementing the solution start small and maybe do a POC. That will give you a sense of what the solution would look like in production.

I'd rate the solution eight out of ten,

Fast prototyping.

Nothing compares with custom development.

• UX
• Business specific functionality

Three years.

Yes. Product failed to start periodically. No tolerance to DB outages.

We did not have significant load, but one physical server instance was able to serve around 100 concurrent users.

Four out of 10. They try to push all issues to the implementation team.

Customer decision.

Straightforward.

Licensing is expensive. You need to wisely select between per user and per case.

Appian BPM and Activiti BPM.

Have a strong skilled architect.

It is a multi-tenant offering for developing applications. We have its latest version.

Generically, at the moment, it can take things that were non-functioning processes and crossing stovepipes and make them function.

I have found a lot of features valuable. The ability to define processes, build reports, and get insights or analytics on data is most valuable. It is a powerful platform.

The way the IDE works with the chatbox and the taxonomy imports could be a little smoother.

There should be quicker approvals for CDH. It is a bureaucratic approval process to be able to get those particular licenses.

I have been using this solution for two and a half years.

It is stable. Like everything, it depends on the quality of the knowledge of the people who are using it.

I like it. It allows for a lot of multi-tenancy.

In terms of usage, it is in its initial use areas, but it is rapidly being adopted.

I have interacted with them. Our overall experience is positive. They have some good folks there. Occasionally, their system doesn't realize the urgency of a problem if the problem isn't in production. If your problem isn't currently causing production failures, the turnaround time can be slower than expected.

We don't use Pega exclusively. We've got other stuff in there. There are some things for which one solution is good, and for another set of things, another one fits very well.  It just depends on the application, the tendency, and the purpose.

We brought in experts. Our experience with them was positive.

The advice that I would give is that when spinning, think about if you're setting up a private one. You should also think about your tenant or your organizational control structure for multi-tenancy so that you can have a mix of licenses for tenants while not overly complicating and having to maintain tons of different work control layers. 

Before you start up an app, take a look, run the wizards, and see what you can reuse from the structure. Its wizards are very good to use when starting up. There are a lot of powerful data models and workflows that you can use as starting points. You can also simply reuse and rename them. 

Whenever you're building things, work with your team regularly on the data model supporting it so that you have a lot of reusable capability. So, you enhance it. It is worth the time to meet weekly with your team over your data architecture.

I would rate Pega BPM an eight out of 10. There is a bit of a learning curve, but it is extremely powerful. When you get into it, then you realize that it is far more powerful.