Validating Variables
Process Developer provides several explicit ways to validate the value of variables during simulation or runtime. These are as follows:
- • Validate activity
The validate activity contains a list of process variables and validates the value of each one against its associated XML or WSDL data definition. For details, see Validate.
- • Validate attribute in an assign activity
This attribute works the same way as the validate activity. When validate is enabled in an assign activity, Process Developer validates all variables used in all of the assign's copy operations.
- • Keep Source Element Name attribute in a copy operation for validating the value of an element-based variable in the To side of a copy operation .
The Keep Source Element Name attribute works specifically on an element-to element copy operation, and is not applicable for any other type of copy operation. Process Developer validates that the root elements are valid against their XML schema or WSDL definition, without performing validation on an entire variable, since the destination element may be only one of many elements in the variable. This type of copy operation requires that the source and destination elements be part of the same schema substitution group. A substitution group allows elements to be substituted for other elements. For an example, see Copy Operation Query and Expression Examples.
- • Preference setting for validating input/output message variables
For details, see Simulation Preferences.
If a variable value is invalid, the bpel:invalidVariables fault is thrown.