apps/panel 0.86.0

English · Русский

Released on 8 October 2026. Previous release: 0.85.0.

What changed

Material consumption in the operator terminal

• With a request on WorkOrderOperation, a task of type WFMaterialConsumptionTaskInstance opens a consumption screen in the work area instead of the placeholder. For the chosen batch or the serial number you confirmed with Item, it shows each material of the specification: the consumed quantity against its norm with the unit, whether the norm applies to the batch or item or to the whole operation, and the status Collected or Collecting. The consumed material instances are listed under the material.
• While the task is in work, the operator enters a material instance number and a quantity and presses Consume. The terminal sends consume; consuming the same instance again adds to its record. The pencil corrects a record to a new total quantity, and the trash deletes it after a confirmation, which returns the stock. Quantities take a point or a comma and at most three decimals. After every action the terminal reads the task from the server again, and a refusal, such as an exceeded norm or missing stock, is shown in the server's own words.
• Complete task is available only when the server reports the norm collected for every item started in the operation, not only the chosen one. A task whose norm cannot be collected can be completed with Complete with a deviation after a confirmation.
• The terminal does not offer consumption on a serial number the operation has not started: the server would take it but would not count it for the task. A quantity operation needs materialInstanceItemIds in the request's attributeList, because that attribute is its batch.

No changes to application JSON are required. The operator's role needs the right to run the task methods, including consume, adjustConsumption and deleteConsumption; without it the server refuses the action and the screen shows its message.

Known limitations

• Complete with a deviation only confirms the completion. The server does not store a reason or a supervisor's confirmation yet, so the terminal does not record them, and the screen says so before the confirmation.
• Consumption recorded by another operator appears at the next read of the task, and the state of the tasks changes only after Refresh state: live updates cover the operation, not its tasks.

Documentation

• Material consumption task: what the screen reads and sends, how refusals, a paused task and a completion with a deviation behave.