Pega Platform Reviews

In the Middle East, ministries such as the Ministry of Justice, Ministry of Labor, Ministry of Finance, Ministry of Education, and Ministry of Municipalities, are using Pega Platform as a front-end application for their citizens.

Pega Platform is excellent for enterprise-level solutions with integrations to entire systems, including case management, service orchestration, CRM, decision-making capabilities, digital process automation, and AI-driven functionalities. It allows for a unified platform with features like case management, BPM, service orchestration, low-code development, digital process automation, CRM, and decision-making, all integrated into a single platform.

In the Middle East and Africa region, Pega was not very strong from the user experience standpoint. To address this, Pega introduced Constellation, which allows a user to build a more engaging visual experience.

I have been working with Pega Platform for over a decade now.

From the platform standpoint, I haven't contacted Pega for support unless it is a product issue or a new feature issue. I never needed support from the platform standpoint, but if additional features are required, we have regular meetings with the product team for feedback.

Top banks in the world, such as the government's HMRC in the UK, see the return on investment with Pega Platform as they use it at an enterprise level.

I work with Camunda for pro-code projects and OutSystems for other requirements. Camunda is a good BPM engine, but it does not provide comprehensive features like Pega. For simple case management, alternatives like APN and Camunda were mentioned.

If you're looking for a solution at the enterprise level with comprehensive features, then Pega is suitable. However, if you only need a simple HR system or a small case management application, other tools might be more cost-effective. Pega Platform is comparable to SAP in terms of its dominance in digital process automation and business process management.

I'd rate the solution eight out of ten.

The primary use case for this solution is business process management within a local bank. The environment involves handling various banking operations and customer interactions, where the solution aids in streamlining and automating processes.

The platform has significantly improved organizational efficiency by automating complex processes and enhancing operational flexibility. It has facilitated smoother workflow management and integration with existing systems, improving overall productivity.

The product's most valuable features include its adaptability and flexibility, attributed to its Java-based architecture. It allows for easy updates and incorporation of new features, ensuring the solution remains relevant and effective in meeting changing business needs.

The product's artificial intelligence capabilities could be improved. More advanced AI features could further optimize process automation and decision-making.

I have been using Pega BPM for approximately three years.

The solution generally maintains good stability. It is designed with dual balances to ensure continuous operation even if one server fails.

The platform is highly scalable, accommodating the growth of organizations and adapting to increased demands effectively.

We previously used a different business process management tool but switched to Pega BPM due to its superior flexibility and adaptability to our specific needs.

The initial setup was straightforward and self-explanatory, taking approximately one day to complete.

The implementation was conducted in-house, and no vendor team was involved. Our internal team handled the process efficiently.

The return on investment is substantial, ranging from 3o% to 80%, with visible improvements and benefits typically realized within a short period.

The product pricing is considered reasonable compared to other solutions in the market.

We evaluated several options, including IBM BPM and Oracle BPM. 

Overall, the solution is highly effective for business process management. However, to fully leverage its capabilities, you must stay updated with the latest features and improvements.

I rate it an eight out of ten. 

Our company is the service provider for Pega BPM; we act as the IACs for three products from Pega. We recommend a product to our company's customers based on the requirement and their budget. 

If a customer is looking for a platform at the enterprise level, which comprises customer service, case management, BPM, and mobile features, our company recommends Pega BPM to them. 

When customers look for standalone applications, not at the enterprise level but a quick local platform they want to build some applications with, such as a leave management system or an attendance system, then we recommend other solutions than Pega. 

When an enterprise-level platform is required, which is Pro Code, our company recommends Comodo. If someone is looking for a case management platform to perform the BPM and native operations using native mobile apps but not the front-end processes, this is where our company will always recommend Comodo.  

The UI cannot be customized in the solution. 

I have been using Pega BPM for ten years. 

Our company is an Elite partner of Pega; there are only six to seven Elite partners of the vendor, which include TCS, Infosys, and Accenture. Thus, our company has a strong relationship with Pega, and we receive a response within an hour from the tech support team when an issue occurs. Our company's CEO was the technical director of Pega for fourteen years. 

For small and medium-scale requirements, the solution can be deployed within a week. But for large organizations the deployment time would vary depending on the requirement volume. The largest systems in Saudi Arabia are running on Pega. The solutions from the vendor handle the process of commercial registration, compliance metrics, investment management, citi management and integrations with IoT solutions. 

Pega is usually not recommended for developing small-scale applications; rather, Comodo or OutSystems can be used. Pega CRM is one of the most robust applications in the market, offering a private cloud, unlike Salesforce.

Some customers in the Middle Eastern countries, India, and other APAC countries don't want the cloud to be hosted outside their native countries. Vendors like Salesforce don't have a cloud server available in the Middle Eastern countries. Pega now offers integrated customer service, 360° customer view, and additional services as per customer needs. 

For one of our customers for Pega, their revenue escalated from 300 million a year to 600 million Saudi riyal in a quarter. There are multiple Pega licensing models, including outcome- and revenue-based licensing models. Financial institutions usually prefer Pega's revenue licensing model. 

For instance, a loan-based financial institute will have to pay X amount as the cost once they can cater one billion loans. As a thumb rule for price calculation, if you are availing a limited number of licenses for a small entity, it's going to cost you a dollar for each case or end-to-end workflow. 

From creating a Pega account to purchasing the solution, all the processes in between, including the KYC and customer role management process, are considered a single case. If there is a huge volume requirement of ten million cases in India, the same price will come down to 50 cents per case; with negotiation, it might also come down to 33 cents a case. 

