I am trying to understand the positioning of the UI web applications, and in particular the Task UI, to know if we could perhaps reuse it for basic needs:
However, I didn’t find a lot of documentation concerning the “App” concept in modeler/task, except from the 6.3.1 release notes where it’s described as now “first class citizen” engine: is it now comparable to other Flowable engines?
Basically, I have a Java application that embeds Flowable engines (it is a classical Spring application, with auto deployment of a process, some decision rules, and ideally some forms), and I would like to add an UI for the deployed processes and forms.
Is there a way to use the “AppEngine” programmatically like the other flowable engines, in order to deploy automatically an app with the processes and forms auto-deployed in the other engines from the same Java application?
Or otherwise, would there be an easy way to use the ui task module without the “app” concept, showing only what is deployed from the same DB?
(our goal is not to be able to use a front to change the process, we don’t mind repackaging our code when we have changes)
I understand that the UI apps are made for demonstration purposes and that we will probably need to write our own front, but I would like to understand to which extent we could reuse some parts of task app for internal needs.
Also, I would like to keep an “embedded” approach: ideally one Java application (of course dividing the front and backend is not a real issue), we have an agile/feature teams approach and we do not want to have one front used for multiple teams that would create dependencies and complications like with more centralized BPM engines.
Thank you for your help,