5.2 Job Creation 5.2 34 Fleet Operation Workspace Core Integration Toolkit 20964-000 Rev. C User's Manual ate and Track a Job This can be accomplished by generating a unique namekey and supplying it in the job cre- ation step as the JobId. This namekey can then be used to obtain information about the job as the Fleet Manager processes it (refer to Monitoring of Jobs on page 44 for more information). Alternatively, a system could create a job without a JobId and then query the job creation method with the Fleet Manager to obtain the assignedJobId which can then be used to track the job. b Creation Information is provided below for the various job creation methods.
eating Pickup Jobs This section provides details for generating new Pickup jobs or deleting existing Pickup jobs. It also describes how to monitor existing Pickup jobs. These functions can be used to manage Pickup jobs for the AMR fleet. The following table describes the Pickup item schema. Table 5-1. Pickup Item Schema Item Details Data Type namekey Unique identifier of a Pickup job entity. Optional for POST/insert/publish method. If omit- ted, the Integration Toolkit auto-generates. String jobId JobId to assign to the job. Optional for POST/insert/publish method. goal Name of the pickup goal. Required with POST/insert/publish method. priority Priority of the pickup segment.
Optional for POST/insert/publish method. If omit- ted, Fleet Manager assigns default priority. Integer assignedJobId JobId assigned to the job. If JobId was not provided when the job was cre- ated, the Fleet Manager automatically creates the assignedJobId. String status "Success" or failure message from the Queuing Manager. kup Job Using REST Use the following REST calls to generate and delete existing Pickup jobs. These calls can also be used to get information for Pickup jobs queued to the Integration Toolkit.