Implementation of a workflow
The only difference in the implementation of a widget is one additional activity and additional meta information from a workflow.
Create
For creating a workflow and a widget, assistants are available which create a functional workflow or a functional widget. The assistants offer the possibility of creating a workflow or widget by merely setting the name. However, they also offer the possibility of configuring extended settings and of thus setting the meta data of the workflow.
Meta information
Meta information can be maintained directly in the XML of the workflow or widget, as well as in the node “Meta information” below the workflow or widget. Localizations are displayed in the object structure window and localizable settings can be made there.
Activities
Activities can be edited using the Designer or directly in the XML of the workflow. Editing the workflow using the Designer has a number of advantages. For example, if a server activity is created, then the appropriate function for this is automatically defined in the script. The structure of the XML data object can be seen here.
Server activity
A server activity serves for the execution of server-side functionalities. The Jint engine is available for this. When creating a server activity using the Designer, an associated function is defined automatically. If the Designer is not used, then the function must be created in one of the existing server-side Javascript data objects. The function name must be identical to the Id of the activity. Server-side Javascript data objects can be created underneath the “resources” data object.
Dialogue activity
A dialogue activity serves for the output of information and for interaction with a user in the form of a dialogue. When creating a dialogue activity using the Designer, several automatisms are performed. First, the model is created if there is not one already. A model is necessary for the execution of a dialogue activity. Components for displaying the dialogue are bound to this model. Then, bindings to the model are performed and a component associated with the dialogue is created. The default dialogue component is bound to the document and the newly created component is bound to the root element. If the root element is renamed or if additional components are to be bound, then the XML of the dialogue activity must be changed manually. The structure the XML node is described here.
Widget activity
A widget activity serves for the output of information and for interaction with a user in the form of a widget. When creating a widget activity using the Designer, the necessary widget component is automatically created and bound. The structure of a widget component is slightly different from the structure of the Genericform component and is described in more detail here.
Client activity
A client activity serves for the execution of client-side functionalities. When creating using the Designer, the XML element for the client activity is created. The structure of the XML node is described here.
Server-side Javascript
