complexType rescheduleWorkItem

diagram
namespace	http://api.brm.n2.tibco.com
children	workItemID itemSchedule itemBody dynamicOrgAttributes
source	<xsd:complexType name="rescheduleWorkItem">   <xsd:sequence>     <xsd:element name="workItemID" type="ObjectID">       <xsd:annotation>         <xsd:documentation>ID of a work item that is to be rescheduled. </xsd:documentation>       </xsd:annotation>     </xsd:element>     <xsd:element name="itemSchedule" type="ItemSchedule" minOccurs="0">       <xsd:annotation>         <xsd:documentation>Optional item schedule period to be associated with the work item.   If no object is passed then the item schedule period will not be changed.</xsd:documentation>       </xsd:annotation>     </xsd:element>     <xsd:element name="itemBody" type="ItemBody" minOccurs="0">       <xsd:annotation>         <xsd:documentation>Optional work item body containing data changes on a  reschedule. The body is the the data as a name/value pair.</xsd:documentation>       </xsd:annotation>     </xsd:element>     <xsd:element name="dynamicOrgAttributes" type="orgdto:XmlDynamicIdField" minOccurs="0" maxOccurs="unbounded">       <xsd:annotation>         <xsd:documentation>If specified the work item will be "re-offered" to the dynamic instance of the org model pointed to by the array of name / value pairs.  If the work item is opened / allocated to a resource and the resource still has visiblity of the work item in the new entities then it will remain allocated to them.   Otherwise it will be re-offered.</xsd:documentation>       </xsd:annotation>     </xsd:element>   </xsd:sequence> </xsd:complexType>

element rescheduleWorkItem/workItemID

diagram
type	ObjectID
properties	content  complex
attributes	Name   Type   Use   Default   Fixed   Annotation id   xs:long   required         documentation Unique ID of the work item.
annotation	documentation ID of a work item that is to be rescheduled.
source	<xsd:element name="workItemID" type="ObjectID">   <xsd:annotation>     <xsd:documentation>ID of a work item that is to be rescheduled. </xsd:documentation>   </xsd:annotation> </xsd:element>

element rescheduleWorkItem/itemSchedule

diagram
type	ItemSchedule
properties	minOcc  0 maxOcc  1 content  complex
children	startDate maxDuration targetDate
annotation	documentation Optional item schedule period to be associated with the work item.   If no object is passed then the item schedule period will not be changed.
source	<xsd:element name="itemSchedule" type="ItemSchedule" minOccurs="0">   <xsd:annotation>     <xsd:documentation>Optional item schedule period to be associated with the work item.   If no object is passed then the item schedule period will not be changed.</xsd:documentation>   </xsd:annotation> </xsd:element>

element rescheduleWorkItem/itemBody

diagram
type	ItemBody
properties	minOcc  0 maxOcc  1 content  complex
children	parameter
annotation	documentation Optional work item body containing data changes on a  reschedule. The body is the the data as a name/value pair.
source	<xsd:element name="itemBody" type="ItemBody" minOccurs="0">   <xsd:annotation>     <xsd:documentation>Optional work item body containing data changes on a  reschedule. The body is the the data as a name/value pair.</xsd:documentation>   </xsd:annotation> </xsd:element>

element rescheduleWorkItem/dynamicOrgAttributes

diagram
type	XmlDynamicIdField
properties	minOcc  0 maxOcc  unbounded content  complex
attributes	Name   Type   Use   Default   Fixed   Annotation name   xs:token   required         value   xs:string   optional
annotation	documentation If specified the work item will be "re-offered" to the dynamic instance of the org model pointed to by the array of name / value pairs.  If the work item is opened / allocated to a resource and the resource still has visiblity of the work item in the new entities then it will remain allocated to them.   Otherwise it will be re-offered.
source	<xsd:element name="dynamicOrgAttributes" type="orgdto:XmlDynamicIdField" minOccurs="0" maxOccurs="unbounded">   <xsd:annotation>     <xsd:documentation>If specified the work item will be "re-offered" to the dynamic instance of the org model pointed to by the array of name / value pairs.  If the work item is opened / allocated to a resource and the resource still has visiblity of the work item in the new entities then it will remain allocated to them.   Otherwise it will be re-offered.</xsd:documentation>   </xsd:annotation> </xsd:element>

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