complexType rescheduleWorkItem

diagram |
namespace | http://api.brm.n2.tibco.com
children | workItemID itemSchedule itemBody dynamicOrgAttributes
used by |
element | rescheduleWorkItem
source | <xs:complexType name="rescheduleWorkItem"> <xs:sequence> <xs:element name="workItemID" type="ObjectID"> <xs:annotation> <xs:documentation>ID of a work item that is to be rescheduled. </xs:documentation> </xs:annotation> </xs:element> <xs:element name="itemSchedule" type="ItemSchedule" minOccurs="0"> <xs:annotation> <xs: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.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="itemBody" type="ItemBody" minOccurs="0"> <xs:annotation> <xs:documentation>Optional work item body containing data changes on a reschedule. The body is the the data as a name/value pair.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="dynamicOrgAttributes" type="orgdto:XmlDynamicIdField" minOccurs="0" maxOccurs="unbounded"> <xs:annotation> <xs: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.</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs: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 | <xs:element name="workItemID" type="ObjectID"> <xs:annotation> <xs:documentation>ID of a work item that is to be rescheduled. </xs:documentation> </xs:annotation> </xs: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 | <xs:element name="itemSchedule" type="ItemSchedule" minOccurs="0"> <xs:annotation> <xs: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.</xs:documentation> </xs:annotation> </xs: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 | <xs:element name="itemBody" type="ItemBody" minOccurs="0"> <xs:annotation> <xs:documentation>Optional work item body containing data changes on a reschedule. The body is the the data as a name/value pair.</xs:documentation> </xs:annotation> </xs: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 | <xs:element name="dynamicOrgAttributes" type="orgdto:XmlDynamicIdField" minOccurs="0" maxOccurs="unbounded"> <xs:annotation> <xs: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.</xs:documentation> </xs:annotation> </xs:element>

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