This presentation was given at the Liferay European Symposium 2011 at Frankfurt am Main, Germany. Aperte Workflow is an Open Source BPM-class solution delivering capability to quickly and easily implements business process in the enterprise. Aperte Workflow combines in a unique way agile BPM engines with rich user interface and state-of-the art integration with external applications. This combination allows to create BPM/Workflow solutions in the spirit of SOA.

1. Building complete workflow solutions with Liferay Tomek Lipski Chief of R&D, BlueSoft, Poland @tomeklipski

3. Aperte Workflow – more than just BPM

4. Choosing right tools

5. The frontend – focus on usability and user experience

6. The platform – where modularity is #1 goal

7. The backend – BPM engine, persistence, integration

8. How do these tools combine into a complete workflow solution

9. The process

10. Automated steps

11. Human tasks

12. Other mechanisms

13. Seeing the benefits

15. Mostly Java-based solutions

16. Largest enterprise integration team in Poland

18. We became Liferay Service Partner in 2011

20. Business processes built from reusable components

21. Multiple BPM implementations supported

22. Liferay 6.0 as a base

23. Plugin mechanism backed by OSGi stack

24. Enterprise integration ready

25. Rich User InterfaceAperte Workflow is available under GNU Lesser GPL: https://github.com/bluesoft-rnd/aperte-workflow-core

27. Stable and clean relashionship with tools’ vendors

29. They provide features you might never think of

30. It is easier and safer for potential users to learn and use a solution based on components they are already familiar with… but when no good tool exists, do not hesitate to develop one!

32. Introduce new portlets and features

34. No HTML/CSS/JavaScript hassle in most cases

35. Great for plugins – management, development, etc.

36. Security and control

38. Ready to use and complete plugin system

40. Automated steps

41. Process definitions

42. Internationalization (I18N)

43. Custom mechanisms

46. Simple Mule services can be deployed as Aperte Workflow OSGi plugins

49. Every implementation of BPM interface fulfills simple API with basic operations

50. Human tasks, process state, process history, etc. are all available to other compenents/plugins

51. Process data available outside of BPM implementation

53. Each OSGi plugin has seperate classloader, which resolves most of the dependency conflicts

55. Generate a document from process data

56. Invoke Web Service using Axis

57. Use MuleClient to invoke Web Service

59. User interface is composed from widgets and action buttons provided as plugins

60. Widgets can perform differentroles:

61. Arrange other widgets

62. Provide generic operations on process data

63. Integrate with external systems (e.g. LDAP or ECM)

64. Action buttons allow the user to make a decision in a process

67. The plugins can be used to provide process components

68. Other mechanisms can be introduced, for example:EMAILCAPTURE PROCESS STATE NOTIFICATION RESTAPI Start process instance or propagate its execution when certain email is received. Notify task owner or any other recipient that a certain process instance has entered designated process step. Provide access to Aperte Workflow’s API using REST. (...)

70. Use a set of pre-built features and plugins

72. Provide any feature you require

74. Existing user base and communities

76. Questions & Answers More information: http://www.bluesoft.net.pl/aperte-workflow https://demo.aperteworkflow.org/ https://github.com/bluesoft-rnd/aperte-workflow-core http://www.bluesoft.net.pl