Show TOC

Object documentationConnectors Locate this document in the navigation structure

 

Connectors are points in the data flow that represent connections that channel data from/to points outside the open iView.

 

You can use connectors to bring parameters in from another iView or send them at the end of the data flow to another iView, or to define the iView initialization or end value. In addition, you can use specialized connectors to augment the data flow within the iView.

Structure

The following table lists the connectors that are available when building your model.

Connectors

Connector Name

Description

Example

Start point

Defines a value used to initialize the work flow.

In an iView used to display n rows of Customers, the initialization value defined in the start point might be 10.

End point

Defines a final value at the end of the flow.

In a popup iView that returns a value to the main iView, Customer Name might be the field defined in the end point.

Navigate

(Web Dynpro runtime only)

Defines the navigation to a different iView (the “target” iView) or view in the same window.

You may have an iView in which you select the city you wish to visit. You might use a Navigate point to send a City Name to an auxiliary iView on the same page, which displays a map according to the value in the City Name field.

Signal In

For eventing, a “collection point” that receives parameters from a different iView.

In Flex-based iViews, this signal can also receive EPCM events triggered internally from nested iViews (but not popup windows). See Signal Out following.

With two iViews connected through eventing, the In signal receives the values of the fields that are output from the Out signal of the same name, in the corresponding iView.

Signal Out

For eventing, a point that sends parameters to another iView.

In Flex-based nested iViews (but not popup windows), this signal can expose an inner event at the out port of nested iView, triggering an EPCM event elsewhere in the same model.

This signal sends the fields to the In signal of the corresponding iView that receives the data of the event. For example, the Out signal may send Employee Name to the second iView, so that the In signal of the second iView sends the value to its data service, which generates the employee details.

Popup Signal

(Flash runtime only)

A point that defines the input and output ports to/from a popup iView.

In Flex-based nested iViews (but not popup windows), this signal can expose an inner event at the out port of nested iView, triggering an EPCM event elsewhere in the model.

For an iView that enables you to order train tickets, you might have an input form for selecting the trip destination, and a popup menu from a Train Departure Time field, which lets the user select the train time.

Timer

A Flash-based mechanism that counts up or down at event initiation.

A timer can be added when displaying data in a table, line by line, in conjunction with a Pause button.

User Data

An editable option that adds the personal data of the user taken from iView initialization to the list of available fields in the Computed Value dialog box (for creating formulas).

You may use the User Data module as input to an Employee GetInfo data service.

Full descriptions of the connectors and their operation are provided in the Compose Model Task Panel section of the SAP NetWeaver Visual Composer Reference Guide.