Robot Tasks

A robot task describes proposed work under a stock request and organization. Inventory Clerk records the device reference, requested time and units, with a controller event reference when supplied through the agreed connection. These details give Inventory Supervisor a concrete task to inspect before authorizing its next state.

The task moves from Draft to Submitted, then receives an Approved or Rejected decision. Only an Approved task can move to Completed through the guarded action. The person deciding a submitted task must be different from the person who created it. Every accepted step raises the revision so later actions can check the version they are using.

• Task preparation. Link the work to the correct stock request and organization. Check the intended device and requested units before submitting the current revision for review.
• Independent decision. Inventory Supervisor examines the submitted task and approves or rejects it. The review action refuses a decision by the creator and refuses stale revisions.
• Completion context. Inventory Clerk completes eligible Approved work through the task action. Preserve the controller event reference when available and examine stock-movement evidence separately for the quantity effect.

Agree how device references map to equipment in the customer’s controller environment. Configure that connection separately, including who supplies an event reference and how the team inspects it. A recognizable device label should not lead the clerk to infer that a command has been dispatched or a physical move has finished.

Define the evidence the supervisor uses when deciding on requested work. Check the parent request’s authorized quantity and the intended location context during the rehearsal. Decide who reviews when the usual supervisor created the task. Keep the independent decision requirement intact rather than having the creator use another screen to approve their own work.

Prepare a robot task for a tote associated with an approved storage request. Inventory Clerk records the intended device and units, submits the Draft task and hands the current revision to Inventory Supervisor. A different person reviews it, then the clerk completes the approved version using the agreed operating evidence.

Repeat with the creator attempting approval and with a stale revision after another accepted transition. Both attempts must be refused. Try completing a Submitted or Rejected task and confirm that it cannot skip approval. Finally, inspect the posted movement for the parent request. A Completed robot task should not hide a quantity mismatch in the stock records.

• Robot Review Queue — Submitted tasks with device, quantity and revision context for independent review.
• Robot Task Board — Open task states and their parent requests for the next handoff.
• Open Stock Requests — The authorized stock-work context behind the task.

Use robot task review and completion, then stock execution and verification to check the quantity effect.