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

Adding Variable Properties and Property Aliases

Adding Variable Properties and Property Aliases

Select properties defined in a WSDL to use in a correlation set.
Properties are useful on non-message variables as a way to isolate a process's logic from the details of a particular variable's definition. Using properties, a process can isolate its variable initialization logic in one place and then set and get properties on that variable in order to manipulate it. If the variable's definition is later changed, the rest of the process definition that manipulates that variable can remain unchanged.
A variable can have several properties, each defined as a
property alias
.
Properties
A property can be one of the following:
  • Schema type like an xsd:int or an xsd:string
  • Element
For example, a property might be a purchase order number or a customer Id. A property exists within a WSDL message transmitted during a Web service interaction or in any process variable. A single variable can contain multiple properties and a single property might exist in several variables.
Property Aliases
For each pairing of a variable and a property there exists a property alias that identifies how to extract the value of a property from the given variable, whether the variable part is a simple type, schema element, or complex type. If the part is an element or a complex type, an XPath (or other language) query is required to identify the location of the property within the element or type.
For details, see the following topics:
  • WSDL Syntax and Example for Property Names and Aliases
  • Creating a Property Definition
  • Creating a Property Alias


Updated March 30, 2020