This package contains all model classes for ewe workflows and workflow instances.
-
Workflow
- {@link com.top_logic.extensions.ewe.model.EWEWorkflow}
- Top model element for ewe workflows. This element holds all
activities, actors, parameters and tickets. In addition it holds
a zipped xml representation of the transition rules used as
input to the zkb.
This element also has a knowledge object representation
in the top-logic knowledge base. This ko is wrapped by the
{@link com.top_logic.extensions.ewe.wrap.Workflow} class.
- {@link com.top_logic.extensions.ewe.model.Activity}
- Models a single activity within a workflow. It holds a reference
to the assigned actor, and lists of all input/output parameters
needed by the activity.
- {@link com.top_logic.extensions.ewe.model.Actor}
- A simple representation of a actor (role/participant) within the ewe.
- {@link com.top_logic.extensions.ewe.model.Property}
- A single unit of information needed by the workflow.
The property also holds information on constraints to its possible values.
Constraints are instances of
{@link com.top_logic.extensions.ewe.model.property.constraint.PropertyConstraint}.
Properties are hanlded by
{@link com.top_logic.extensions.ewe.util.PropertyContainer}s.
See section Property Relations
for the for the classes importan in the context of properties.
- {@link com.top_logic.extensions.ewe.model.ParameterDeclaration}
- A parameter declaration contains the information to refer to a parameter.
The parameter declaration is used as base class for Property,
and by performers to identify the required parameters.
- {@link com.top_logic.extensions.ewe.model.ActivityParameter}
- An ActivityParameter establishes a reference to a parameter. It allows
the activity to refer to the parameter through a local namespace.
- {@link com.top_logic.extensions.ewe.model.ParameterHolder}
- A parameter holder is a set of ActivityParameters. Both Activity and ActivityPerformer
are parameter holders. Whereas an activty performer extends the set of activity parameters
declared by its surrounding activity.
- {@link com.top_logic.extensions.ewe.model.ActivityPerformer}
- A reference to the performer responsible to do the actual work required to
perform the activity.
- {@link com.top_logic.extensions.ewe.model.TicketReference}
- The ticket reference stores the data required to identify tickets
required by workflows.
All above elements also hold information about their representation in the gui
-
Workflow instance
- {@link com.top_logic.extensions.ewe.model.WorkflowProcess}
- An instance of a workflow. It holds a collection of the process activities
in the workflow, a workflow process context, and a workflow process engine
- {@link com.top_logic.extensions.ewe.model.WorkflowProcessActivity}
- A representation of an activity within a workflow process.
It holds a list of workflow process activity instances, one for each
time the activity is activated.
- {@link com.top_logic.extensions.ewe.model.WorkflowProcessActivityInstance}
- Holds Information about a single process activiy activation.
- {@link com.top_logic.extensions.ewe.model.WorkflowProcessEngine}
- Provides the interface to the rule engine. It is used to request the
runnable activities within a workflow process
The {@link com.top_logic.extensions.ewe.model.Property}
Property Relations
{@link com.top_logic.extensions.ewe.model.Property} and
{@link com.top_logic.extensions.ewe.util.PropertyContainer}
have a direct representation in the layout layer.
The {@link com.top_logic.extensions.ewe.layout.constraint.PropertyFormConstraint}
represents a property and handles the validation of the associated constraints.
The {@link com.top_logic.extensions.ewe.layout.constraint.PropertyFormContext}
contains property form constraints for all properties of a given property container.
Additional constraints
({@link com.top_logic.extensions.ewe.layout.constraint.dynamicConstraints.DynamicConstraint},
and {@link com.top_logic.extensions.ewe.layout.constraint.dynamicConstraints.DynamicPropertyConstraint})
can be attached to the property form contex and the property form cionstraint repectivly
to extend the constraints dynamically (e.g. directly on the activity's jsp).
Copyright (c) 2004 Business Operation Systems GmbH. All Rights Reserved.