Pega Platform Reviews

We have integrated a tool with Pega. It is used for project management. We use it for customer process management, insurance, and licenses.

The frameworks are built over the core Pega platform. All the codes are already built. A user can directly use the framework according to their needs. All the corresponding data models and processes already built in the framework can be reused with our custom layer. The tool reduces our costs. It is faster to implement.

The solution has everything. It is model-driven. It generates its own code. It has a rules engine. Previously, Pega had its own UI. Now, we have Constellation DX API. It helps us have any user interface we need, like Angular or React. API helps create work objects in the workflow.

The licensing cost is very high.

I have been using the solution since 2004.

As long as we have a license, we get support. The support is good. We must have a contract with the vendor.

Positive

The administrators deployed the tool in my organization. It took one to two hours. It doesn’t take much time to deploy tools in the cloud.

There are different licensing models.

We integrate the solution with different business tools. The integration is very straightforward. We have custom wizards to take care of the integration. If everything is set right, integration does not take much time. I recommend the tool to others. Overall, I rate the product an eight out of ten.

I am an application developer or software developer, and I use PegaRULES for writing down the code for full stack development, starting from the UI to the backend to the database. I write everything down for developing the application for the end users. For example, the end users could be bank employees or employees working for healthcare and insurance organizations.

What I found most valuable in PegaRULES is that it allows you to quickly make changes to an existing application. It's pretty easy to do any modification in the tool, which you cannot do in legacy solutions. For example, it takes a lot of time to do it in Java or in .NET. I have worked with both legacy technologies in the past, so that I can tell the difference.

In any low-code, no-code tool, it's always easier to implement, and it's the same for PegaRULES because it's a lightweight tool. I found implementations and transitions in PegaRULES very smooth because everything comes out of the box, making implementation easy. This is the reason why PegaRULES is one of the most sought-after low-code, no-code tools in the market at the moment.

What PegaRULES should work on is the integration aspect. I can integrate it with other platforms, but that can take time. It would be good if integration could be automated or if the tool had more out-of-the-box integration features.

Apart from that, I can do most of the integrations with other platforms in  PegaRULES. Still, from a development perspective, as a software developer, I would like to see an easier way to implement integrations where I can click a few screens or do less coding for integration. Still, if I have to do any integration, it would be possible in PegaRULES, but it would take two to three hours to complete.

I want a more straightforward integration process in the tool because compared to Microsoft Power Platform, another low-code, no-code tool, Microsoft Power Platform is relatively straightforward to integrate with Twitter. You can quickly get the feeds from Twitter. Microsoft Power Platform has an out-of-the-box integration setup with Twitter.

Based on this example, PegaRULES could have a more straightforward integration piece. If the tool had more default integration pieces or out-of-the-box integrations with other platforms by default, that would help a lot. For example, Twitter integration, ChatGPT integration, etc., especially because ChatGPT is becoming popular.

Otherwise, I'll have to write some custom code and then create the connectors and the HTTP connectors and connect the connectors to the system manually, which takes time. I want default integrations that I can plug and play to make integrations in PegaRULES easier.

Integration with the latest AI is a feature I want to see in PegaRULES. For example, an out-of-the-box integration with ChatGPT because I'm working on an integration piece for one of my own POCs, but I need custom coding to build that feature. I need a feature that lets you click a button to integrate PegaRULES with multiple platforms to make the integration process very easy.

Less custom coding when it comes to integration is also what I want to see in the tool, though that impacts developers like me rather than the customer experience because it's more the backend.

I am a software developer and have been using PegaRULES for the last seven years. I started working with this tool in late 2015, so my experience with it is more than seven years.

PegaRULES is a stable product, provided that the upgrade is happening regularly. Every four to six months, there's a patch version ready from Pegasystems. Right now, the latest PegaRULES version is 8.8, which means I'll be having an upgrade a few months from now as I'm currently working on version 8.7.

Any application that has regular upgrades will be stable for sure. Still, if you have a legacy application running version 7.1 and want to upgrade to version 8.8, that's a big jump, requires more effort, and would take time. Though the upgrade process is still quicker, there can be implications because of many code changes. You might have to adjust or tweak your application so that it gets accustomed to the latest features of PegaRULES 8.8.

