Specifying Data Flows

In the diagram containing the activity and the data element you can map the data as the activity's input and output. There is at least one data flow connection between an activity and a data. The data flow connection is indicated by arrows:

However, Business Process Modeling perspective allows only:

In case multiple data mappings exist between a structured data and an activity, only the first data mapping is displayed.

This chapter covers:

For details on data flow in general, refer to chapter Workflow Data Workflow Data of the Concepts handbook. Concepts Handbook in the Stardust Documentation.

Creating Data Flow Connection

You can create data flow connections using two different ways:

Deleting Data Flow

Hover the mouse in proximity of the data flow connector and click the Delete icon.


Figure: Delete Data Flow

Viewing and Editing Data Flow Properties

To view and edit properties of data flow, perform the following steps:

  1. Click the data flow in the swim lanes. The properties window is displayed at the top-right corner of the swim lane.


    Figure: Data Flow - Properties

  2. Specify the following properties:

Setting Access Points

Access points are named parameters to set or get values associated with a model element at runtime. Refer to section Access Points of chapter Workflow Data of the Stardust Concepts handbook Access Points of chapter Workflow Data of the Concepts Handbook in the Stardust Documentation for details on the concept of using access points in Stardust.

You can select the context from the drop-down list in the Input Access Point and Output Access Point fields. Per default, the Default input and output access points are selected. For application activities, application context access points are provided according to the type of implementation. Refer to the Specifying Applications overview and select the chapter applying to your application for details on setting implementation specific access points.

Application Context
Figure: Input Access Point - Application Context

In an engine context, you can also select Activity Instance.


Figure: Output Access Point - Application Context

Access Point Path

Depending on the type of the access point an input or output access point path can be applied to it.

For example, an output access point path could be a String method to convert a primitive output from a message transformation application to upper case letters:


Figure: Example Output Access Point Path

Importing an Eclipse-based model which contains Java classes

In case you import an Eclipse-based model which contains Java classes and methods associated with Java-type application (Spring Bean, Session Bean etc.), its access points are available for selection in the Web-based modeler. Data paths are not editable for data mapping between Java, Spring Bean and Session Bean applications and data.


Figure: Input Access Point - Java-type Application

Setting Data Access Points for Multiple Instance Tasks

Input and Output Access Points for multiple instance tasks have (List) appended to indicate that the list data iterates for each data element from the list as access point.

Access Point Selection for Multiple Instance Activity
Figure: Access Point Selection for Multiple Instance Activity

For details on the concept of using multi instances activities refer to chapter Using Multiple Instance Activities of the Concepts handbook. Using Multiple Instance Activities of the Concepts handbook.

Setting Data Access Points for Rule Tasks

Data Access Points for Rule Tasks are computed from the Rule Set that is selected for the Rule Task. All data parameters created for the Rule Set are exposed in the Data Flow. For details on Rule Tasks refer to section Rule task implementation of chapter Working with Activities.

For example, a Rule Set IN data parameter CustomerName is provided for a Rule Set that is selected as implementation for the Rule Task.

In Data Parameter
Figure: In Data Parameter for selected Rule Set

This data parameters is provided as In access point for the Rule Task data flow.

Input Access Point for Rule Task
Figure: Input Access Point for Rule Task

The same happens for the OUT data parameters specified in the same Rule Set.

Out Data Parameter
Figure: Out Data Parameter for selected Rule Set

They are provided as Out Access Points for the Rule Task data flow.

Output Access Point for Rule Task
Figure: Output Access Point for Rule Task

Similarly, all In/Out data parameters created in the Rule Set are provided for both, In Access Points and Out Access Points for the Rule Task.

Data Mappings in Process Interface Context

The Process Interface Context is needed when one model is referring to another model through exposed process interface. Suppose the referred subprocess has IN parameters defined and it returns the result. Then, in this case. the called process should know the IN and OUT parameters. So if the referred process has exposed the parameters then you need to provide the data mappings in the process interface context.

Note that the data type specified in the formal parameters should match with the data type specified in the consumer model. For example, you have defined structure data type in the provider model. To access the same structured data in the consumer model, you need to drag and drop the structured data and reference through the data mappings.

To specify the process interface context, perform the following steps:

  1. Create the data flow between the referred subprocess and the data
  2. Click the data flow connection


    Figure: Data Flow - Referred Elements

  3. Specify the data path in the Input Data Path text box.
  4. In the Input Access Point drop-down list, from the processInterface option select the specified parameter. If Input check box is selected, then only this field is enabled.


    Figure: Input Access Point - Process Interface Context

  5. Similarly, you can specify Output Access Point if the Output check box is selected.