Chapter 5: Jobs 20964-000 Rev. C Fleet Operation Workspace Core Integration Toolkit 41 User's Manual l Queue an AMR for multiple Pickups and Dropoffs at multiple goals with a new Job Request. l Monitor existing Job Requests. l Delete existing Job Requests. The following table describes the Job Request item schema. Table 5-7. Job Request Item Schema Item Details Data Type namekey Unique identifier of a Job request entity. Optional for POST/insert/publish method. If omit- ted, the Integration Toolkit auto-generates. Required for SQL INSERT statements. String jobId JobId to assign to the job. Optional for POST/insert/publish method. defaultPriority Default priority selection.
Required for POST/insert/publish method. When set to true, this will override any priorities set in this job request. Bool goal (enumerated item) See note below The goal name for the job segment. Refer to Job Request JSON Schema below. Required for POST/insert/publish method. String priority Priority of the pickup segment. Optional for POST method. If omitted, Fleet Man- ager assigns default priority. Integer segmentType (enumerated item) See note below Must be replaced with job segment type with either "pickupGoal" or "dropoffGoal". Refer to Job Request JSON example below. Required for POST/insert/publish method. String assignedJobId JobId assigned to the job.
If JobId was not provided when the job was cre- ated, the Fleet Manager automatically creates the assignedJobId. status "Success" or failure message from the Queuing Manager. NOTE: The goal and segmentType items in every job request's details are presented in one type-value pair instead of two separate entries. If the segment type is pickup, segmentType and goal are presented as "pickupGoal":"goal name". If the segment type is dropoff, segmentType and goal are presented as "dropoffGoal":"goal name". Refer to the JSON example below for correct syntax.