If the clients upgrade regularly or every four to six months, for example, the tool is stable and has no issues. For clients on cloud deployments, PegaRULES is updated regularly because Pegasystems takes care of upgrades in the cloud.

PegaRULES is a scalable tool. I have worked on banking applications where many loan cases are generated. I've also worked on larger healthcare clients with many cases or work objects generated. PegaRULES can handle that, so it's scalable.

The tool also follows the concept of load balancing, so if the load is too high, you can scale it, for example, when many users log in and work on items in PegaRULES. You apply the load-balancing concept. Based on the client's budget, there can be multiple nodes in a single cluster in PegaRULES, such as five or six nodes. PegaRULES will route to a node with fewer users or lesser load, so the load balancing feature of the tool helps make the tool scalable.

Pegasystems has a support portal where you can go and raise a software request or raise a case if you find any discrepancy. If you need any hotfix, you can also go to the portal, and the support team will install the hotfix and close your software request.

Support for PegaRULES is a seven out of ten, not nine or ten, because of the response time. It might be because the Pega support team receives a lot of queries but has limited resources, so the response time is slower.

In terms of providing the solution, I have no problems with that because most of the time, the solution I receive from Pega support helps a lot. It's nine for me once a caseworker picks up the issue and works on it.

Sometimes it takes time for the support team to respond, but if the issue is high-priority or happens in pre-prod or UAT environments, the team prioritizes that issue, and the response time is less.

Neutral

My company works with PegaRULES because it's adaptable and easy to build applications on. The tool is seamless and lightweight, saving you time and effort.If you don't do much customization, write your own rules, or use PegaRULES only for UI or backend platform-related features, that would reduce your testing time. Using out-of-the-box controls and features saves you time and effort because those have been tried and tested by Pegasystems.

Another reason why the company went with PegaRULES is because of its platinum partnership with Pegasystems.

My company also has very happy clients, primarily because of the tool's performance. I'm talking about clients from different parts of the world, in EMEA, APAC, and the North and South Americas.

It's easy to set up PegaRULES because seventy to eighty percent of the projects have a cloud deployment. Pegasystems does the setup, particularly a cloud setup for any project that starts from scratch, so software developers and clients won't have headaches from the setups. My company can immediately begin with the implementation from day one, so this setup is very sophisticated and makes the tool easy to use.

From what I remember, Pegasystems also helps improvise your setup, so it doesn't take much time, and the process is straightforward.

Deploying PegaRULES is very easy because of the Deployment Managers. A deployment manager is part of the CI/CD (Continuous Integration and Continuous Deployment). Pegasystems has the Deployment Manager, a tool you need to install that you can use to easily integrate all the environments, such as the dev, the test, the UAT, the staging, the pre-prod, and the prod environments. There's a hierarchy of environments till the code has gone live.

The Deployment Manager helps to promote the code from one environment to the other with just a click of a button. You need to create deployment pipelines and click some buttons, and the code is automatically promoted from one environment to another, which makes the process quite fast.

Whether PegaRULES is implemented by a vendor team or an in-house team depends on the project. In some projects, in-house developers working on the application development can do it easily using the Deployment Manager, which is the more modern way to do it through CI/CD. That process doesn't need any input from the vendor or third party.

Another way to implement PegaRULES is by taking the Java files and the Java archival files directly from one system and then putting it on the other system, which is the traditional way to do it.

Sometimes, the client wants only Pegasystems to access the production environment; in that case, the Pegasystems team will handle the deployment of PegaRULES in the production environment. However, before production till pre-production, anybody can do it, particularly anybody working on the application, so there's no need for a third party. Technically, a software developer with two to three years of experience can easily do that till production.

The management team discusses pricing for PegaRULES with the clients, so I have no information on pricing.

I'm using PegaRULES version 8.7, though the latest version in the market is 8.8.

Regarding where the tool is deployed, I cannot say the deployment type in my organization because of security constraints, but it is generally done in both. I have worked on previous projects on-premises and projects deployed on the cloud, but if I have to give a percentage, around seventy percent is deployed on the cloud, and thirty percent is on-premises.

Quite a lot of employees use PegaRULES, and not just in my organization. I'm originally from India, but I'm in Europe right now. India has a lot of PegaRULES developers.

