Designing the Procedure Logic › Client Procedure Standards › Standards for Client Procedure with Flows (Links)

Standards for Client Procedure with Flows (Links)

In client procedures, event handlers are placed at the end of the action diagram but are executed independently of the main processing.

The following list shows standards for a procedure with flows to server procedures:

• View definitions:
  • Import views
  • Export views
  • Local views
• Initial processing:
  • Move import view contents to export views
  • Set initial values
  • Set a default exit state
  • Test for previously stored exit state and command to control subsequent processing
• Processing prior to any server:
  • Some application processing
  • Set and preserve values and commands for server procedures, and initializing links to servers (only one link is activated in any one execution of the procedure)
  • Move returned data to export views
  • Prepare for display of windows, dialog boxes, and fields
  • Initialize opening and closing dialog boxes
  • Set exit states
  • Exit
• Processing after server procedure “A”:
  • Test return code values for success or failure
  • Some application processing
  • Move returned data to export views
  • Prepare for display of windows, dialog boxes and fields
  • Initialize opening and closing dialog boxes
  • Set exit states
  • Exit
• Processing after server procedure “B”:
  • Test return code values for success or failure
  • Some application processing
  • Move returned data to export views
  • Prepare for display of windows, dialog boxes, and fields
  • Initialize opening and closing dialog boxes
  • Set exit states
  • Exit
• Event handlers only reached by a GUI event:
  • Respond to changes in windows, dialog boxes and fields and their selection
  • (Optionally) validate changed data
  • Prepare for display of windows, dialog boxes, and fields
  • (Optionally) Set exit states