8.1.2 Workflow integration in Daisy

8.1.2.1 Workflow component in the repository server

The picture below illustrates how the workflow is implemented as an extension component in the Daisy repository server. “Extension component” means that the workflow can be disabled without any impact on the core repository server, and its code base is completely separated from the core repository, the workflow only communicates through official APIs/SPIs with the repository.

As discussed in the section on deployment, we have set up jBPM so that it stores its data in the same relational database as the Daisy repository server.

8.1.2.2 Daisy workflow API

Daisy defines its own Workflow API. This not only hides the underlying implementation, but allows to layer additional functionality (such as access control), and to provide a remote implementation.

One of the neat features of the Daisy Workflow API is its generic query system.

8.1.2.3 Daisy Wiki integration

Next to the workflow extension component in the repository server, the Daisy Wiki provides a complete workflow GUI, including:

• administration screens to deploy process definitions and manage workflow pools

• workflow console (dashboard) showing the tasks assigned to the current user and pooled tasks for the user

• the necessary screens to start workflow processes and perform workflow tasks

• search screens for processes, tasks and timers

• and the obvious little things like deleting/suspending/resuming process instances, viewing the complete details of a process instance, (re-)assign tasks, view timer details (including exception if timer failed), ...