JiwaAPI

WorkOrderInstructionPATCHRequest

The following routes are available for this service:
PATCH	/WorkOrders/{WorkOrderID}/Stages/{StageID}/Instructions/{InstructionID}	Updates an instruction for a work order stage.

**WorkOrderInstructionPATCHRequest** Parameters:
Name	Parameter	Data Type	Required
WorkOrderID	path	string	No
StageID	path	string	No
InstructionID	path	string	No

**WorkOrderInstruction** Parameters:
Name	Parameter	Data Type	Required
InstructionID	form	string	No
ItemNo	form	int?	No
InstructionText	form	string	No
CustomFieldValues	form	List<CustomFieldValue>	No

**CustomFieldValue** Parameters:
Name	Parameter	Data Type	Required
SettingID	form	string	No
SettingName	form	string	No
Contents	form	string	No
PluginID	form	string	No
PluginName	form	string	No

**WorkOrderInstruction** Parameters:
Name	Parameter	Data Type	Required
InstructionID	form	string	No
ItemNo	form	int?	No
InstructionText	form	string	No
CustomFieldValues	form	List<CustomFieldValue>	No

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

To embed the response in a jsonp callback, append ?callback=myCallback

HTTP + JSON

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

PATCH /WorkOrders/{WorkOrderID}/Stages/{StageID}/Instructions/{InstructionID} HTTP/1.1 
Host: api.jiwa.com.au 
Accept: application/json
Content-Type: application/json
Content-Length: length

{"WorkOrderID":"String","StageID":"String","InstructionID":"String","ItemNo":0,"InstructionText":"String","CustomFieldValues":[{"SettingID":"String","SettingName":"String","Contents":"String","PluginID":"String","PluginName":"String"}]}

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

{"InstructionID":"String","ItemNo":0,"InstructionText":"String","CustomFieldValues":[{"SettingID":"String","SettingName":"String","Contents":"String","PluginID":"String","PluginName":"String"}]}