I would suggest to anyone looking into using PegaRULES to go ahead if you or your client wants to save on cost, but your use case should suit the tool. If you don't want to work with legacy codes such as Java or .NET, then go for PegaRULES because it's a low-code, no-code tool, though it initially comes with a licensing cost. Another pro of going with PegaRULES is that you can complete application development in three months, which takes three years in Java, so I advise working with PegaRULES.

My rating for the tool is nine out of ten because I am pretty satisfied with PegaRULES in terms of how my organization uses it, and I'm also happy with Pegasystems.

I have worked with it for multiple use cases, such as insurance, banking, asset management, and oiling. I'm currently using it in banking operations. Before that, I used it in insurance, and prior to that, it was used in asset management.

The most valuable feature of the product is that it's very customer-centric. It's easy to use for a customer or a user. It's also easy for someone who is developing an application. You can develop different features in just one place. You don't have to go to different places. Unlike Salesforce, where you have to buy different components to make a complete application, Pega comes in one single package.

I also like the fact that a lot of platforms and new automation are coming in.

The UI has always been the weakest part. These days, the competition with Salesforce is with respect to the outreach of handling the process. That has been one of the challenging factors. So, mostly, it's about the UI, which I believe is because Pega is dependent upon a third-party application, be it React or Angular, to have a UI.

At times, the performance can be a major issue, which is something they're working on. So, performance can be a concern sometimes.

Their support could also be better.

In terms of additional features, I have no requirements.

It has been more than 12 years.

It's stable because it has been in the market for more than 30 years. There have always been some hiccups, but it's evolving pretty well. There are a lot of features such as NLP, AI, decisioning, process management, and process automation. They have a lot of features coming in. I would rate it a seven out of ten in terms of stability.

It's quite scalable in nature. I would rate it a seven out of ten in terms of scalability.

I work for a huge client organization with at least 500,000 people. Across the globe, there might be many more. In my organization, there are 2,000 to 3,000 people. It's a tool that is being used on a daily basis.

That's a pain point at times. I'm not that happy with their support. They should improve their support in terms of responsiveness and understanding of the customer's needs. It should also be improved in terms of skill because at times, they don't have someone who understands the problem well, and they take unnecessary time in resolving even simpler issues. I would rate them a four out of ten.

Neutral

It's straightforward. There are no complications. I would rate it an eight out of ten in terms of ease of setup.

So far, it has been a bit of an expensive tool to manage. It's not as expensive as Salesforce and others, but it's relatively more expensive than some of the simple applications that can be developed in Java. However, it gets more leverage than usual application-making languages.

Its pricing is on the higher side, but they have come up with different plans and different small products that can be used by smaller organizations that don't have that much money to spend. They have different pricing packages depending on the number of users or depending upon the number of cases created in the production or live environment. I would rate it an eight out of ten in terms of pricing.

My advice would be to know what a product is offering and align your requirements. You should have a clear vision of how you want to use a product and make sure that you are getting what you are looking for. Many times, the salespeople sell something, but the end client or the company doesn't get what they were looking for. So, first of all, the company needs to have a clear vision of the product and requirements.

I've been working mostly with Pega throughout my career. I find it very good in terms of how easily a process can be developed around a customer's thinking. I've not seen any other tool that can be used in such a manner. So, from my perspective, as a developer, I would always recommend Pega, and I would always go for it.

Overall, I would rate it a seven out of ten.

Pega BPM is a business process management tool, and a use case for it is case management. There's a problem statement; for example, for bank support, where you need to work on customer onboarding, you'll find customer details verified by a bank authority. Once the detail is verified, the customer will be onboarded. Pega BPM will handle the three steps or stages. You have to create a case where onboarding will be one stage, verification another stage, and then customer registration as another stage, and Pega BPM takes care of the stages or process model.

Pega BPM is very user-friendly, and business people won't have to do a lot of configurations on it. The Pega team also came up with App Studio.

With every release of Pega BPM, new features and modifications emerge, enabling business people to do many things, which helps improve the organization.

The most valuable feature of Pega BPM is step-by-step voice guidance that converts your problem statement into different diagrams and then implements the process.

Pega BPM is a technology, not merely a tool, so it has different industry frameworks. It's customized for various industries, such as financial, insurance, healthcare, etc.

Other valuable features of Pega BPM include AI, decisioning, and robotics. It also has a more intuitive UI. Clients weren't as happy with the UI in the past, but that has now improved.

