The Oracle Business Process Management Suite is an integrated environment for developing, administering, and using business applications centered around business processes.
N/A
ProcessMaker
Score 9.0 out of 10
N/A
ProcessMaker is a business process management and workflow automation platform. It uses a drag-and-drop interface to build workflows to drive automation.
Oracle BPM is well suited to organizations and environments that have a good understanding of their business processes and organizational structures. Trying to introduce a tool such as Oracle BPM into the organization without a good grasp on how the business operates is a recipe for disaster as the implementation will uncover all of the dirty secrets of an organizations business processes and bring them to light. BPM is not to be utilized for smaller service orchestrations or technical service implementations, these should be handled by the Oracle SOA Suite using the BPEL process manager, leaving BPM to handle the organizational business processes, referring to and including lower level services and BPEL processes as needed.
I loved it. You will not get an easier interface. You can develop workflow processes in a simple way, one which allows anyone to understand what you are trying to accomplish; however, you will get into some issues if your employees are scared of coding (when you get to the advanced features). For some, this will never be an issue as the knowledge you need is very basic. But for the school I was working with, it would have stopped them cold
We can write PHP and Javascript code to handle the way the ProcessMaker does. It makes the ProcessMaker more flexible to meet our requests on our workflow.
The Processmaker provides a What-You-See-Is-What-You-Get flowchart design tool, we can draw our process very easy like Visio. And, We can use the flowchart to implement our workflow.
Also, the Dynaform, the electronic form function of Processmaker, is WYSIWYG form design tool, help us design forms participated in the process.
Oracle BPM is left behind by other tools more modern in terms of user experience, usability and ability to integrate with everything else.
To really harvest the potential of Oracle BPM you need to do it in JDeveloper and with ADF. This restricts its usage to very technical people.
The administration of the Oracle BPM tools has really put a burden on our team. It is running on Weblogic and we experience issues very often either with performance or with a bad configuration of the system.
As with all Oracle products, the price can be an issue for smaller shops.
We evaluated Bonita and found that it might fit a smaller-sized company better; we found that Oracle BPM Suite scaled much more evenly. We almost went with one of the competitors, but in the end chose Oracle BPM Suite after we factored in the cost of VMware licensing. There are literally tons of analytics on the back end which are great for upper management, but not so much for average users, but this fits our business model quite well.
Before making the decision to get ProcessMaker, we assessed different and best options in the market, which are also quite competitive. KiSSFLOW, Blueworks Live, and Bizagi, being the most relevant and ADONIS, to mention the ones we consider the most relevant and capable of meeting our needs. In the end, we went for ProcessMaker because of mainly three things as described before: 1. Real-time process status tracking. 2. Metrics and dashboards. 3. Ease of use for constructing diagrams.
You'll most certainly need a deep dive and extensive training before your users can even think of using the product and they are very expensive.
Lack of documentation makes it very difficult to manage the application if any error is encountered which will result in you ending up hiring a dedicated person to look into the application once it's deployed.
For a very large org., if properly implemented and used, it can help identify the cost-intensive and inefficient processes.
This would have been the easiest program to implement. It would have been the quickest, and the one that most of the employees would have been able to master. That alone would have saved countless dollars in time investment.
Unfortunately, the environment doesn't support knowledge of coding. So, they would never be able to advance further than a certain degree before having to bring someone else in again. It would have saved money at first, but then would have ended up costing in the long run.
