In many cases, the only processing associated with a value of Command is the setting of Exit State to a particular value.
For example, consider the example in Example From MENU Procedure. The MENU procedure does nothing but inspect the incoming command and set an exit state value based on its value in anticipation of flowing to a different procedure step.
In cases like this, it is possible to associate a particular value of Command with a particular value of Exit State. A command associated with an exit state value for a procedure step is called an “autoflow” because you can use it to cause a dialog flow to take place without any action diagram logic to support it.
At execution time, autoflows are processed as follows:
In the menu example (see Example From MENU Procedure), it would have been possible to simplify the construction of the Procedure Action Diagram shown in the illustration Procedure Action Diagram for MENU Procedure even further by specifying the autoflows in the following table.
Autoflow Command |
Exit State Value |
1 |
TAKE ORDER REQUESTED |
2 |
CANCEL ORDER REQUESTED |
3 |
MAINTAIN CUSTOMER REQUESTED |
Autoflows handle all valid exit states. Therefore, the Menu Procedure Action Diagram has to set only the Invalid Request condition as shown in the following illustration. If it ever executes, it means that an invalid value was placed in Command.
Revised MENU Procedure Action Diagram
Procedure Step MENU MENU EXIT STATE IS invalid_request
The combination of these autoflow definitions, the Dialog Flow Diagram shown in the illustration Annotated Dialog Flow Diagram in the Example From MENU Procedure, and the action diagram shown in the illustration Revised MENU Procedure Action Diagram give the same execution time result as the MENU Procedure example.
Copyright © 2013 CA.
All rights reserved.
|
|