Retrieve all routing tasks

get

/productionMonitoring/clientapi/v2/routingTasks

This operation retrieves information for all routing tasks.

Request

Query Parameters
Back to Top

Response

Supported Media Types

200 Response

Successfully processed.
Body ()
Root Schema : RoutingTask_receive_list
Type: object
Show Source
Nested Schema : items
Type: array
Show Source
Nested Schema : items
Type: object
Show Source
  • attributes
    The custom attributes provided by the user as {name, type, value} tuples. Can contain any information about the raw material requirements, standard processing times,min-max requirements, capacity, expected throughput, etc.
  • The description about the routing task.
  • The unique identifier of the routing task
  • The fastest cycle time (in milliseconds) to complete this routing task for the given product under optimal circumstances.
  • machines
    The list of identifiers of machines qualified for the routing task.
  • The name of the routing task (For example: drilling, cutting etc).
  • The order number of the routing task, starting from 1.
  • The identifier of the product the routing task is related to.
Nested Schema : attributes
Type: array
The custom attributes provided by the user as {name, type, value} tuples. Can contain any information about the raw material requirements, standard processing times,min-max requirements, capacity, expected throughput, etc.
Show Source
Nested Schema : machines
Type: array
The list of identifiers of machines qualified for the routing task.
Show Source
Nested Schema : Attribute_receive
Type: object
Show Source
  • The device model URN, applicable and must be specified when attribute type is 'device', 'sensor', 'alert'.
  • The name of the attribute.
  • The type of the attribute. One of [STRING, NUMBER, BOOLEAN, DATE, BINARY, DEVICE, SENSOR, ALERT].

401 Response

Unauthorized. The request requires user authentication.

403 Response

Forbidden. The server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated.
Back to Top

Examples

curl -X GET 
   -u <username>:<password>
   -H 'Accept: application/json'
   https://iotserver/productionMonitoring/clientapi/v2/routingTasks

Example of Response Body

The following example shows the content of the response body in JSON format:


{
"count":2,
"hasMore":false,
"items":[
{
"attributes":[
{
"deviceModel":"The device model URN, applicable and must be specified when attribute type is 'device', 'sensor', 'alert'.",
"name":"The name of the attribute.",
"type":"The type of the attribute. One of [STRING, NUMBER, BOOLEAN, DATE, BINARY, DEVICE, SENSOR, ALERT]."
}
],
"description":"The description about the routing task.",
"id":"559562b05e1a-6f35",
"idealCycleTime":0.0,
"machines":[
"machines_1",
"machines_2",
"machines_3"
],
"name":"The name of the routing task (For example: drilling, cutting etc).",
"orderNumber":12345,
"product":"The identifier of the product the routing task is related to."
},
{
"attributes":[
{
"deviceModel":"The device model URN, applicable and must be specified when attribute type is 'device', 'sensor', 'alert'.",
"name":"The name of the attribute.",
"type":"The type of the attribute. One of [STRING, NUMBER, BOOLEAN, DATE, BINARY, DEVICE, SENSOR, ALERT]."
}
],
"description":"The description about the routing task.",
"id":"15e4110c75ed-2a4f",
"idealCycleTime":0.0,
"machines":[
"machines_1",
"machines_2",
"machines_3"
],
"name":"The name of the routing task (For example: drilling, cutting etc).",
"orderNumber":12345,
"product":"The identifier of the product the routing task is related to."
}
],
"limit":10,
"links":[
{
"href":"https://iotserver/productionMonitoring/clientapi/version/resource/path",
"rel":"self"
},
{
"href":"https://iotserver/productionMonitoring/clientapi/version/resource/path",
"rel":"canonical"
}
],
"offset":0
}



Complete cURL Example

The following example shows a complete cURL command that you can use to perform the described operation:

curl -X GET 
   -u <username>:<password>
   -H 'Accept: application/json'
   https://iotserver/productionMonitoring/clientapi/v2/routingTasks



Note that in the request, https://iotserver will be replaced by the name and port of your assigned IoT Cloud Service instance. The format of the Cloud Service instance is https://myinstance-myidentitydomain.iot.us.oraclecloud.com and the default port is 443.
Back to Top