Pega BPM and other solutions from the vendor are all low-code solutions. Especially in the Middle East and African markets, our company has noticed that they are more focused on front-end development; therefore, often, a customized UI is required, which cannot be implemented with Pega due to low code functionality and standard principles defined in the platform. But Pega BPM offers an integrated case flow and customer service, which contributes to the vendor becoming a world leader. 

There are AI-driven business process management features being incorporated in the solution. For instance, if you mention the vendor about your plan to develop a loan application, they build the entire case flow for you and make the application available within an extremely short span, after which the connectors and APIs need to be set up and integrated. Pega BPM is a highly advanced solution. 

At our company, we also evaluate if a customer actually needs Pega solutions before recommending it. For instance, if Pega is considered the Ferrari of the industry and the customer is willing to drive at a speed of 10 to 20 Km/h, then it's not worth the cost. For basic requirements, a customer can choose Comodo when only the BPM layer and custom UI are needed to build native mobile apps, while the workflow remains on Comodo. 

Pega is the leader in business process management solutions. Pega creates market trends across the globe. If you check Forrester or Gartner reports, Pega has always been rated as the top BPM solution provider. Other competitor companies learn from Pega and implement improvements in their products. Pega is not considered a front-end portal platform. The limitations of Pega are quite logical. The product owner of Pega mentioned that to build a low-code rapid development platform, it is mandatory to provide templates.

For example, in MS Word, you can use the numerous templates or start from a blank template. The templates in Pega are pre-defined; they cannot be customized; when starting from scratch in a solution, it won't be considered as a low-code solution. Pega needs to find a way to implement low code even with a blank template. Pega is working on a new product line called Constellation in which the aforementioned issue will probably get resolved. 

I would overall rate Pega BPM an eight out of ten. There are still some challenges with the front-end aspect of the solution, but the product is best when it comes to business processes and customer service management. 

The European and American customers of our company are more keen on the process flow rather than the application appearance at the front-end. But for customers who are focused on the front-end more than what's underneath the Pega product, it becomes very difficult to make them understand the value of Pega. I expect the vendor to implement improvements on the front-end. 

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.

The primary use case includes working with Pega Platform, but the organization is planning to switch to another solution soon.

While there may be stability issues, they are minimal.

The technical support is very low, rated at a one or two out of ten. There is a lack of support and community presence in the country, leading to challenges in finding developers.

There have been some stability issues, however, they are not significant.

The technical support from Pega is very low, rating a one or two out of ten.

Negative

The pricing is expensive, and this is an issue.

The organization is in the process of selecting a new solution.

I'd rate the solution seven out of ten.

I work in the automobile industry, and I generally use Pega for automating regulations and warranty applications.

Currently, we are in a project where the return on investment is less than six months, which is quite noticeable. Time savings are about three hundred percent when building an application in Pega compared to building in Java.

It's an end-to-end solution and a digital transformation tool. It has a range of modern technologies and proven designs built into it, making it a one-stop solution for many industries, including banking, insurance, automobile, and government. It includes AI, has decision-making capability, and is a rich case management tool.

The UI layer is a concern since it is native to them and embedded into the code. I cannot have my own UI layer at the moment. Also, finding a person with the right knowledge for Pega, since it has fewer resources available, is a challenge.

I have been using it for 18 years now.

When you say stable, it all depends on how you have approached the application or the design. If you choose it and design it correctly, it is 100% sustainable.

There is no need to be concerned about scalability. It is scalable across regions and divisions.

The support is okay. I would rate it as six or seven. They have a process-driven approach that can delay problem-solving.

Neutral

I have used WorkFusion and Kofax in one of the solutions. However, Pega clearly outperforms them in all aspects.

As a cloud-based solution, it's a click away. If you are talking about on-premises, it hardly takes an hour, and one person is enough for installation.

Currently, we are working on a project where our return on investment is less than six months.

Pega is at the higher side of medium pricing, but with the cloud, it should be manageable.

I have used WorkFusion and Kofax before. However, Pega clearly outperforms them.

I'd rate the solution nine out of ten.

We use Pega BPM for backups, consumers, markets, payments, loans, etc.

The most valuable features of the solution are case management, routing, and low-code environment.

The solution's pricing model or licensing model could be a little better.

I have been using Pega BPM for 12 years.

I rate the solution’s stability an eight out of ten.

I rate the solution an eight out of ten for scalability.

The solution's technical support is good, but there are some things it needs to improve. Sometimes, the support takes longer because of the customer queries and the analysis it has to do.

Neutral

The solution’s initial setup could be made a bit easier.

We are using the solution's case management, many finance-related modules, and some frameworks. The solution's case management function has improved our daily operations. It was easy to customize Pega BPM for our industry. The solution handles some industry-leading tasks, like legal compliance.

Pega BPM has a huge offering, which includes CLM (Contract Lifecycle Management) and many frameworks built into their packages to comply with industry standards. Pega BPM is deployed mostly on-premises in banks for data security. Other BPM services, such as Oracle BPM, IBM BPM, Appian BPM, and Camunda BPM, are available in the market.

Small and medium enterprises have different needs and different costs. Pega BPM simplifies the modeling of a typical low-code workflow and data. There are other use cases where some other tool works better. Recommending Pega BPM depends on the business needs and journeys. Using the solution varies from case to case and depends on cost, complexity, infrastructure, and all other associated things that come with it.

Overall, I rate the solution 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.