Job Order Import — Custom Service Creation
A custom service is not necessary for Job Order Import but could be created if automating imports from an external system. If using a custom service, the service will call a ThingWorx Applications service and parse the response to determine success. Below is a description of the input required for the ThingWorx Applications service as well as the expected result from the service.
Entity—PTC.FSU.CORE.JobOrder.EndPoint_TG
Service Name—ImportJobOrder_END
Input
The ImportJobOrder_END service requires a STRING input that can be parsed into JSON.
• JobOrderList (STRING)—This input must match the structure of the example exactly or the import will fail. See the
example JSON for the structure and explanation of fields. Multiple job orders can be imported at one time but will be validated and transacted separately. This means that one object within the input can fail validation while the other objects will not be affected.
Output
The ImportJobOrder_END service will return the results of the input validation as a JSON object.
• Result (JSON)—The validation can return three types of results and can return multiple results per object within the input. The three types of results are
Success,
Warning and
Failure. See
Troubleshooting for details regarding these results and see
JSON Structure for the structure of the JSON object.