IBM BPM Reviews

• The process creation
• Task creation
• User management
• Task allocation
• Rich UI and third party integration

The above features have helped me to build a successful application.

It has reduced the time a human spends in completing the jobs using spreadsheets and other traditional methods.

There are a few areas, like triggering mechanisms, externally exposed variables, and changing its values, which need to be revisited, as they do not sometimes function properly. However, this is a rare scenario.

Seven years.

No, it is highly stable.

No.

I would give their technical support an eight and a half out of 10 as a rating.

No, I did not previously use a different solution.

The initial setup is quite simple and user-friendly to perform.

I am unclear about the pricing and licensing as I do not deal with such matters. I only develop things from the tool.

Not applicable to me.

If you are looking for a product which should be capable of handling SOA principles, third-party integration, and effective user management, I highly recommend this product for you.

• Very easy test management
• Good import/export features
• Very good JIRA integration
• Great customer support
• Good report templates, which are very easy to use.

• Shortened time for test management 
• Saved time in QA team communication and collaboration

• Import/export of attachments 
• Transfer of attachments to/from JIRA

Three years.

Not at the moment.

Not at the moment.

Currently, I am using the latest cloud version on my current project. On previous projects, I have used in-house solution.

I mainly use BPM to automate our internal workflows.

BPM helps us with automation and with assigning and delegating tasks.

The most valuable feature is the ability to customize your rules and put them inside the tool. I also think BPM is easy to do development on.

An area for improvement would be the user interface of the portal itself.

I've been using IBM BPM for around four years.

BMP is scalable both horizontally and vertically.

The configuration is not that easy, and the initial deployment took three months. I'd give my experience with setting up a rating of three out of five.

I used a third-party team to implement.

The pricing is quite high, I would rate it two out of five.

I would rate this solution as seven out of ten.

We use IBM BPM for AC Kronos process management to use for calls and users. 

I like the APIs and the BPM Coach is a good tool. But if I had to pick one, it would be the API.

The push notifications are also good. 

The debugging needs improvement. There is some confusion surrounding the debugging.

They should also improve the APIs.

I have been using IBM BPM for four months. 

It is scalable. No bugs or glitches. 

We don't use it in the production systems right now. We're just using it in the pilot mode. 

Our teams work on scalability and I think it is good. It's based on IBM vSphere, and the scalability is good.

It's used by around 10,000 people and around 15 developers.

IBM's technical support is not enough. We don't get good responses from technical support.

The initial setup was straightforward. It's automatic, then you compress it.

It took us around one day to install it. 

My advice would be to use an open-source solution. It would be more valuable than IBM. Our company is based on IBM. IBM is good for our needs but I wouldn't recommend it for an old age company. An open-source product would be better. 

I would rate IBM BPM an eight out of ten. 

The possibility to add Java code as embedded .jar, that increases the flexibility of the solution.

BPM products are there to optimize the business flows in mid to large organizations. IBM BPM does that pretty well. Currently we use it for the automation of virtual machine provisioning in private clouds.

• The user interface builder could be more powerful and easier to use.
• The real-time process reporting functionality is limited to human activities – there is no visibility over the system tasks.
• IBM BPM uses JavaScript as a programming language for the server-side. I don’t know why it’s not Java, as it’s more powerful and the JavaScript part is translated into Java anyway.
• Sending complex data from the user interfaces to the server side is not achieved easily.

Three years, constantly.

No, stability is good, even with hundreds of new process instances per day.

Scalability depends greatly on the application server, WebSphere Application Server in this case. I haven't encountered any issues so far.