Ad-Hoc Activities

An ad-hoc activity is an area in which other activities are arranged. These activities are not linked via transitions. During the process, the user defines transitions in enaio® client.

Any number of ad-hoc activities can be added to a model at any position. Alternatively, a model can consist of only one single ad-hoc activity. At least one activity must be added within an ad-hoc activity, though loop activities or further ad-hoc activities are not required.

Examples:

You do not assign applications or participants to ad hoc activities. You do not configure a variable transfer. You can optionally set up dunning periods using the context menu. The user can assign these dunning periods to activities within an ad-hoc activity in enaio® client.

You add activities to an ad-hoc activity in the same way you would add participant activities. You simply do not define transitions. All activities within an ad-hoc activity can be run any number of times.

Use the context menu to define an activity within an ad-hoc activity as a standard activity. It will start first, and it is the one from which the user launches to configure the order of the following activities in a circulation slip. However, the user of this activity can forward data to the activity coming next in the ad-hoc area.

The activity order is not defined, so global variables will forward the data; otherwise they have to be organized via events.