Designing the Procedure Interaction › Passing Data

Passing Data

When data needs to be passed from one procedure to another, it is done using view matching for both flows and remote uses.

The navigation diagram in the following illustration represents a slightly more complex example.

The illustration provides an example of data passing for both a flow and a remote use would be if the user is on the customer list and decides to update information about a customer.

The illustration shows a navigation diagram collection of an airline reservation system:

• The user selects a customer.
• That customer identifier is view matched along the flow from the customer list client to the customer detail client.
• It is view matched along the remote use from the customer detail client to the customer server.
• The customer server reads all of the data that can be updated for the customer and returns that data to the customer detail client. The data is returned via a view match on the remote use.

Data can pass over both flows and Procedure Step USE to its destination. Any data in the source procedure's export data view can be passed to the destination procedure's import data view, as long as the views are compatible.

Link flows can also return data from the destination of the link to its source. Any data in the destination procedure's export data view can be passed to the source procedure's import data view, as long as the views are compatible. Remember that during a return from a link, the source procedure's import view is populated from the export view of its previous execution. However, any data returned from the destination to the source procedure overlays the corresponding elements of that procedure's import view.

More information:

Designing the Procedure Logic