eQuipAPI

<back to all web services

CreateUpdateTasksForWorkOrder

The following routes are available for this service:
All Verbs/CreateUpdateTasksForWorkOrder
CreateUpdateTasksForWorkOrder Parameters:
NameParameterData TypeRequiredDescription
UserIDquerystringNo
WorkOrderIdquerystringNo
UuidquerystringNo
TaskNumberqueryintNo
TaskSequenceNumberqueryintNo
TaskDescriptionquerystringNo
TaskStatusquerystringNo
TaskLeadquerystringNo
TaskWorkGroupquerystringNo
WorkOrderDetailIDquerystringNo
StartDatequeryDateTime?No
NamequerystringNo
TaskTypequeryintNo
TagsquerystringNo
CompletionDatequeryDateTime?No
TaskTemplateIDquerystringNo

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: equipstage2.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>