Table of Contents

Search

  1. Preface
  2. Part 1: Using Process Developer
  3. Part 2: Creating and Modifying Processes
  4. Part 3: Functions, Events, Errors, and Correlation
  5. Part 4: Testing and Deployment
  6. Part 5: Process Central and Process Server (On-Premises)

Process Developer

Process Developer

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
>

0 COMMENTS

We’d like to hear from you!