Table of Contents

Search

  1. Preface
  2. Welcome to Informatica Process Developer
  3. Using Guide Developer for the First Time
  4. Getting Started with Informatica Process Developer
  5. About Interfaces Service References and Local WSDL
  6. Planning Your BPEL Process
  7. Participants
  8. Implementing a BPMN Task or Event in BPEL
  9. Implementing a BPMN Gateway or Control Flow
  10. Using Variables
  11. Attachments
  12. Using Links
  13. Data Manipulation
  14. Compensation
  15. Correlation
  16. What is Correlation
  17. What is a Correlation Set
  18. Creating Message Properties and Property Aliases
  19. Adding a Correlation Set
  20. Deleting a Correlation Set
  21. Adding Correlations to an Activity
  22. Rules for Declaring and Using Correlation Sets
  23. Correlation Sets and Engine-Managed Correlation
  24. Event Handling
  25. Fault Handling
  26. Simulating and Debugging
  27. Deploying Your Processes
  28. BPEL Unit Testing
  29. Creating POJO and XQuery Custom Functions
  30. Custom Service Interactions
  31. Process Exception Management
  32. Creating Reports for Process Server and Central
  33. Business Event Processing
  34. Process Central Forms and Configuration
  35. Building a Process with a System Service
  36. Human Tasks
  37. BPEL Faults and Reports

2. Designer

2. Designer

Validating Variables

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.


Updated March 30, 2020