Overview to the embedded workflow engine (EWE)

This package provides a workflow driven controlling of activities embedded in the Top-Logic framework.

The central controlling class is the {@link com.top_logic.extensions.ewe.EWEDriver EWEDriver}. It manages the available workflows and the instances (process).

Workflows and instances both have a representation in the {@link com.top_logic.extensions.ewe.model ewe model world} ({@link com.top_logic.extensions.ewe.model.EWEWorkflow} and {@link com.top_logic.extensions.ewe.model.WorkflowProcess} respectively) and in the Top-Logic knowledge base ({@link com.top_logic.extensions.ewe.wrap.Workflow} and {@link com.top_logic.extensions.ewe.wrap.WorkflowInstance}). The ewe model side handles the persistancy and the logic mainly, the top-logic side handles the security (actor mappings, and roles) and keeps the associations to other knowledge objects.

The data of workflow properties is handled via the {@link com.top_logic.extensions.ewe.util.WorkflowInstanceDataContainer}. It stores the workflow specific data via the {@link com.top_logic.extensions.ewe.Persistency} given by the {@link com.top_logic.extensions.ewe.EWEConfiguration}. It also manages the delegation of data of external properties (e.g. given via a ticket) to their respective {@link com.top_logic.extensions.ewe.util.PropertyContainer}.

There are some central components for the user interface of the ewe. The {@link com.top_logic.extensions.ewe.layout.WorklistEntryTableComponent} provides a user with a view of all activities currently pending to be performed by him. If the user selects an activity, the {@link com.top_logic.extensions.ewe.layout.WorklistEntryContentComponent} provides a view of the activity and the means to start the performance of the activty. The {@link com.top_logic.extensions.ewe.layout.PerformerResultComponent} finally provides a view of the result of the performance. A core feature therby is to view an arbitrary page given as a result from the performer and providing buttons to interact with the activity (commit, store, ...). E.g. the {@link com.top_logic.extensions.ewe.performer.JSPViewPerformer} provides a specific jsp page based on the id of the calling activity.