Pega Platform Reviews

When our clients automate the KYC and onboarding processes, they can reduce their manual force and then deploy them in much better tasks rather than the mundane activities of selecting forms and gathering information.

There is definitely an advantage to digitization, so we recommend Pega to our clients for the KYC digitization. Pega's strength is in KYC onboarding.

The workflow automation can be slow, so there is room for improvement there.

Personally, I have been using the solution for the past three years, but my company has been using it for about seven or eight years. 

The solution is stable.

The solution is quite scalable. 

The customer service team is very responsive and helpful. We haven't had any complaints or issues with them. I would rate the customer service as a nine out of ten.

Positive

The initial setup was easy. On a scale of one to five, I would give it a four. 

The deployment was handled by Pega and was quite easy, not very complex, and the customer was satisfied. 

The pricing is a bit on the high side, but you're paying for a quality product.

I would recommend that you work with one or two Pega developers in the initial stage. After that, it's quite straightforward.

I would rate this solution as a nine out of ten. The Pega product is definitely good. 

I use Pega BPM to automate business use cases and integrate third-party application data into applications designed on Pega Platform.

Previously, our HR onboarding application ran in silos, so everything was happening separately. Pega BPM allowed us to consolidate all the data in one place, from which we could define our business workflow. This means that we have the entire flow running in one application from start to end with the help of third-party application data.

Pega BPM's most valuable features are case management, integration, the convenience of using REST APIs, and the ease of changing things at the UI level.

Pega BPM could be improved by including token-based authentication and extending its integration options. In the next release, Pega should live up to their claim to be low-code/no-code and make their platform more simple and UI-based.

I've been using Pega BPM for almost two years.

Pega BPM is stable.

Pega BPM is scalable.

The initial setup wasn't complex, but you have to define your class structure and architecture properly. Deployment took around a month. Also, Pega says BPM is low-code/no-code, but that's not true - you need intervention as you can't design the application without some knowledge about it.

We used an in-house team.

Pega is expensive. If your company has a good amount of money to spend, go for Pega as it has many things readily available out of the box. But if you're looking to save money, you may be better going for an open-source platform.

I also evaluated WaveMaker, but Pega has features that aren't available on WaveMaker.

Pega BPM is a very good tool if you have the budget to spend on it and you need to automate any business process wherein you get the data from multiple sources. I would rate Pega BPM as six out of ten.

PegaRULES is used more for business process management. Perhaps in a bank or any other organization. If you want to automate anything, you may require a tool, which is, simply building the same thing in Java. 

People choose Pega because it's a flow-oriented tool that is already predefined and you can plug and play.

I can say that less development effort is required for developers, allowing them to focus on business problems rather than technical issues. It corresponds to every BPM, so it serves the same function.

Pega also sells the same so that you can integrate with legacy applications or with different applications that may or may not have AP capability. You can use UiPath in between with PegaRULES integration.

There are a lot of features, which most people prefer.

Case Management is the most valuable feature of PegaRULES, which is not found in other BPM tools.

Containerization should be improved in relation to Pega because Camunda is deployable in the containerization deployment process. Pega is trying to move in that direction, but that will have to improve slightly.

I have been using PegaRULES for 15 years.

Pega has multiple models, and I believe a few teams are cloud-based. Our organization is mostly moving to the cloud, but not entirely. However, we use on-premises deployment.

PegaRULES is extremely stable. It is still dependent on developers. 

Initially, I believe we will require the services of architects to set up the cloud structure and design. Everything must be thoroughly reviewed. Developers will need to follow suit. In terms of stability, I would say it's a solid application. How you use it is determined by how you built it. You must exercise caution when developing the application. If teams attempt to build the Pega without the necessary experience, performance issues and other issues may arise. That design must be correct, and it must be reviewed and monitored. I believe it will be able to stabilize this application.

It can also be scaled up. It is determined by the scope of the data, but it can be scaled up to meet the requirements of the application. It's in hardware and adding hardware to an extra. It will follow the data availability features. Pega will support the ability of Java applications to scale up based on stability. I don't know much about that particular hardware side, but I can say that it can scale up to meet the needs of the user. It is dependent on the application or how large these applications are. It can be scaled to any size.

The number of users is dependent on the project. There are large projects that may involve 10,000 or more users. In a few applications, you may see only 1,000 or 500 users or something along those lines. It is dependent on the application and who is using it.

I have contacted technical support, and they are very good.

The technical support for Pega is excellent. They were able to assist us and even guide us if we had any issues. If you contact Pega technical support, we'll find a solution right away.

I would rate them a five out of five.

Positive

We mostly use Pega products.

Pega provides documentation. The same documentation can be followed during their own deployment process.

In my opinion, it's not complicated in terms of deployment; but it depends on how your applications will be deployed. It's the same method. 

Pega will also assist you in this regard. It simplifies the deployment process and makes it easier to set up others.

I would rate the initial setup a five out of five.

