Pega BPM Reviews

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. 

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.

The company has a strategic partnership with Pega. I was the general sales manager. 

This is a customizable product. It's low code and can be restored quickly if needed. 

The solution is expensive and it put many of our customers off. After a while, the company was no longer prepared to work directly with customers which created problems. 

I recently stopped using this solution because I changed jobs but I had used it for 18 months. 

The product is stable. 

The technical support is very good. 

Positive

We helped our customers implement this solution because the company had its own in-house dedicated team. 

This product is quite expensive. 

This product is suitable for pretty much any size of organization. I rate this solution eight out of 10. 

Pega is an Intelligent Automation Platform that has evolved from a BPM perspective. This allows teams using this solution to address complexities without having deep knowledge in a specific development area.

One of the areas of this solution that could be improved would be to improve the low code features of the application itself. We would also like to use the same platform to build any application, even if it is not necessarily defined as a functionality needed by a BPM.

The RPA tool within this solution needs further enhancement to compete with other RPA tools in the market. They are focusing more on the overall platform rather than working on the RPA. Document AI tools could be an added functionality, for example. Alternatively, customers will need to purchase another RPA tool to complement the whole solution if they have very advanced RPA needs across their business.

I have used this solution for one year. 

This is a stable solution. 

This is a scalable solution. 

The technical support is good.

The initial setup was not that complex but also was not that simple.

We often recommend this solution to our customers. It is a wonderful solution. There are not many professionals working with this tool which is important to note.

If the core need of a customer is for BPM and automation, this is a suitable solution. If their needs exceed a BPM solution, such as modernizing different kinds of applications, there may be other suitable solutions. 

This is a good solution from a technical perspective and is based on a very reliable and scalable platform.

I would rate this solution a nine out of ten. 

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.

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.