Recommendations

In addition to the requirements, certain tips can help the design of your DLG:

Generally, use as few dialog flows as possible between a client and a server. For example, add, change, and delete requests should be on one flow, not three. The client application can set the command to CURRENT on the flow to the server application. The logic in the server application tests the CASE OF COMMAND to determine which action to take. The reverse can happen on the return flow. In some situations, individual flows may be more efficient on a network because you pass only required data.
Include the word client or server (or an abbreviation for them) as part of your procedure name, perhaps as a suffix. This helps you visually identify the two types on the DLG and during packaging.