Designing the Procedure Logic › Client Procedure Structure

Client Procedure Structure

A client Procedure Action Diagram can be viewed in three parts:

• Information views—These views support all logic in the client procedure and included event handlers.
• Procedure main logic—This logic includes return status from flows to server procedures, execution first logic on flows from other procedures.
• Event handler logic—These are the handlers for each of the GUI events.

CA Gen automatically adds event handlers to the bottom of the procedure action diagram. The handlers can then be moved, but you should use a consistent approach to structure their action diagrams.

For client procedures, most logic can be placed in event handlers. Since they are focused groupings of logic, understanding a Procedure Action Diagram is simplified.

Keeping together window or dialog boxes that deal with related data minimizes the number of information views needed. This improves ease of maintenance by reducing the number of changes that have to be made to views. This approach also minimizes the number of flows, attendant view matching, and procedure logic. All of this leads to increased productivity and a reduction in the impact of change.