Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 10 Palette Reference : Throw

Throw
Activity
The Throw activity throws the specified fault and control is passed to any error-handling routine defined to handle the error. If no error-handling routine is defined in the orchestration process, the error is propagated to the calling environment (for example, the client or service that sent the request). See Chapter 6, Exception Handling for more information about error handling.
Configuration
The Configuration tab has the following fields.
Name of the fault. You can define any fault to throw. The schema of the fault is defined on the Fault Data tab.
Fault Data
The Fault Data tab defines the schema for the fault you wish to throw. If you choose to throw a pre-defined fault message for one of the incoming messages in the process, you should select the correct fault message from the WSDL resource. You can also choose to throw a new fault and define your own fault schema.
See TIBCO ActiveMatrix BusinessWorks Process Design Guide for more information about defining schemas.
Join Condition
The Join Condition tab allows you to define an expression based on the values of the incoming transitions to the activity. If the expression evaluates to true, the activity is executed, if the expression evaluates to false, either the activity is bypassed or a fault is thrown. See Transitions and Join Conditions for more information about join conditions.
The Join Condition tab has the following fields.
Specifies what action to perform if the join expression evaluates to false. The following options are available:
Inherit setting — use the default action specified within the current scope. The current scope is either the current group containing the activity or the orchestration process if the activity is not within a group.
Bypass activity if false — skip the processing of the activity, set the outgoing transition conditions to false without evaluating them, and resume processing.
Throw fault if false — throw a joinFailure fault and switch control to an error-handling routine configured to catch all unhandled exceptions. If the exception is not caught, the fault is propagated to the calling environment.
The expression to evaluate to determine if the activity should be executed. The only data available to this expression is the value of any transitions into the activity. You can use the XPath Formula Builder to create the join expression.
Input Variable
The Input Variable tab allows you to specify whether you will use the contents of a process variable as input to this activity or you will use the Input tab to specific input bindings as XPath expressions. If you choose to use a process variable, the schema of the variable must match the input schema of the activity exactly.
Use Input Variable — specifies that you will select an input variable to use as input for the activity. The schema of the variable must match the input schema of the activity or an error is thrown when this activity is executed.
Use Input Binding Tab — specifies that you will use the Input tab to create mappings and XPath expressions to provide input for this activity.
When Use Input Variable is selected in the Input Style field, this field allows you to select from a list of process variables to use as the input for the activity.
Input
The Input tab is only enabled if Use Input Binding Tab is selected in the Input Style field on the Input Variable tab. See TIBCO ActiveMatrix BusinessWorks Process Design Guide for more information about mapping and transforming input data.
The input for the activity is the following.
The schema for the fault message to throw. The schema depends upon the fault message.
 

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved