eQuipAPI

CreateUpdateTasksForWorkOrder

The following routes are available for this service:
All Verbs	/CreateUpdateTasksForWorkOrder

**CreateUpdateTasksForWorkOrder** Parameters:
Name	Parameter	Data Type	Required
UserID	query	string	No
WorkOrderId	query	string	No
Uuid	query	string	No
TaskNumber	query	int	No
TaskSequenceNumber	query	int	No
TaskDescription	query	string	No
TaskStatus	query	string	No
TaskLead	query	string	No
TaskWorkGroup	query	string	No
WorkOrderDetailID	query	string	No
StartDate	query	DateTime?	No
Name	query	string	No
TaskType	query	int	No
Tags	query	string	No
CompletionDate	query	DateTime?	No
TaskTemplateID	query	string	No

To override the Content-type in your clients, use the HTTP Accept Header, append the .xml suffix or ?format=xml

HTTP + XML

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

POST /xml/reply/CreateUpdateTasksForWorkOrder HTTP/1.1 
Host: equipstage3.e-isg.com 
Content-Type: application/xml
Content-Length: length

<CreateUpdateTasksForWorkOrder xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/eQuipModel">
  <CompletionDate>0001-01-01T00:00:00</CompletionDate>
  <Name>String</Name>
  <StartDate>0001-01-01T00:00:00</StartDate>
  <Tags>String</Tags>
  <TaskDescription>String</TaskDescription>
  <TaskLead>String</TaskLead>
  <TaskNumber>0</TaskNumber>
  <TaskSequenceNumber>0</TaskSequenceNumber>
  <TaskStatus>String</TaskStatus>
  <TaskTemplateID>String</TaskTemplateID>
  <TaskType>0</TaskType>
  <TaskWorkGroup>String</TaskWorkGroup>
  <UserID>String</UserID>
  <Uuid>String</Uuid>
  <WorkOrderDetailID>String</WorkOrderDetailID>
  <WorkOrderId>String</WorkOrderId>
</CreateUpdateTasksForWorkOrder>

HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length

<boolean xmlns="http://schemas.microsoft.com/2003/10/Serialization/">false</boolean>