What needs improvement with Oracle BPM?

The stability of this solution deteriorates when more than one thousand instances are concurrently active.

The Oracle database is not an easy product to maintain.

I would like to see the next version of this solution be simpler and more transparent about what is happening at the level of the database. This would allow users to better understand problems.

The technology that is being used for the UI needs to be updated to make it quicker. Oracle is using the ADF technology, which is a very heavy framework. Oracle cloud uses the JET framework, which is much faster and consumes fewer resources.

Oracle needs to return some of their focus to the Fusion products, rather than concentrating so heavily on cloud-based technologies.

Overall, the engine and the UI both have to be made lighter. 

Click Here https://mindmajix.com/oracle-bpm-training  to Learn Oracle BPM Certification Course.

Oracle BPM could probably be improved with respect to the cost. When you are using this product, it'll be a bit costlier for the ROA. I think they should do some discounts on these products, especially for the licenses.

From my knowledge of this solution, I don't see that the Oracle BPM includes features such as the growth of discovery and process mining. Technical support could be better. In the next release, I would like to see the growth of discovery and process mining features added. Also, the ability to be containerized, and to support the cloud-native deployments.

The solution needs to offer better integration with third-party systems. The solution should focus more support towards new department methods that assist with the architecture of the deployment itself.

We have had some issues with version migration, from one version of processes to another. We would have to call Oracle Services but on a day to day, we didn't have any issues. I would like for the design of the migration of process instances from one version to another to be more visual. It would be very helpful to have visual tools in order to design the equivalence of tasks and process payload between versions. Until now bpm database migration has been needed. I would also like more UI flexibility, the ADF framework is too Oracle-specific.

The stability of this solution deteriorates when more than one thousand instances are concurrently active. The Oracle database is not an easy product to maintain. I would like to see the next version of this solution be simpler and more transparent about what is happening at the level of the database. This would allow users to better understand problems. The technology that is being used for the UI needs to be updated to make it quicker. Oracle is using the ADF technology, which is a very heavy framework. Oracle cloud uses the JET framework, which is much faster and consumes fewer resources. Oracle needs to return some of their focus to the Fusion products, rather than concentrating so heavily on cloud-based technologies. Overall, the engine and the UI both have to be made lighter.

The API interfaces could be more robust. Existing APIs in the product need to be fine-tuned, made more robust and flexible for adoption. The product should be made available with all its current capabilities addressing known shortcomings on the cloud. I would like to see current out-of-the-box MIs enhanced, offering more interactive capability. Introduce machine learning and AI capabilities. Change the front end and the ability to offer forms for business users.

In the future, the market is consolidating towards microservices approaching software development product. Microservices can be the future of programming, and the old way of doing middleware and implementing middleware services could shift to the microservices side, so we will need some hybrid solutions. At this time, we use the microservices, and microservices will support external digital applications that we publish on mobile and website. We will keep using the middleware side for delivery and back office systems. Therefore, it will not be 100% microservices or it will not be 100% middleware, but instead we are going to use a hybrid approach where some parts use microservices. Thus, it would be good if they could provide some additional connectors or an application developer environment for microservices. It could have easier administration. It takes time to configure and deploy. We need more team messaging buzz, like Kafka. People do so much business and logic coding in an ESP site, but what we need more of is lightweight messaging mechanisms, like Kafka. This is also the trend. We need some type of pretense for best practices for new generation programs, which can serve digital customers.

Support for Decision Modelling Notation (DMN). There is a Business Rule Engine available, but this is not DMN-compatible.

Although it is a robust product, its learning curve can be steep without having the proper training and mentoring on the first project. As with most BPM projects interaction with people is a key element. Creating user interfaces the end users see and interact with as work item instances travel through process can be challenging. If ADF is used, most companies struggle due to its complexity, steep learning curve, and the need to tune it for performance. The web form design tool in Composer (currently an OEM product from Frevvo) is simple to use for citizen developers, but can be lacking in the functionality most projects need. To get around these issues, the architecture is flexible enough to allow the use of other UI technologies. On new projects we now create and edit forms using Angular JS using REST services. This has made our developers much more productive and the forms perform better.