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

Presentation Parameters

Presentation Parameters

If you query on presentation parameters, additional information is returned.
<tsst:propertyValues xmlns:tsst= "http://schemas.active-endpoints.com/b4p/wshumantask/ 2007/10/aeb4p-task-state-wsdl.xsd"> <tsst:propertyValue name="parentprocessid" type="ns:string" xmlns:ns="http://www.w3.org/2001/XMLSchema">5013 </tsst:propertyValue> </tsst:propertyValues>
If no task is deployed with the presentation parameter, an error message is returned:
<htdt:illegalArgument xmlns:htdt="http://www.example.org/WS-HT/api/xsd"> Task parameter property 'parentProcessId1' does not exist. </htdt:illegalArgument>
However, if no task with this parameter exists but it is a valid name, the returned information is empty. Here is an example of this kind of parameter:
<aetgt:getMyTasksResponse xmlns:aetgt="http://www.example.org/WS-HT/api/xsd" xmlns:htdt="http://www.example.org/WS-HT/api/xsd" xmlns:result="http://saxon.sf.net/xquery-results" xmlns:tss="http://www.activebpel.org/b4p/2007/10/wshumantask/aeb4p-task-storage.wsdl" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" >
This element lists tasks that a
parentProcessId
parameter and also returns what this value is:
<xsd:getMyTasks> <xsd:taskType>TASK</xsd:taskType> <xsd:whereClause>parentProcessId >''</xsd:whereClause> </xsd:getMyTasks>
The following table summarized what can occur when you use a presentation parameter.
Presentation Parameter
Is it Deployed
Actual Values
Query
Result
MyString
Yes
"a", "b"
<
a where clause
>
<
a parameter result
>
MyStringB
Yes
No Values
<
a where clause
>
<
a parameter result
>
MyStringC
No
Not applicable
<
a where clause
>
<
a parameter result
>


Updated March 30, 2020