Activity Icons

Copyright © Cloud Software Group, Inc. All Rights Reserved

Activity Icons

Each activity is represented by an icon in the palette and design panels. These icons represent the function of the activity. There are some common elements of activity icons that represent the type of activity and the direction of data between the activity and the process.

Table 5 describes the various elements in activity icons.

Table 5 Activity icon elements

Element

Example

Description

Arrows indicate the direction of information between the process and the external system. Multiple arrows indicate either sending or receiving data, as opposed to performing an operation (see the description of single arrows below).

In the example, the information is flowing from the process to the adapter (the adapter is represented by the purple and blue sphere).

A green circle with an arrow inside (similar to a "Play" button on a media player) indicates the activity is a process starter. These activities start new processes based on the receipt of an event from the external system. See Process Starters for more information about process starters.

A yellow square with two parallel lines inside (similar to a "Pause" button on a media player) indicates the activity waits for an incoming event from the external system.

These activities, also known as "Event activities" cause the process to suspend until the incoming event is received. See Event for more information about Event activities.

A single arrow going into or out of the external system indicates that the activity is performing a request, sending a response, or performing a request and receiving a response.

This is different from simply receiving a message or data (indicated by multiple arrows) because the activity is performing or responding to a remote operation call.

The direction of the arrow indicates whether the activity is receiving a request, sending a response, or sending a request and receiving a response.

In the Invoke an Adapter Request-Response activity example, the activity is sending a request to an adapter and expects to get a response from the adapter.

In the Adapter Request-Response Server activity example, the activity starts a process based on the receipt of a request from an adapter.

In the Respond to Adapter Request activity example, the activity is sending a response to a previously received adapter request.

Element	Example	Description
		Arrows indicate the direction of information between the process and the external system. Multiple arrows indicate either sending or receiving data, as opposed to performing an operation (see the description of single arrows below). In the example, the information is flowing from the process to the adapter (the adapter is represented by the purple and blue sphere).
		A green circle with an arrow inside (similar to a "Play" button on a media player) indicates the activity is a process starter. These activities start new processes based on the receipt of an event from the external system. See Process Starters for more information about process starters.
		A yellow square with two parallel lines inside (similar to a "Pause" button on a media player) indicates the activity waits for an incoming event from the external system. These activities, also known as "Event activities" cause the process to suspend until the incoming event is received. See Event for more information about Event activities.
		A single arrow going into or out of the external system indicates that the activity is performing a request, sending a response, or performing a request and receiving a response. This is different from simply receiving a message or data (indicated by multiple arrows) because the activity is performing or responding to a remote operation call. The direction of the arrow indicates whether the activity is receiving a request, sending a response, or sending a request and receiving a response. In the Invoke an Adapter Request-Response activity example, the activity is sending a request to an adapter and expects to get a response from the adapter. In the Adapter Request-Response Server activity example, the activity starts a process based on the receipt of a request from an adapter. In the Respond to Adapter Request activity example, the activity is sending a response to a previously received adapter request.