Pega Platform Reviews

We use the solution as a low-code development tool. The tool has pre-built rules. Hence, they can be reused and configured as per client requirements.

We can use the rules as per the class.

PegaRULES need to improve its JVM. It needs to enhance the operation speed and memory size.

I have been working with the solution for four years.

I would rate the tool's stability a nine out of ten.

I would rate PegaRULES' scalability a nine out of ten.

The tool's support will take time to resolve issues if it's a product enhancement issue. Application-related issues will be resolved immediately.

Positive

PegaRULES' setup is easy.

I would rate the product's pricing a six out of ten.

PegaRULES is mainly for enterprise companies and I would rate it a nine out of ten.

The latest releases of PegaRULES are scalable, advanced, and can be easily integrated into your environment.

PegaRULES should provide a more drag-and-drop interface to make it a low-code, no-code product.

I have been using PegaRULES for about a couple of years.

PegaRULES is a stable solution.

PegaRULES is a scalable solution.

The solution's technical support is good, but getting professional support is a bit expensive.

Positive

The solution’s initial setup was easy.

The solution's overall deployment plan was for around a couple of weeks.

PegaRULES is a good product, but its pricing is a bit on the premium side, especially for professionals. Licensing-wise, PegaRULES is at par with market rates.

Overall, I rate PegaRULES a nine out of ten.

We are using Pega for content management and as a ticket management system.

The most valuable feature is flexibility, as we can configure it to best suit our requirements.

The reporting does not work well for us. If we have somebody working on a ticket or request, we are not able to track the end-to-end time. Also, the assignment is not happening correctly. Ideally, they should have panel management reporting.

The end-user notifications need to be improved because there is a delay.

It is not fully compatible with all versions of Internet Explorer, so sometimes, it does not work. There are technical glitches because of this.

I have been using Pega BPM for about three and a half years.

We have experienced technical glitches with the use of Internet Explorer and with reporting.

I don't feel that there are any issues with scalability. That said, until our concerns with reporting are satisfied, we don't want to scale.

The technical support is good.

The initial setup is not complex, although I would not say that it is simple, either. You need to know the technology to implement it.

Our in-house technical team was responsible for the deployment, and we had a consultant working with us.

The pricing is pretty good, compared to other similar products.

We are changing systems because we are trying to bring total service delivery into a common platform, and Pega is not able to handle the requirements. We are interested in a user-friendly solution without reporting glitches and difficulties.

The suitability of Pega BPM depends on the requirements. For smaller companies, where one or two products are being serviced, I would recommend it. However, I suggest that larger enterprises consider other tools.

For what they are providing, I think the pricing is fair.

I would rate this solution a six out of ten.

We use Pega BPM for one of the finance applications and the different order and demand management.

Pega BPM offers a lot of out-of-the-box functionalities.

Pega BPM's documentation should be improved, especially for freshers or new trainees.

Pega BPM's pricing could be improved because it is expensive. People are not choosing Pega BPM because of its price and are moving to open-source or cost-effective solutions like Camunda.

I have been using Pega BPM for around two years.

Pega BPM is a very stable solution.

Pega BPM is a scalable solution. Around 10,000 users are using Pega BPM.

Pega BPM's initial setup is easy.

Users have to pay a yearly license cost for Pega BPM, which is expensive.

I am using the latest version of Pega BPM.

When we started, it was a team of 10, and now 23 employees are involved in the solution's deployment and maintenance. The solution has nine to ten developers and testers.

Overall, I rate Pega BPM a seven out of ten.

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.

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,