I also like that Pega BPM has a UI that can be integrated with JavaScript-based, such as React or Vue.

An area for improvement in Pega BPM is security. It's secure, but it still has a lot of vulnerabilities, though Pega takes care of security through upgrades and different patch versions released from time to time.

Pega BPM is robust, but it still needs some improvement performance-wise.

I've been using Pega BPM for twelve years.

There shouldn't be any issues with Pega BPM stability-wise as it's the number one BPM tool in the market, and it's been in the market for forty years. It's pretty stable, though when there's a new version released, sometimes, there's an issue, and the Pega BPM team quickly resolves that.

Pega BPM is scalable. You have horizontal and vertical scalability. One type of scalability is just adding servers. Pega BPM is Java-based and runs on JMS, so you can add different servers. You can add other nodes, or in one node, you can have different JMS, so in this way, you can increase the processing power easily.

Another way to scale is classifying nodes, so based on the job, you can run the nodes and also run the different functionalities of Pega BPM, which is another process for scaling it up.

Scaling Pega BPM isn't challenging because it's running on the cloud, so you can always add and subtract nodes as needed. If your Pega BPM is on-premise, you can scale it horizontally or vertically. It supports both horizontal and vertical expansions.

I've contacted the Pega BPM technical support team many times because of issues I found in the tool that only the Pega core team can handle. I create a service request, then a person from the Pega BPM technical support team will be assigned to the case, then I'll work with that person.

It's normal in a day to experience an issue, need modification, or get help from Pega support. The support process is pretty streamlined. You have to go to the Pega website, create a service request, and immediately someone will be assigned to your ticket, and he will get in touch with you. Quickly, you can get into a call with support and talk to him, so technical support isn't an issue.

My  Pega BPM technical support rating is seven out of ten because you don't get to talk to an expert on the first call. If your issue isn't resolved in the first call, then that's the only time you'll get an expert. Otherwise, Pega's support is good.

Neutral

Pega BPM is the number one tool in the market, so the only reason a client switches over to another BPM tool, such as Appian and IBM, is purely because of finances and nothing else. Functionality-wise and feature-wise, other BPM solutions aren't at the same level, not even close to Pega BPM.

In my fifteen or sixteen years in the software industry, I've never seen a client move to another solution because Pega BPM isn't a good tool. Clients always switch from Pega BPM to another tool because of the cost.

Pega BPM is easy to set up, particularly its cloud version, because Pega will help you do all the setup. Pega also provides a JAR file that you can import to your database, and then once the connection is established, you can start using Pega BPM, so the setup is easy.

Infrastructure setup is different when you do it on-premises. Setting up Pega BPM on the cloud is easier.

There's ROI from Pega BPM because it expedites time to market. You can also complete your work based on a Java tool faster when you use Pega BPM within three months, for example, rather than one year.

Businesses get ROI from Pega BPM, which is why many financial institutions use it, for example, Bank of America, JP Morgan, Wells Fargo; you name it.

The costing model for Pega BPM is different. One is a license that you can pay yearly. Another licensing model for Pega BPM is based on the number of cases you create in production in a year. Costing based on use cases is also available for Pega BPM. I don't have information on its exact pricing or costs, though.

I handle different projects that use Pega BPM. Some use version 8.5, while others use 8.7. I also have some using version 8.8 of Pega BPM.

Pega BPM is deployed differently for different projects. Some on the public cloud and Pega Cloud on AWS. Some deployed Pega BPM on-premises, while others deployed the solution on a private cloud. All three versions of infrastructure can be used for Pega BPM.

My organization is a pure Pega organization, so out of one thousand people, at least six hundred people within my organization work on Pega BPM, but my organization is a service organization with different clients. It's an elite partner of Pega, and only ten elite Pega partners exist worldwide.

My rating for Pega BPM is eight out of ten.

PegaRULES is utilized to streamline the progression of a case or business process, guiding users through various stages and steps required to accomplish a specific task. PegaRULES offers built-in functionality for reporting and provides a basic user interface. It is currently implemented on an older version of the Pega platform, specifically Pega 7.1.7 or 7.2, which may employ technologies, such as Cosmos.

