Aperte Step Editor is part of the Aperte Modeler Editor window, focused on providing functionality to design the graphical user interface using widgets and configure automatic process steps.

Aperte Step Editor is tightly integrated with Aperte Workflow runtime infrastructure. It requires a fully working and running Aperte Workflow installation to be accessible via HTTP to the step editor. Otherwise, the editor won't function. Although this may introduce certain restrictions, it allows the editor to browse all the widgets and automated steps deployed as OSGi bundles.

Because the editor needs to be applied to existing process step, it's only available from the element shortcut menu. The editor presence is indicated by the Aperte Workflow logo, usually on the bottom of the element.

Human task

Aperte Step Editor can be invoked on any task node. This operation is shown below:

Upon accessing the Aperte Step Editor on a task a new popup window is opened. The window is split into three tabs:

• User Interface Definition
• Assignment
• Permissions

Tabs are described in subsequent sections.

User Interface Definition

This tab is used to create user interface, consisting of hierarchy of widgets. User is able to drag and drop available widgets and configure them to create a desired hierarchy tree. Widgets are provided as plugins, so for detailed description please refer to plugins documentation on this wiki .

Image below shows User Interface Definition tab's overview.


Assignment

Assignment tab provides means to edit step assignment attributes, which are not directly represented in the Aperte Modeler Editor window.


Permissions

This tab allows to configure access to the task, for example Search permission allows process instances in this task to be found by users with specified roles.


Automated step

Aperte Step Editor can be invoked on any automatic step. This operation is shown below:

Upon accessing the Aperte Step Editor on an automatic step a new popup window is opened. The window allows to edit step attributes that are not directly represented in the Aperte Modeler Editor window. These additional attributes are then stored inside Aperte Configuration attribute.