Red Hat Polymita Business Suite Overview

What is Red Hat Polymita Business Suite?
Red Hat JBoss BPM Suite combines business process management (BPM), business rules management (BRM), business resource planning, and complex event processing (CEP) technologies into a single, integrated, open source platform. JBoss BPM Suite lets project stakeholders collaborate to build business automation solutions with a choice of modeling tools. This includes a web-based authoring environment for business experts and an Eclipse plug-in for developers. A rich set of tools for process and decision management covers the full process life cycle - from modeling, simulation, and testing to deployment, monitoring, and optimization. Process and decision logic can be modeled and automated together, without the need to learn multiple tools or develop custom integrations between disparate environments.

Red Hat Polymita Business Suite is also known as Polymita Business Suite.

Buyer's Guide

Download the Business Process Management Buyer's Guide including reviews and more. Updated: May 2021

Red Hat Polymita Business Suite Customers
Bayer, Grupo Televisa, RCBC, Peavey
Red Hat Polymita Business Suite Video

Filter Archived Reviews (More than two years old)

Filter by:
Filter Reviews
Filter Unavailable
Company Size
Filter Unavailable
Job Level
Filter Unavailable
Filter Unavailable
Filter Unavailable
Order by:
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Showingreviews based on the current filters. Reset all filters
Luis Yndigoyen
Partner at a tech services company with 11-50 employees
Real User
Gives you the ability to design the screens outside the software and connect them as a component with the BPM engine

What is our primary use case?

In Latin America, a common business case is in banks, for onboarding clients and credits approval, also the government and insurance, lately. During the last three or four years insurance companies have come to use it more.

Pros and Cons

  • "The main factor that separates Red Hat software from Oracle, IBM, Pegasystems, is the ability that it gives you to design the screens outside the software and connect it as another component with the BPM engine."
  • "I think the documentation for the tool, the official documentation, is not as strong as in other tools. You have lot of community. That is good. But sometimes you need - when you are working on a big client or a critical process - to be certain about certain things. So I think that the documentation for the tool, from the company, could be a little stronger."

What other advice do I have?

I would recommend for any BPM implementation - and I have been dedicated to this the last 11 years - that you have a very clear objective, the goal of the BPM implementation. It's not the tool for the tool's sake. The end of the project is not the project itself or the tool itself. The end must be, "Okay this process is from this current condition, has these performance indicators, and I want to obtain this improvement. If the process is taking three days I want it to take one day. If the process is costing $100, I want it to costs $40. If the process requires 10 signatures, I want to apply…