One of the key advantages of PegaRULES is its out-of-the-box capabilities, which eliminate the need to build certain functionalities from scratch. For instance, features like "get next" in process flows allow for the seamless continuation of a flow without the requirement of additional activity creation. This serves as an illustration of how existing components can be leveraged rather than starting from scratch. It provides a solid foundation, to begin with, and allows for enhancements at a higher level, making it a beneficial starting point.

There is room for potential improvement in the performance of PegaRULES, as well as the need to address any existing security concerns. It should be noted that working with an older version of Pega, rather than the latest 8.x versions, may limit certain capabilities and leave room for vulnerabilities that could benefit from increased attention. Furthermore, the user interface (UI) could be a candidate for enhancements. It is worth mentioning that newer versions of Pega may have introduced improvements in these areas. 

I have been using PegaRULES for approximately five years.

At times, I find PegaRULES to be a bit convoluted, although I don't rely heavily on their technical support. Instead, I usually turn to their Pega Product Network (PPN) to seek assistance when I encounter challenges. It proves helpful to see what others are writing and sharing on the platform.

One aspect I am not fond of when it comes to PegaRules is their training. The training methodology often feels disjointed and lacks clarity, making it difficult to grasp the concepts they are trying to convey. Personally, I have struggled to understand their training materials based on my own experience.

I rate the support from PegaRULES a seven out of ten.

Neutral

PegaRULES is generally straightforward to work with, at least in my experience. While there may be some learning involved, it is not overly complex. Having some familiarity with Java can also be beneficial. Personally, I did not encounter any significant difficulties when working with PegaRULES.

The price of PegaRULES is more expensive than other solutions on the market.

I rate the price of PegaRULES an eight out of ten.

This is one of the best solutions in its category.

I rate PegaRULES a nine out of ten.

This solution is useful for business process management if you have any banking solutions or need to manage a process. Maybe a very simple example could be a loan approval process where you need to upload your documents and have them be verified by users. In other words, you have a methodical process in place that encompasses reviews. It can be anything, it might be an order that you have placed on Amazon which needs to go through another. Anything that involves a methodical process is a good fit for Pega as a product.

What I found the most valuable is the case management and the UI design capabilities. We have the ability to do any kind of integration on Pega, which is really beneficial. 

I think there is room for improvement in the low code/ no code environment that they're promoting now. That needs to be aligned a little bit more. I still feel that it is not that friendly for a person who has no experience with Pega to just go in and try to create something. It is a little bit difficult to comprehend, which can be a challenge for the developers who manage the solution because they will have a hard time getting people to use it. For example, if several business users start developing an application at the same time, bottlenecks can happen and the developer will have to go in and kill the conflict in the rules that they have created. That could be better streamlined, which means there is room for improvement there.

I have been using this solution since 2010.

I would rate the stability of this solution a nine, on a scale from one to 10, with one being the worst and 10 being the best.

I would rate the scalability of this solution a seven, on a scale from one to 10, with one being the worst and 10 being the best.

I would rate their support a five, on a scale from one to 10, with one being the worst and 10 being the best. There are lags in their responses.

Neutral

My impression is that the initial setup process has to be followed via documentation. It's becoming a little bit less complicated, but it is still not easy for an inexperienced user to kickstart and deploy. The deployment an hour and a half at most. It can be deployed by one person. 

I would rate this process a six, on a scale from one to 10, with one being the worst and 10 being the best.

The pricing is a bit costly. Although it is a little bit costlier than all other tools on the market, it is more consistent. It also shortens the time to go live by quite a bit.

As far as maintaining this solution goes, how extensive it is will depend on whether or not you will be maintaining just Pega. It allows you to delegate many of the business rules to business users where they themselves can actually go and configure their rules and modify them. A user can have their own dedicated set of rules that they can go and configure. 

Overall, I would rate this solution an eight, on a scale from one to 10, with one being the worst and 10 being the best.

Our use case for Pega BPM is BFS process management. Earlier, we were facing some challenges such as using the end numbers of applications, but now we are careful. Decision-making took too much time in the past, but now that can be done within a few hours or a few days. For example, when managing a claim, that used to take almost five days to a week. Now, that would only take two to three hours in terms of resolving issues. The processes are much faster now in Pega BPM, in particular, almost ten times faster.

The most important features of Pega BPM are case management and claims management, and soon they'll also be offering claims processing.

