This packages provides the integration of ewe in the Top-Logic layout framework.

The basic layout for the ewe consists of a Worklist ({@link com.top_logic.extensions.ewe.layout.WorklistEntryTableComponent}) paired with a Task-View ({@link com.top_logic.extensions.ewe.layout.TaskLayoutContainer}). The Worklist presents the Task currently scheduled for the current user, the Task-View presents an adequate Layout to work on the selected task. The various Workflows in the system provide specific layouts.

Simple Task-Layout

TTS Task-Layout

E.g. the sub-package {@link com.top_logic.extensions.ewe.layout.tts.view} contains some layout classes providing a layout for Trouble-Tickets and mates with the layout and behavior known from the TTS 1.1.2.

The {@link com.top_logic.extensions.ewe.layout.tts.view.PerformerResultComponent} presents the result of the invocation of an {@link com.top_logic.extensions.ewe.model.ActivityPerformer}. The {@link com.top_logic.extensions.ewe.model.ActivityPerformer} returns a result code (int) and additional data via a {@link com.top_logic.extensions.ewe.performer.PerformerContext}. The {@link com.top_logic.extensions.ewe.layout.tts.view.PerformerResultComponent} gets invoked only if the activity is not completed. If the PerformerContext contains an url to a jsp, this jsp is presented. The PerformerContext can also contain {@link com.top_logic.tool.boundsec.CommandHandler}. If so, the command handler replace the standard commands of the performer result component. See the image below for the process of activity invocation and the handling of the result via the performer result component.


Copyright (c) 2003-2004 Business Operation Systems GmbH. All Rights Reserved.