If everything works and is ready, the initial setup can be deployed in half a day.

In terms of the price, if I were to compare Pega to other tools, it would be more expensive, but it would also provide you with the same features.

If there are applications that scale up to the enterprise level, we would go with Pega, and if it's a smaller application with a smaller workflow, or if they can't afford to invest that much money, they'll go with less expensive tools such as Appian. Camunda is open source, we have people working on it.

The licensing fees are not that much.

I would rate PegaRULES an eight out of ten.

We do not use this solution in my organization. We are consultants and we act as a third-party for our clients.

This solution is used to orchestrate processes across different parts of the infrastructure. All of the activities are coordinated and controlled, managed by a unique platform where they can keep track of everything. 

The most valuable feature is the situational layer cake. It's a feature of the tool that allows us to specialize a process according to different countries, products, or other dimensions. This means that we can create complex processes that are differentiated according to geography, product, or other characteristics. The result is that it makes it much easier for us to maintain the solution.

In terms of functionality, Pega is probably the number one solution in this field.

Compared to other BPM products, the interface is somewhat complex, so the usability could be improved.

We have been using this solution since 2014.

Pega BPM is very stable and our customers use it on a daily basis.

This is a very scalable solution. Our customers are large enterprises.

The technical support is okay.

One of our clients was using a BPM solution by TIBCO before switching to Pega. TIBCO is more technical, whereas Pega is more business-oriented.

The initial setup is quite complex. It requires a lot of time and its not something that you can just do quickly. Pega is a very complete and structured product that needs to be configured according to the organizational structure.

Considerations have to be made with respect to managing data and integrating with their tools. In many ways, it is a Plug and Play tool, but it will require some time.

We have had cases where we have done the deployment for our customers, although in other instances, the client does everything. We prefer not to do the installation, if possible.

The price of this solution, including installation and configuration, is comparable to competing vendors.

My advice to anybody who is implementing this solution is to make sure that they understand it. For example, we are certified in the usage of Pega BPM. It's a very complete product but it is not a simple one. They need to use the right, structured approach to implement it properly. Pega is not a product for a client with small needs. If anything, when setting up Pega you should think bigger and put things in place for what will be needed to lead the team in the right direction in the future.

I would rate this solution an eight out of ten.

In terms of features that I have found most valuable, there are lots of new things in Appian BPM, maybe six in this newer version. Earlier, what we needed to do if we wanted to deploy some code into the other environment was to upload it into the environment, take a patch from the other environment, patch it, and import it. Nowadays it is easier. There is a new feature in the Admin Console where I just need to click on that environment, pick a patch, and just select the environment. Then I see whether it is queuing in the scheduled environment or going for production. I select the environment and I can directly deploy that patch. This is a very good feature of the current version.

There is a very well implemented UI side - the front-end visibility. There is a new progress bar that allows you to see your progress. There is a very impressive UI design that they've embedded into the BPM tool.

In terms of areas that need to be improved, I would say the timeout. This is because sometimes when we are patching some data from the database, we are getting added as a timeout. I would like to build a solution for that or to improve that feature, because by doing so the process will be trimmed. Sometimes it gets stuck just due to taking so much time for the user in the back-end data from the database. I think all the other features are very good.

Additionally, I'd like to select the availabilities. I'm using the earlier version now because it is on-premise implementation. If I go on the newer PGi for a couple of days, the latest version, then I will able to see what other additional features we need to have in the BPM tool.

I've been working on Appian BPM tools for about three years.

I do not have an issue with stability. I'm completely fine with that.

It is definitely scalable and I know that is a very good feature of the Pega BPM and Appian BPM.

I have never contacted support. 

But we have one help ticket raised, so technically I do support the production.

I like Appian BPM. In Appian BPM I need to code for the components. If it's a bigger program, depending on the sizing, I read about using Pega BPM for that. But I'm working as an Appian Lead and working on Appian BPM tools for about three years.

About a year ago, I was working as a DOS developer and then I moved to Appian BPM and Pega BPM. I get feedback from the users. Based on the data from the POC, I present that to the user and if there is any implement I'll do it on the same day and avail it to the user. If they're okay with it, then I can go ahead and create the application and develop it for the solution.

Working as a DOS developer I'm coming from a different place. I came to know about this BPM tool from the website and learned that it has very good features. So that's the main attraction to BPM tools.

The initial setup is not complex, it is easy. For the first time user, we do have the trial version of it. Nowadays, as you are aware, we have data in the Cloud where it is like MySQL. It will take under 30 minutes. Not more than that.

We are working in Agile. So there is a sprint of two weeks. After each and every sprint we have to be looking forward to the after-sprint plans. So the solution has been deployed after each and every sprint to the queue and on the decided date, to the production.

I used a number of integrators for my current project that was as a re-seller. I don't have experience with implementing. On my current project, I do integrate with the re-seller that does business with Appian. We are just consulting for the solution at our end with an integrator at Appian by using the data authentication.

