TIBCO iProcess Suite Reviews

It's very simple to use and the integration features between Java and other services within the workflow are very easy. We're looking for something else because the licensing model they have is too expensive. We want something that's not specific to Java customization. I'm not that familiar with TIBCO, so right now I'm just telling you what I've heard from my colleagues. These are the key points that they raised. 

Currently, we have a mixed environment between Java web services and other network services. Mainly, the guys that are actually running the code are saying that the services that have been developed on the internet are experiencing some integration issues. That's the reason why we initiated an evaluation for other products.

It involves a lot of investment. The learning curve is not similar to other products, like K2. Regarding the user interface, I have to access workflows and define and manage the processes on the variant of a Windows application, which is not accessible if you don't have access from the client to install it on the workstation. And most of the solutions we're currently evaluating are web-based. Our customers and developers have complained that the UI is a little bit confusing. It has lots of elements. It's not user-intuitive compared to other products. Other than that, the licensing model is our main concern. 

The Conductor and Decision features of the product are the backbone of the product because it enables the user to create a custom ruleset which can be used to implement the order orchestration.

For order fulfilment and service configuration the tasks are assigned to the Engineer, and once the Engineer completes the task, then closes the task assigned to him with his comments.The flow then goes to the next task and so on, this improved our turnaround time and manual effort. This also partiallyautomates the process (as much as possible).