Juan Gonzalez P:
Hi again Cyprian,
Is this a "layer" between BPM engines and Liferay, or it has a built-in engine in it? (like Kaleo).
Thanks!
Hi Juan,
Aperte Workflow utilizes existing BPM engines (just like Liferay can run with Kaleo, jBPM, Activiti, ...), but it is done independently from Liferay's workflow configuration. Currently released version of Aperte Workflow comes bundled with jBPMv4.4, but in the near future more BPM engines will be supported.
To better understand Aperte Workflow you might think of elements required to put an enterprise BPM application together. You need a BPM engine (obviously), you need users management/security/layout (that's Liferay), you need a place for custom UI components coming from business requirements (Vaadin), you need to model your data (Hibernate) and to provide some kind of integration with external systems (e.g. Mule ES

.
And Aperte Workflow can be seen as some kind of "glue" or integration between these software components - done once and done right (I hope), so that you don't have to do it by yourself no more - and also benefits from things that might be missed or neglected in custom BPM application deployment, such as: modeler, Business Activity Monitoring and finally reusability of components on all levels.
But even if it is a ready-to-use product, Aperte Workflow is still designed to be as as much open to customizations as it is possible. OSGi plugins deployed in Aperte Workflow, can do more than just render UI or call your legacy system - they can provide i18n settings, they can support other plugins (e.g. Mule Plugin detects and deploys simple Mule services provided by other plugins). It is really up to your imagination what you might do with a given API. But still, you have a rock-solid foundation for you BPM deployment.
A lot of information is available at the
project Wiki, it is also very easy to just download
installation/
demo bundle and see Aperte Workflow for yourself

Best regards,
Tomek Lipski