@orion-front/docs

Appearance

apps/panel 0.83.0 ​

English · Русский

Released on 28 September 2026. Previous release: 0.82.4.

What changed ​

The changes below apply to an operator terminal whose panel.request is a standard request. The local demonstration works as before.

Operation list ​

  • The search, the Future and Completed toggles and By date / By priority sorting now work with a standard panel.request. They were disabled for that source before. A search finds operations by order, equipment or item number: workOrder, selectedWorkUnit.itemId and materialInstanceItemIds.
  • The terminal opens with completed operations hidden and sorted by planned start, as the demonstration does. Configured findAttributes stay in force; configured sortParams now order only the operations that the selected sort leaves equal.
  • After a failed list read, the terminal hides the previous cards until a read succeeds, so the list no longer shows operations that may not match the displayed search, toggles or page.

Opened operation ​

With a request on WorkOrderOperation:

  • The opened operation shows its tasks, work instruction and documents from the API. Tasks follow the workflow graph from Start to Finish. Choosing the work instruction task shows its text. The document area downloads each file of the operation and shows it in the viewer.
  • The terminal adds the quantities, status and timer fields to the read of the selected operation itself, without changes to attributeList. The default footer shows the plan, queue, in-work and other quantities and the status from the API; a custom footer shows them where its fields use them, and a value the API does not return shows —.
  • The terminal labels the states inScheduling, inDevelopment, inReview, obsolete, Released, disabled and enabled. For example, an operation of an order that is still being scheduled shows Scheduling (В планировании) instead of inScheduling, and its tasks show In development (Разработка) instead of inDevelopment.
  • The footer timer shows the remaining time of the operation from the API. In work, it counts down every second from the stateEnteredAt and remainingDuration values that the API returns; in another status, it shows the API remainder as it is. Overdue time is red. While remainingDuration is empty, the timer shows —.
  • The footer shows the operator's profession and personnel number from the API: the personnel number of the signed-in user's Persona and its profession as code and level, for example 16015/6. Before, these rows showed — with a real API. An operator with several professions sees the first one; the value is underlined with dots, and a tap, a click or the Tab key opens a tooltip with the others. If these details cannot be read, both rows say Read error, and Refresh reads them again.
  • With live updates enabled for the deployment (NUXT_PUBLIC_REALTIME_HUB_URL), the opened operation follows the server: after a SignalR notice about it, for example a start or pause on another terminal, the terminal reads the operation again and shows the new status, quantities and remaining time without Refresh state.
  • The notice at the top of the terminal now names only what is still not connected: workflow commands.

Known limitations ​

  • Start, Pause, Good and task completion stay disabled for a real source.
  • My operations is still unavailable.
  • A list read fails with an error if one of its conditions names an attribute that the configured metaTypeName lacks: the default read uses state.systemName and plannedStartTime, a search adds the three search attributes, and sorting by priority adds priority.
  • The timer never turns yellow for an API operation: the API gives no planned total for the 90% threshold.
  • Live updates cover the opened operation only: its task states and the list cards change after Refresh state or reopening.
  • The workflow graph does not order the tasks of one parallel step; they keep the order of the API response.
  • Only the work instruction task shows content; other tasks show their name and state.
  • Choosing a serial item is not connected for this source: Item stays disabled, and the header shows all item numbers of the operation.

Updated documentation ​

  • The operation source section lists the conditions that the search, toggles and sorting add to the request, the reads an opened operation makes, and how their failures are shown.