Route Export — Custom Service Creation
A custom service is not necessary for Route Export 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.ProductionPath.EndPoint_TG
Service Name: ExportRoutes_END
Input
ExportRoutes_END requires a string input that can be parsed into JSON.
• RouteNames (STRING)—This input must match the structure of the example exactly, or the export will fail. See the example JSON in
ExportRoutes_END JSON Structure for the structure and explanation of fields.
Output
ExportRoutes_END will return the results as a JSON object.
• Result (JSON)—Contains values for
ErrorCode,
ErrorMessage, and
Timestamp. See the example JSON in
ExportRoutes_END JSON Structure for an explanation of the fields.