Pega Platform Reviews

They use it for marketing and case management. It is also used for workflow process automation and market intelligence, using the solution’s AI capabilities.

The case management functionality of this solution has been most valuable.

There is a scarcity of resources who have worked with this solution before.

I have been using this solution for eight years.

This is a stable solution.

This is a scalable solution.

I would rate the customer service for this solution a four out of five.

Positive

The initial setup for this solution is not that complex.

The enterprise product has the best features as a cloud product. It is the market leader in the BPM space.

I would rate this solution a 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.

We use this solution for HR automation or HR service delivery.

It is quite configurable, which is the most exciting feature. We can easily configure it as per our needs. 

Reporting is not so clear and not so great. We really struggle to get the right reporting. When we need reporting based on the content of the tickets, we are not able to get it. The MIS reporting is not great. That's one of the reasons why we are switching to ServiceNow.

Its compatibility with the higher versions of Internet Explorer should be improved. It really works well in Mozilla Firefox or any other browser, but when it comes to Microsoft Edge or Internet Explorer, sometimes, the layout gets disturbed. The positioning of the buttons changes, and there is some distortion in the layout. I am not sure whether it is our configuration problem or Pega's, but when it is working in Mozilla Firefox, it should also work in Microsoft Edge or Internet Explorer.

I have been using this solution for almost three years now. We started using it in late 2017.

It is stable. We haven't faced any downtime or any other issues.

It is quite scalable.

My team would know about it, and I personally don't really get into those details. After the implementation, our teams are on their own. I don't think they are reaching out to Pega support frequently because I don't see any product issues as such. Everything is configurable, and it is running daily.

It is not so complex, but it needs an intermediate level of skill set. It is not so complex, but it is also not so easy.

It is cost-effective for medium enterprises. It is cheaper than ServiceNow.

I would definitely recommend this solution. It is more cost-effective as compared to other products. It is the right product for medium enterprises rather than a highly-expensive solution such as ServiceNow, to which we are switching. When you're implementing it, you should configure it in the right way with all categories, subcategories, and other things.

I would rate Pega BPM a seven out of ten.

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.

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.

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.