| All Verbs | /CreateUpdateTasksForWorkOrder |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| 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 .jsv suffix or ?format=jsv
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /jsv/reply/CreateUpdateTasksForWorkOrder HTTP/1.1
Host: equipstage3.e-isg.com
Content-Type: text/jsv
Content-Length: length
{
UserID: String,
WorkOrderId: String,
Uuid: String,
TaskNumber: 0,
TaskSequenceNumber: 0,
TaskDescription: String,
TaskStatus: String,
TaskLead: String,
TaskWorkGroup: String,
WorkOrderDetailID: String,
StartDate: 0001-01-01,
Name: String,
TaskType: 0,
Tags: String,
CompletionDate: 0001-01-01,
TaskTemplateID: String
}
HTTP/1.1 200 OK Content-Type: text/jsv Content-Length: length False