An exit state is a trigger that transfers control from one Procedure Step to another. A dialog flow takes place based on the existence of one or more exit states.
Note: You can add two types of exit states with the Action Diagram in Analysis and Design: global exit states and exit states created for a specific business system.
Global exit states may be defined prior to the existence of a business system and thus are not associated with a business system. They accommodate the concept of common action blocks. Because a common action block may be USEd in multiple business systems within the same model, the exit states referenced and set within that action block must be available to all those business systems.
Both types of exit states can be used by any Action Diagram or action block within the same model, regardless of business system.
Note: For more information about managing exit states and their messages, see the Design Guide.
Exit states are set within procedures based on the following:
You can modify an exit state in the Action Diagram with the EXIT STATE IS action. This action sets the value of the special attribute, exit state. In the EXIT STATE IS statement, you can compare the exit state to possible exit state values. Since there is only one occurrence of the exit state special attribute, the execution of an EXIT STATE IS action destroys its previous contents.
The format of the EXIT STATE IS action statement is:
EXIT STATE IS exit-state-value
The following statement sets the exit state value to order_cancelled:
EXIT STATE IS order_cancelled
The following statement uses the EXIT STATE IS statement in an IF statement to set screen attributes:
IF EXIT STATE IS EQUAL TO customer_not_found MAKE ERROR
|
Copyright © 2014 CA.
All rights reserved.
|
|