I also love Pega BPM in terms of performance. It's also one of the very few user-friendly solutions in the market. It may take some time to learn Pega BPM, but once you get a proper handle on it, tracking and managing processes become very easy anytime, anywhere.

Pega BPM also has very good documentation you can use to learn the solution. Pega has a community portal that has complete information and explanations, and if you're facing a challenge, you can post your challenge on the community portal and get a resolution at the same time.

Currently, there isn't any feature I want to be added in the next release of Pega BPM because Pega always adds new features that my team welcomes and looks forward to learning.

One area for improvement in the solution is the long learning curve, but after that, you'll find Pega BPM easy to use.

I've been using Pega BPM for almost four years now.

Pega BPM is a stable solution.

Pega BPM is a solution that's easy to scale.

I haven't contacted the Pega BPM technical support team yet, but when an issue arises, and I would need to contact the team, hopefully, there would be a good response and availability from them.

Pega BPM is my first BPM solution, so I have no experience with other similar solutions.

Setting up Pega BPM was very easy for the team. Deploying the solution is so much faster and takes up a lesser amount of time than other solutions. For example, if a competitor takes a month to completely deploy, Pega BPM deployment will be completed within two weeks, or almost half a month.

I would rate the setup for Pega BPM four out of five.

We implemented Pega BPM in-house through our BPM team.

In terms of the pricing for Pega BPM, other solutions may be cheaper, but it doesn't matter if Pega BPM has a higher price tag because what's important is that it's the best solution, and that is what people look for.

If I would rate the pricing for the solution, I'd give it three out of five.

You have to pay extra for additional features in Pega BPM.

The business process management solution my team uses is Pega BPM, particularly the older version 7. My team is planning to onboard the new version of the solution, version 8, soon.

Maintaining Pega BPM is sometimes expensive, but it's manageable. It takes money to maintain the solution, but it's a good product based on the service it provides to customers. Pricing doesn't matter because what matters to any client is that the solution should be very good and should provide accurate results. This is the main reason people go with Pega BPM.

My company has a team dedicated to maintaining the solution.

Five to six people currently use Pega BPM within the company.

For now, I don't have any suggestions for people looking into implementing Pega BPM because for sure those people have research teams that do the research and implement the solution according to market research. They know exactly what type of solution is needed based on research.

I would recommend Pega BPM to new users of BPM solutions or local platforms, but research is still required before implementing the solution.

My rating for Pega BPM is nine out of ten.

My company is a partner of Pega BPM with clients it provides services to. My company also provides implementation support to clients.

We had an audit team for order management, primarily focused on mobile communications. This encompassed tasks such as SIM card dispatch and user configurations.

The most notable feature is the dynamic workflow changes, allowing adjustments without completing the entire cycle. Transitioning from test to build to production was seamless and on the fly, which is something truly remarkable about Pega. Additionally, the workflow creation doesn't require users with extensive technical skills, thanks to its low-code platform, making it accessible and efficient.

The pricing could be flexible and have multiple options. It is mainly suitable for large enterprises. They could have subscription plans to cater SMEs.

I have been using Pega BPM for four to five years.

I rate the solution’s stability a seven out of ten.

The product might not have been developed, possibly due to the absence of a dedicated product owner overseeing its development. Those who did the coding might not have performed up to standard. Improvements could be made in that area, as the code quality was lacking, affecting the scalability of the product.

300-400 users are using this solution. I rate the solution’s scalability as a five point five because we have lot of performance issues.

The setup process is fairly complex, and we always need an integrator for implementing it. It requires expertise in the platform. It's essential to have someone with Pega expertise rather than relying solely on regular users.

Pega is expensive than Versace. I rate the solution’s pricing a six on ten.

When it comes to Pega, I haven't come across any particularly outstanding out-of-the-box functionalities. However, I appreciate their local, no-code approach, which makes it easy for users to quickly grasp how to create work solutions. Although case management is included, it doesn't seem as flashy compared to other VPNs.

Pega was coming with lot of out of the box integration options with APIs and others but, we did not drive the AI part.

Based on the specific use case, I would recommend it to companies prioritizing user functionality over scalability in their portfolio. However, it's crucial to collaborate with a skilled integrator to ensure smooth implementation.

Overall, I rate the solution a seven out of ten.