Adding conditions dependent on attribute values consists of building a CASE OF and subordinate CASE action statements.
The CASE action statement appears in the following format:
CASE OF expression _1 CASE constant_1 action_statement_list_1 [CASE constant_2 action_statement_list_2]... [OTHERWISE action_statement_list_3]...
The CASE OF conditional action specifies actions that depend on the value of a specific attribute. All actions depend on the same attribute and are mutually exclusive.
To add conditions dependent on attribute values, begin by specifying the attribute whose value determines the action. Specify each CASE attribute value as shown in the following example:
CASE OF competitive vendor company_rating CASE "BEST" CASE "GOOD" OTHERWISE
Then, specify the action for each possible value of that attribute, as shown in the following example:
CASE OF competitive vendor company_rating CASE "BEST" MOVE competitive vendor TO preferred vendor CASE "GOOD" MOVE competitive vendor TO ok vendor OTHERWISE
Finally, specify what happens when the attribute value is equal to none of the above using OTHERWISE. This is shown in the following example:
CASE OF competitive vendor company_rating CASE "BEST" MOVE competitive vendor TO preferred vendor CASE "GOOD" MOVE competitive vendor TO ok vendor OTHERWISE MOVE competitive vendor TO export vendor
When you implement a process in the Dialog Flow Diagram, CA Gen automatically creates a Procedure Action Diagram containing a CASE statement. When you specify commands during process-to-procedure implementation, the CASE statement includes a USE action for each command selected. This is shown in the following example:
CASE OF COMMAND CASE modify USE modify_purchase_order CASE log USE enter_purchase_order CASE cancel USE cancel_purchase_order OTHERWISE
Note: For more information about the CASE command, see the Design Guide.
|
Copyright © 2014 CA.
All rights reserved.
|
|