|
| Copyright © Cloud Software Group, Inc. All Rights Reserved |
Table 4 Example activities
•
•
−
−
•
•
• Configuration — Used for general configuration of the activity. For example, this tab specifies the adapter service to use for an Adapter activity.
• Advanced — Any advanced configuration parameters are specified here.
• Event — For activities that wait for incoming events, such as HTTP requests or incoming TIBCO Rendezvous messages, this tab specifies the timeout for the incoming event and a condition to determine whether the incoming event is the correct one for the specific process instance.
• Editor — A data schema for the activity. This is used when the input or output data is not known by the activity, and the user must specify their own schema. Once specified, the schema becomes available on the Input, Output or both tabs of the activity.
• Input — The output data from all activities that precede this activity in the process definition is available for mapping to this activity’s input schema.
• Output — The activity’s data is output to activities that follow in the process definition.There are two activities that are included in a process definition by default: the Start activity and the End activity. See Start Activity and End Activity for more information about these activities.
|
| Copyright © Cloud Software Group, Inc. All Rights Reserved |