1. Activity type settings

Added a new "Activity types" page under Plant Settings for configuring how each activity type (e.g. Order, Downtime, etc.) behaves:

\ Enable or disable an activity type entirely.

\ Turn subtypes on or off for a type, and choose whether picking a subtype is required when creating an activity of that type.

\ Enable automatic numbering for a type.

\ When subtypes are enabled, manage the list of subtypes for that type: create new ones, rename them, reorder them by drag-and-drop, mark one as the default, and disable individual subtypes without deleting them.

Activity types-20260915-062630.png

Activity types 2-20260915-062639.png

2. New fine-grained permissions system

Introduced a more precise, elementary permissions model in PackOS (replacing broader group-level permissions), along with a reworked permissions management screen in Hub. As part of this, order management was split into more specific permissions, and several previously bundled admin capabilities got their own dedicated permission.

New permissions added:

\ Create orders - create new production orders (separate from managing/editing them).

\ Withdraw orders - withdraw a released or already-activated order.

\ Use data importer - upload activities or items into the plant via the data importer, using configured import templates.

\ Manage import templates - manage the templates used by the data importer.

\ Manage shared custom reports - manage custom reports shared across the whole tenant.

\ Pre-processing functions configuration - configure the pre-processing functions used in data flows.

\ Hint rules configuration - configure the hint rules shown to operators.

\ Rerun/replay line data processing - rerun or replay line data processing for past worklogs.

Because permissions are now more granular, existing roles may need to be reviewed after upgrading - a user who previously had one broad permission covering several of these actions may now need each one assigned individually.

Switching between the old and new permissions screen: On both the User and Role permissions tab in Hub, there's a button in the top corner that toggles between "Classic view" and "New experience." Both views edit the same underlying permissions - it's purely a display preference. The choice is remembered per browser (saved locally), so each admin can pick whichever layout they prefer independently.

The new permissions UI is still evolving and does not represent its final look - further design and layout changes should be expected in upcoming releases.

obraz-20260916-085716.png

3. Displaying Basic Information for Deleted SKUs

Archived information for deleted SKUs is now displayed in the Order Summary (at each stage) and in reports. Users cannot access the linked SKU details, but can still view its number and description.

image-20260910-084500.png

Ongoing order with deleted SKU

4. Improve date selectors on mobile version

Date and time pickers on the mobile app are now easier to use on smaller screens.

Better date selecors on mobile-20260915-063308.png

5. Edit Order – Improved Drag and Drop Activity Between Lines

Improved the process of moving an activity in the Timeline view from one line to another. Users can now select a new flow when the order is moved to a different line. Previously, the order remained in Draft status with no option to correct it.

After the improvement, the order:

\ is set to Draft when no flow is configured for the selected technology and SKU;

\ is set to Released when both the flow and technology are properly configured

image-20260910-123141.png

SKU Technology - Flow and line are configured

6. Validate unit code maximum length

Unit codes are now validated to prevent overly long values.

Units 8 chars-20260915-062849.png

7. Flows – Base Machine Validation

Added validation to prevent users from saving a flow without a machine configured with both Base Availability and Base Quantity.

Zrzut ekranu 2026-09-16 o 10.56.08-20260916-085614.png

8. Fix for permissions issue – editing an Activity in the Activated state

The “Inprogress order edit access” permission controls the ability to edit an Activity in the Activated state.

With this permission enabled, an activated Activity can be edited when the changeover process has already started.

image-20260911-135831.png

9. Node Ordering by Classification in ConfigHub

Improved the ability to reorder nodes within a classification, making it easier to find the appropriate problem type when adding or editing a downtime in the drawer.

image-20260909-135729.png

ConfigHub - nodes classification edit

10. Add information message for invalid flow configuration in Man-hours calculation

A clear warning message now appears when a Man-hours calculation flow is misconfigured.

obraz-20260915-070249.png

11. Order cards now show the selected production technology and flow

It's easier to see at a glance how an order will be produced.

12. Count order production from activation

Orders can now be configured so that production counts, waste, and performance figures start being measured from the moment an order is activated (including the changeover), instead of only once the order actually starts running. This is useful for lines where changeover activity should count toward the order. Currently set per production line on request - ask support if you'd like this enabled for a line.

13. Downtimes tracker better initial precision value dependent on report time scale

The downtime tracker now automatically starts with a precision level that matches the time scale of the report you're viewing.

14. Fix custom reports showing stale data when report parametrisation is enabled

Custom reports with parameters now always show up-to-date data instead of occasionally showing outdated results.

15. Fix UI problems with short performance chart

Fixed a display issue with the short performance chart in work spectrum view.

16. Fix debug value showing up on UI side for production reports

Removed a stray debug value (false) that was incorrectly appearing in the UI.

17. Order import improvements

Order import functionality was reworked for better maintainability and clarity, with no change to how imports are used.