Designing Dialogs › Procedure Definition and Dialog Design › Dialog Flows and Client/Server Applications

Dialog Flows and Client/Server Applications

In an application designed for client/server processing, the following restrictions apply:

• Client procedures must be designated as online.
• Client procedures can flow to other client procedures or to server procedures.
• Flows from client procedures to server procedures must be links. The flow must return to the client.
• The link from a client procedure to a server procedure must be set to Execute First.
• Server procedures must be designated as online with no display.
• Server procedures can be subdivided into procedure steps, but the flow from a client procedure must go to the first step of the server procedure.
• If data is sent or returned on a link, you must match information views on the links from client procedures to server procedures.
• The server procedure must set an exit state to return control to the client procedure at the end of a server procedure execution.

When data is to be sent or returned across a link, the information views on both the client and server procedures are mapped to one another by view matching.

The following illustration shows a DLG for a client/server application.

More information:

Designing Client/Server Applications