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:

• If an activity has input data flow connection then the flow is labeled with an arrow to the activity.
• If an activity has out data flow connection then the flow is labeled with an arrow to the data.
• If an activity has both input and out data flow connections then both the arrows are drawn.

However, Business Process Modeling perspective allows only:

• One input data mapping
• One output data mapping
• A pair of the two, per data

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

This chapter covers:

• Creating Data Flow Connection
• Deleting Data Flow
• Viewing and Editing Data Flow Properties
• Data Mappings in Process Interface Context

Creating Data Flow Connection

You can create data flow connections using two different ways:

• In the toolbar, click Create Connector icon and connect data with activity


Figure: Create Connector Icon

OR

• Hover the mouse in proximity of already added data in swim lanes and click the Connect icon in the flyout menu


Figure: Create Connector - Data Flyout Menu

• Connect data with activity in the swim lane

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:
   • UUID - A unique identifier ID gets generated as an identifier for client server communication
   • ID - An ID generated automatically based on the data flow name. If element with the same name exists then during ID generation, a numerical suffix gets added to the ID. If the element is renamed, the ID gets regenerated.

   The UUID and ID options are displayed only when you switch to Integrator profile.

   • Name - Specify name of the data flow
   • Input - Select this check box to specify in data flow. If the input data flow is created while connecting activity with data then this check box is selected by default.
   • Output - Select this check box to specify out data flow.
   • Input Data Path - Enabled when Input check box is selected. Specify the input data path.
   • Output Data Path - Enabled when Output check box is selected. Specify the output data path.
   • Input Access Point - In data mapping from an application activity should have its Input Access Point set. The Default access point is displayed, by default. You can select application context from the drop-down list.

   
   Figure: Input Access Point - Application Context

   • Output Access Point - The Default option is selected by default. It also contains the option Activity Instance in case of engine context if out mapping is provided from an activity.

     
     Figure: Ouput Access Point - Engine Context

     You can select application context if the Out data mapping from an application activity is provided.

     
     Figure: Output Access Point - Application Context

   • When 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

     For more information, refer to the chapter Workflow Data Workflow Data of the Concepts handbook. Concepts Handbook in the Stardust Documentation.

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.