uCosminexus Service Platform, Basic Development Guide
Linking two activities deployed on the canvas defines a business process execution sequence.
The following types of links can be used for activities:
How the linking line is displayed on the canvas differs depending on the linking method. The following table describes the relationship between linking methods and linking lines.
Table 5-1 Linking lines displayed on the screen
Linking method | Linking line displayed | Line color | Line type | Termination |
---|---|---|---|---|
Link based on connection | Black | Solid line | Triangular arrow | |
Link based on fault connection | Red | Broken line | Triangular arrow | |
Link based on link connection | Blue | Dotted line | Line arrow |
To link activities:
To change an already specified link, drag and drop the starting point or termination point of a linking line into another activity.
You can bend and display linking lines. You can use this operation to rearrange the linking lines on the canvas when the links among activities become complex. The method for bending linking lines is described as follows:
Whether an activity can be used as a link source or link destination differs depending on the type of activity and the link used. The following table describes activities that can or cannot be used as link sources or link destinations.
Table 5-2 Activities that can or cannot be used as link sources or link destinations
Activity | Connection | Fault connection | Link connection | |||
---|---|---|---|---|---|---|
Link source | Link destination | Link source | Link destination | Link source | Link destination | |
Start | Y | -- | -- | -- | -- | -- |
Receive | Y | Y | -- | Y | Y | Y |
Reply | Y | Y | -- | Y | Y | Y |
Invoke service | Y | Y | Y | Y | Y | Y |
Invoke Java | Y | Y | Y | Y | Y | Y |
Data transformation | Y | Y | -- | Y | Y | Y |
Assign | Y | Y | -- | Y | Y | Y |
Empty | Y | Y | -- | Y | Y | Y |
Throw | -- | Y | -- | Y | Y | Y |
Standby | Y | Y | -- | Y | Y | Y |
Validate | Y | Y | -- | Y | Y | Y |
Scope | Y | Y | Y | Y | Y | Y |
While | Y | Y | -- | Y | Y | Y |
Switch (Start) | Y | Y | -- | Y | Y | Y |
Switch (End) | Y | Y | -- | -- | -- | -- |
Flow (Start) | Y | Y | -- | Y | Y | Y |
Flow (End) | Y | Y | -- | -- | -- | -- |
End | -- | Y | -- | -- | -- | -- |
When activities are linked through a connection, an activity that becomes the transition source to another activity is called a transition-source activity, and an activity that becomes the transition destination from another activity is called a transition-destination activity.
The number of transition-source activities and transition-destination activities that can be linked using a connection (excluding fault connections and link connections) varies according to each activity.
The following table describes the number of transition-source and transition-destination activities that can be linked for each activity.
Table 5-3 Number of transition-source and transition-destination activities that can be linked
Activity | Number of transition-source activities that can be linked | Number of transition-destination activities that can be linked |
---|---|---|
Start | 0 | 1 |
Receive | 1 | 1 |
Reply | 1 | 1 |
Invoke service | 1 | 1 |
Invoke Java | 1 | 1 |
Data transformation | 1 | 1 |
Assign | 1 | 1 |
Empty | 1 | 1 |
Throw | 1 | 0 |
Standby | 1 | 1 |
Validate | 1 | 1 |
Scope | 1 | 1 |
While | 1 | 1 |
Switch (Start) | 1 | 1 or more |
Switch (End) | 1 or more | 1 |
Flow (Start) | 1 | 1 or more |
Flow (End) | 1 or more | 1 |
End | 1 | 0 |
All Rights Reserved. Copyright (C) 2015, Hitachi, Ltd.