Previous Topic: Add Logic to MAINTAIN SCORING RECORD Using Procedure SynthesisNext Topic: Add Logic to LIST SCORING RECORD Using Action Block Synthesis


Edit the Action Diagram

This image depicts the eGolf Home page

Follow these steps:

  1. In the Navigation Diagram, select the Action Diagram This image shows the action diagram icon icon from the Tool Bar to open the MAINTAIN SCORING RECORD procedure step action diagram and review the results of our Procedure Synthesis. Expand the Views. We now have the CASE OF COMMAND statement, the action block use statements, and views created to support the view requirements of the called action diagrams. There are no export views because none of the called action blocks have export views.

    Are there any changes that need to be made? Thinking back to the basic structure of a server procedure step action diagram, there were three things that were commonly done:

    1. Initializing the Exit State to a known value
    2. Moving the contents of the import views to the export views
    3. Invoking the various PADs by way of a Case of Command structure

    Thus, we need to make a few changes.

  2. At the top of the action diagram, set the exit state value to PROCESSING OK. See a prior section if you need help.
  3. Normally, we would have to move the import views to the export views. Since this particular server procedure requires no export views, this will not be necessary. However, it will be necessary to mark some of the import views as optional, since every import view is not required for every invocation of the server. For example, to delete a scoring record, only the golfer's userid and the scoring record's date and time are needed. In fact, since those three attribute views are required for all three processes, they can be left as mandatory while everything else is marked as optional. See a prior section if you need help changing the import view properties to optional.
  4. The two notes added during synthesis are not providing us with any value. Delete the two notes.
  5. Save the model.

    The completed action diagram should look like the following example. The import views have been reordered manually.

    This image depicts the statements in the action diagram