Informatica ActiveVOS
- Informatica ActiveVOS 9.2.4.6
- All Products
Required Properties
| Optional Properties
|
---|---|
Copy
optional attributes:
Keep Source Element Name. See
Validating Variables
Ignore Missing From Data. See Copy Operation with Ignore Missing From Data Attribute.
| Name. See
Selecting Activity Labels
|
Join Condition. See
Creating a Join Condition for an Incoming Link
| |
Suppress Join Failure. See
Process Properties
| |
Comment. See
Adding Comments to a Process
| |
Documentation. See
Adding Documentation to a Process
| |
Setting Visual Properties and Using Your Own Library of Images
| |
Execution State. See
Viewing the Execution State of an Activity or Link
| |
Validate. See
Validating Variables
| |
Extension Attributes and Extension Elements. See
Declaring Extension Elements and Attributes .
|
From Type
| Description
| Upon Selection of this Type...
|
---|---|---|
Expression
| An XPath (or other language) expression to perform computations on variables and properties. Must return a string, number or Boolean.
| You can create the expression with an Expression Builder. For more information, see
Using the Expression Builder
|
Literal
| A constant that conforms to an XML schema definition. The type can be indicated inline using
xsi:type
| Do one of the following:
Type in literal value (for example, 100)
Select the Literal Contents
Dialog (...) Button to open a larger editing area
Generate literal contents for a complex variable, described in
Using the XML Data Wizard and
Copy Operation Literal Contents Examples .
Assign a dynamic endpoint reference. See Copy Operation Dynamic Endpoint Reference Example.
|
Opaque
| Name representing private application data. Use this option only for an abstract process. For more information, see
Creating an Executable vs. an Abstract Process .
| No other choices are allowed
|
Partner
| This selection generates a list of partner links and roles
| Select a partner link and role defining an endpoint reference
|
Variable
| A WSDL message variable and optional part name
A WSDL message property
XML schema simple type or element
| Select a variable name, and optionally, a part name and query. For more information, see
Using the Query Builder . Queries are allowed only in executable processes.
|
Variable Property
| A WSDL message property
| Select a variable name and property
|
This From type
| Must match this To type
|
---|---|
Message-type variable
| Message-type variable with matching type
|
XML schema type variable
| A variable containing a schema type
|
XML element type variable
| A variable containing the same element
|
Literal
| Must have a matching XML schema type
|
Expression
| Expression or Variable
|
Partnerlink
| partner role
|
<assign validate="yes|no"? standard-attributes> standard-elements (<copy keepSrcElementName="yes|no"? ignoreMissingFromData="yes|no"?> from-spec (see below) to-spec (see below) </copy> | <extensionAssignOperation> ...assign-element-of-other-namespace... </extensionAssignOperation>) + </assign>
<from variable="BPELVariableName" part="NCName"? <query queryLanguage="anyURI"?>? queryContent </query> /from> <from partnerLink="NCName" endpointReference="myRole|partnerRole"/> <from variable="BPELVariableName" property="QName"/> <from expressionLanguage="anyURI"?>expression</from> <from><literal>literal value</literal></from>
<from opaque="yes">
<to variable="BPELVariableName" part="NCName"? <query queryLanguage="anyURI"?>? queryContent </query> /to> <to partnerLink="NCName"/> <to variable="BPELVariableName" property="QName"/> <to expressionLanguage="anyURI"?>expression</to>
<assign> <copy> <from>'yes'</from> <to part="accept" variable="approval"/> </copy> </assign> <assign> <copy> <from>$po.lineItem[@prodCode=$myProd]/amt * $exchangeRate </from> <to>$convertedPO.lineItem[@prodCode=$myProd]/amt</to> </copy> </assign>
<bpel:assign> <bpel:extensionAssignOperation> <bpel:documentation>new script operation </bpel:documentation> <ext3:script>abx:createAttachment('request', 'text/plain', abx:base64Encode("Test attachment") )</ext3:script> </bpel:extensionAssignOperation> </bpel:assign>