Design › Designing Client Procedures › Lesson Activity › eGolfer Home › Complete the Flows

Complete the Flows

Now that we have our views defined in the eGolfer home page, we can complete the flow from the eGolf Services home page to the eGolfer home page.

If you recall, after successfully registering or logging in to the system, the golfer should be sent to their home page. We already set the triggering mechanism. Within the eGolf Services procedure step action diagram logic we set an exit state to xfr to egolfer home. Flows from one client procedure to another are triggered when there is a flow defined between the two procedure steps, and the source procedure step completes execution with the exit state value set to the defined flows on exit state. Within the flow, we can also pass data and commands. Data is matched from the export view of the source procedure to the import view of the destination procedure.

There are two types of flows: Links and Transfers. For client/server-type applications, including Web applications, we usually use Links. That said, for this particular application, we are going to use two Transfer flows.

Links are essentially two-way flows. In addition to flows on exit state value, you also define a Returns on Exit state value. It is the destination procedure's responsibility to set the Returns On exit state value. You can also return data from the destination procedure step's export views back to the source procedure steps import views, along with a command.

One other property of a flow is the action you want to take when you get to the procedure you are flowing to or from. For a link, there are two actions to define: The action you want to take at the top procedure step when you get there, and the action you want to take back at the from procedure step when you return.

The choice of action to take includes Display First or Execute First.

• Display First—No logic is executed at the destination procedure step. The screen or window associated with the destination procedure step is displayed, along with any data passed to it.
• Execute First—Execute the logic in the destination procedures step's action diagram. After executing the logic, it can display the screen or window associated with it, or it can flow somewhere else, depending on the logic.

For Windows and Web applications, we usually use Display First actions. Any logic we want executed prior to the window actually appearing is usually placed in an open event for the destination procedure.