element scheduleWorkItem

diagram |
namespace | http://api.brm.n2.tibco.com
properties |
content | complex
children | item itemSchedule itemContext itemBody dynamicOrgAttributes
annotation |
documentation
Request element for scheduleWorkItem operation.
source | <xs:element name="scheduleWorkItem"> <xs:annotation> <xs:documentation>Request element for scheduleWorkItem operation.</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="item" type="Item"> <xs:annotation> <xs:documentation>Basic, participant and work type information about the work item</xs:documentation> </xs:annotation> </xs:element> <xs:element name="itemSchedule" type="ItemSchedule" minOccurs="0"> <xs:annotation> <xs:documentation>The schedule period to be associated with the work item. If no object is passed then the item with have no schedule and cannot be worked on. If an empty object is passed BRM will default this to immediately available with no target date.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="itemContext" type="ItemContext"> <xs:annotation> <xs:documentation>The work item's context, as supplied by the application that scheduled the work item.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="itemBody" type="ItemBody"> <xs:annotation> <xs:documentation>The work item body, containing each data field (as a name/value pair) required by the data model in the work item's work type. </xs:documentation> </xs:annotation> </xs:element> <xs:element name="dynamicOrgAttributes" type="orgdto:XmlDynamicIdField" minOccurs="0" maxOccurs="unbounded"> <xs:annotation> <xs:documentation>If specified, this will specifiy the array of name / value pairs of attributes that DE will use to identify the correct dynamic instance for any template org model entity.</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType> </xs:element>

WSDL documentation generated by XMLSpy WSDL Editor http://www.altova.com/xmlspy