You need to deploy and link activities on the canvas and define their details.
The following table describes the activities that can be defined and their definition contents.
Table 5-12 Activities that can be defined
Activity | Definition |
---|---|
Start | Indicates the start of a business process. |
Receive# | Defines an interface for receiving a request message from a service requester. |
Reply# | Defines an interface for returning a response or fault to request messages received synchronously from a service requester. |
Invoke service# | Defines the transmission of a request message to a defined HCSC component. |
Invoke Java | Defines the invocation of a Java class that implements a dedicated interface. |
Data transformation | Defines data transformation processing. |
Assign | Creates definitions for executing the following processes:
|
Empty | Defines that the activity does nothing even if executed. |
Throw | Defines a fault notification to a higher-order scope activity. |
Standby# | Defines the process for putting a process flow in standby mode at regular intervals or until a certain time limit. |
Validate | Validates messages transferred within a business process. |
Scope | Defines a process flow consisting of one or more activities as a single unit (scope). |
While | Defines repetitive processing of one or more activities under specified conditions. |
Switch (Start) | Defines switching of the processing of a business process according to the result of a conditional expression. The switching start and end points must be defined. |
Switch (End) | |
Flow (Start) | Defines the division of a processing flow into multiple sequences and the concurrent execution of these sequences (parallel processing of a flow). The flow start and end points must be defined. |
Flow (End) | |
End | Indicates the end of a business process. |
The following subsections provide details of the definition of each activity.