I would definitely let people know about it. Let me give you a scenario. Let's say there is a banking system. Generally, people come to the bank, fill out the form, and submit it. Then a record will be created in the system. So what happens by using the Pega BPM is that we can clearly identify the flow - how you do it by using the different user input tasks. This is appealing to the user, to the customers, to everyone. Definitely I would like to get a return on that and let them know that if they use this BPM tool, more than any other technology tool, it has the most complete set of tools for the system.

On a scale of one to ten, I'd rate it an eight. This is because it is easier to use than any other product and it is more secure. All of our software was developed in Java and as we know Java is a secure language. 

There are many more features. It is easy to use, easy to understand, easy to implement and easy to enhance and we can do it as a Cloud. Also, it is very user-friendly. Nowadays, it's on Cloud so we can access it from anywhere. There is no location per se or any system requirement.

We support clients who use this solution. We have had a client who used Pega in London at their headquarters and in their data center operations in India. They installed Pega in the UK, but they wanted to run the applications from the data center in India. They wanted to give access to all the business users across the world in more than 12 different countries. 

The client used SAP for their business system, Pega for the business process management and UiPath for automation.

The robotic process automation has increased the confidence of business users. 

The cost of licensing could be improved.

I have been using this solution for 5 years. 

There are multiple components within support. This first component is the functional support from an BPM perspective that is module related. The second component is technical support for when clients want any customization of their BPM product along with any workflows.

The initial setup is straightforward. For an implementation project, we usually have a team of 10 BPM developers along with the BPM technical architect and the BPM technical lead. The implementation projects runs over 18 to 20 weeks, while an upgrade project, requires eight to 10 people over 12 to 16 weeks. If it is a support project, we use a team of six people over a period of one year.

Normally, we don't own the licenses. Customers have their own licenses and we work on their environment.

As an IT services company, we provide different solution options to customers. We offer SAP BPM, Pega, IBM BPM and Oracle BPM. The first and foremost consideration is that the customer needs to be comfortable with the solution that we offer. 

Our customer base is varied, ranging from insurance to banking to government. In the insurance domain Pega is used for things like policy, as middleman management, policy administration and claims administration. In the banking realm, it's used across multiple areas from CRM systems, customer service, sales automation, and things like loan origination, payment investigations and payment arrangement management. In the government sector, it's used particularly as a case management software to manage processes.

Most of our customers are enterprise businesses, we are partners of Pega and our company functions as a system integrator. I am co-founder and Chief Technology Officer. 

One of the valuable things in the solution is that Pega offers a unique environment where its entire architecture is very unified, meaning it's used free across multiple areas. In other products, say IBM, and other solutions, the products range across several solutions and include separate components for analytics, separate components for the UI and a separate component for business roles. Pega, on the other hand, is one unified architecture and that is very valuable. The second thing is that Pega is model driven architecture so building something up on it from models is very quick. 

From a room for improvement point of view, what I've seen is that many customers want solutions that directly meet their requirements so while Pega has somewhat vertical solutions on Pega customer service and sales automation, industry and customer experts expect more out-of-box solutions to be readily available on Pega.

It is the same for additional features - the customer expects more business solutions to be directly available on Pega. For example, when I say business solutions, Pega could have a business solution on customer service, a business solution on sales automation. Pega may not have a proper business solution for LOS, or Loan Origination System. These are common business solutions which could be made available in the solution, it would be very good if they could focus on the direct business solutions which customers expect over here.

I've been using this solution since 2003, so 17 or 18 years. 

As enterprise customers are using it, you can tell it's stable. It's one solution which we've basically used and worked both on-prem as well as on cloud and it's one of the other unique value aspects of Pega, that the same solution can work on cloud as well as on-prem. 

From a scalability perspective, it's scalable. In terms of high volume, we have some applications based out of Vietnam which have millions of cases, so in terms of the number of cases, it's highly scalable. We have other customers who also have a high volume of users. 

Because I've been working with Pega since 2003, I can see the improvements that have been made in terms of how they go about establishing contact with customers. These days, it's pretty easy and accessible.

Initial setup is quite straightforward. Deployment time is based on the actual size of the project. On average, it can take anywhere from three to five months to build. Usually, the team servicing from our side is around five to seven people and from the client side it's usually a project manager and a couple of others. 

PegaRules is a very powerful rule engine. It's a very powerful platform to build any sort of solution onto. Where a customer makes mistakes is when they underestimate the business expertise of a partner, so they really need to ensure that initial implementation is right. It is very important to understand who is implementing it on the ground. If they don't understand the business requirements and the required business outcome of management, it can be awkward, and not in line with expectations.

The main thing I have realized is that understanding the business problem and understanding the required outcome for the customer is very important. One of the biggest business areas is to focus on understanding problems and the kind of business outcome the customer requires. It's really about understanding the big picture. 

I would rate this product a nine out of 10. There is always room for improvement, but I've seen many customers getting very good value out of this solution.

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.