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

Element to Element Copy Operation with Keep Source Element Name Attribute

Element to Element Copy Operation with Keep Source Element Name Attribute

Select a FROM Type and then complete the Copy operation by making other appropriate selections. Add, edit, copy, delete, and reorganize Copy operations and scripts for the selected Assign activity.
Use
Keep Source Element Name
to replace the element at the destination with a copy of the entire element at the source, including children and attribute properties. This attribute supports XSD substitution groups and choice.
If Keep Source Element Name is disabled, then the resulting value for element-based variable in the destination (that is, the TO side) has its original namespace and local name properties.
If Keep Source Element Name is enabled, then the resulting value for the element-based variable in the destination uses the name of the element-based variable in the source (that is, the FROM side).
Given the following schema snippet:
<xsd:element name="poHeader"> <xsd:complexType> <xsd:sequence> <xsd:choice> <xsd:element name="shippingAddr" type="tns:AddressType" /> <xsd:element name="USshippingAddr" type="tns:USAddressType" /> </xsd:choice> <xsd:element name="billingAddr" type="tns:AddressType" /> </xsd:sequence> </xsd:complexType> </xsd:element>
Given the following process variable values prior to the copy operation:
poHeaderVar1
poHeaderVar2
<tns:poHeader>
<tns:poHeader>
<tns:USshippingAddr verified="true">
 
<tns:street>123 Main Street</tns:street>
 
<tns:city>SomeWhere City</tns:city>
<tns:shippingAddr pobox="true" />
<tns:country>USA</tns:country>
 
<tns:zipcode>98765</tns:zipcode>
 
</tns:USshippingAddr>
 
</tns:poHeader>
</tns:poHeader>
Given the following copy operation:
<assign> <copy keepSrcElementName="yes"> <from>$poHeaderVar1/tns:USshippingAddr</from> <to>$poHeaderVar2/tns:shippingAddr</to> </copy> </assign>
The resulting value of
poHeaderVar2
is:
<tns:poHeader> <tns:USshippingAddr verified="true"> <tns:street>123 Main Street</tns:street> <tns:city>SomeWhere City</tns:city> <tns:country>USA</tns:country> <tns:zipcode>98765</tns:zipcode> </tns:USshippingAddr> </tns:poHeader>


Updated March 30, 2020