[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [bpel4people] NEW ISSUE: Title: Outcome field is missing fromtask view
Hi, The outcome field came in very late and was requested by Oracle so I'd like to make the following proposal: WS-HT spec: ========== Section 6.1.1 Participant Operations: ------------------------------------- - Add the following Operation: Operation Name: getOutcome Description: Get the outcome of a task Parameters: In: task identifier, Out: string Authorization: Any Section 6.1.2 Simple Query Operations: ----------------------------------------- - In the 'Simple Task View' table, add a row Column Name: OutcomeExists Type: xsd:boolean Section 6.1.3 Advanced Query Operation: ------------------------------------------- - Add another element to the XML-schema type "tTaskQueryResultRow" <xsd:element name="outcome" type="xsd:string"/> - Modify the XML-schema file "ws-humantask-api.xsd" to include above element in complexType "tTaskQueryResultRow" - Add a row to the 'Complete Task View' table: Column Name: Outcome Type: xsd:string Constraints: - Section 6.2 XPath Extension Functions: ---------------------------------------- - Add an XPath operation: Operation Name: getOutcome Description: Returns the outcome of the task. Evaluates to an empty string in case there is no outcome specified for the task. If the task name is not present, the current task is considered. Parameters: In: task name (optional), Out: the task outcome (xsd:string) ws-humantask-api-wsdl.xsd: =================== - Add the following XML schema elements: <xsd:element name="getOutcome"> <xsd:complexType> <xsd:sequence> <xsd:element name="identifier" type="xsd:anyURI" /> </xsd:sequence> </xsd:complexType> </xsd:element> <xsd:element name="getOutcomeResponse"> <xsd:complexType> <xsd:sequence> <xsd:element name="outcome" type="xsd:string" /> </xsd:sequence> </xsd:complexType> </xsd:element> ws-humantask-api.wsdl ================ - Add the following artifacts: <wsdl:message name="getOutcome"> <wsdl:part name="getOutcome" element="htdt:getOutcome" /> </wsdl:message> <wsdl:message name="getOutcomeResponse"> <wsdl:part name="getOutcomeResponse" element="htdt:getOutcomeResponse" /> </wsdl:message> <wsdl:operation name="getOutcome"> <wsdl:input message="getOutcome"/> <wsdl:output message="getOutcomeResponse"/> <wsdl:fault name="illegalArgumentFault" message="illegalArgumentFault"/> </wsdl:operation> Best Regards, Ralf Mark Ford wrote: > TARGET: HT, Section 6.1 > > DESCRIPTION: The outcome field for a task is defined in Section 4.2 as a > query that is run against the output message in order to produce an > xs:string that represents the business result of the task. This field > doesn't appear in the task view described in Section 6.1 where an > application can get a list of tasks. It seems like a simple omission from > the list of fields that come back when requesting a listing of tasks. > > I also think it's worth considering adding a custom function to b4p to get > the outcome from a people activity but this will be opened as a separate > issue pending the outcome of this issue (no pun intended). > > PROPOSAL: > > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. You may a link to this group and all your TCs in OASIS > at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]