3.4 Summary

API

• Fixed failures on older Power Pick databases where version-specific columns are not present in transaction history, zone, location, or carrier tables.
• Fixes the Location Contents API response so quantity fields use the legacy field names expected by existing integrations.

Mappings

• Data Push, Data Pull and Variance Mapping screens now show the full source path for selected fields, such as Order / Order Name, so it is easier to tell similarly named fields apart when setting up integrations.

Reporting

• Fixed report failures when selecting or filtering order status type descriptions and other legacy type description fields.
• Prevented report row requests with oversized pagination values from reaching the database and causing SQL errors.

Explorer

• Explorer detail pages now show only configured dynamic fields in the Dynamic Fields section.

UI

• Connection and workflow forms now use clearer field prompts so users see the expected database and file-type inputs.

API

• The API now returns a clear validation error when creating or updating a material with a missing material property or material family, instead of failing with a database error.

Variance App

• Fixed an issue in the Variance report column mapping experience where clearing a selection could cause unintended behaviour.

Misc

• Removes the "Custom Columns" settings page from the UI.

API Fixes

• Updating API orders with both standard fields and dynamic fields now avoids a timeout. 
• Order responses now always include top-level zones for active orders, and ItemPath 1 compatibility responses now return zones in the legacy string-array format

Workflow and Reporting

• Workflow setup screens in the UI now use a cleaner, more consistent form layout for triggers, criteria, and actions, making workflow configuration easier to read and use across screen sizes.
• Workflow scheduling and criteria setup now behave correctly in the UI when configuring hourly triggers and report-based criteria.
• Report filters now keep the grouping value when editing and prevent negative grouping numbers from being saved.
• API and reporting now expose the History Number field for transaction history records, including support for viewing, filtering, and sorting by that value.

Explorer and App Experience

• App settings cards now match the styling used in the main Apps library so the experience is visually consistent between /apps and /settings/apps.
• ItemPath now shows a Patch Notes link next to the version number in the app footer so users can open product update information from within the application.
• Deactivated users now remain visible in the Users list, with a clear status indicator so teams can distinguish active and inactive accounts.
• Fixed a Data Push issue where filters for blank date/time values could cause integration jobs to fail instead of matching empty values.

API and Data Compatibility

• Added an optional on-premise API mode that allows authenticated API routes to run without JWTs when explicitly enabled by environment configuration.
• Added the material name back to API work order line responses so they match the legacy work order line response data more closely.
• Improved API call logging so unauthenticated probe traffic is not recorded, while authenticated user requests remain auditable, and protected the OpenAPI schema behind JWT authentication.

Improvements

• Admins can now generate a non-expiring API token for application users from the user profile screen.

Bug Fixes

• Resolves an issue in the UI where updating the Data Structure of a Data Pull integration would not work. 

Data Pull

• Fixes issue where updating a mapping would fail
• Fixes issue where the mapping key would automatically change to be lowercase

API

• Adds enum support previously existing in ItemPath 2 but missing in ItemPath 3 (e.g. Order priority, Bin type, etc...)

Files

• Fixes an issue where generate a report file for reports with the theme of Task, Log, or API Call would fail

API

• Adds connection gating when the Power Pick SQL connection is unavailable
• The GET /work_order_lines API endpoint can now properly order by locationName

UI

• Properly refreshes the list of integrations after changing the name or status of an integration
• The Displays app new integration form has been fixed

Database Management

• Move the internal ItemPath database to be managed by Docker in Linux storage in order to resolve issues surrounding Windows permissions.

Cache Storage

Modified where the cache is saved to prevent issues with Windows installations.

Apps / Navigation

- Refreshed the ItemPath app library with updated app cards, visuals, and navigation so included apps and available add-ons are easier to browse.
- Improved the app discovery experience by separating licensed apps from add-on apps in a clearer library-style layout.
- Updated app icon coverage and app presentation details to better match the current ItemPath 3 product surface.

Priority Balancing / Operations

- Added dedicated Priority Balancing settings in ItemPath 3 so teams can manage metering frequency, default queue size, max queued orders, release thresholds, and the dynamic field used for balancing.
- Improved Priority Balancing worker behaviour and status handling so balancing runs are more reliable in day-to-day warehouse use.
- Added more detailed balancing logs to help operators and support teams understand queue decisions, worker activity, and failure conditions.

Web Services / Integrations

- Improved PowerPick Web Services connection management with support for web-service user records, including password-presence tracking, active-session visibility, last-heartbeat timestamps, and remote session logout for idle sessions.
- Added optional support for unauthenticated manual integration runs when an integration explicitly enables that behaviour, making controlled external trigger scenarios easier to support.
- Continued improving integration and API compatibility for ItemPath 3, including request and response behaviour that better matches established ItemPath 2 expectations where compatibility matters.

Orders / Materials / API Compatibility

- Improved order creation compatibility by accepting `lines` as an alias for `orderLines` and validating common request issues earlier.
- Expanded ItemPath 2 style API compatibility across materials, warehouse, logistics, and related filters so existing client-side request shapes migrate more cleanly to ItemPath 3.
- Fixed material creation so the configured default material property is respected when no explicit property is provided.
- Improved material ownership handling so material create and update flows keep owner records aligned, including support for assigning or correcting a material owner through the material update path.
- Fixed material-property handling for materials created through ItemPath 3 so they align more reliably with downstream PowerPick lookups and related workflows.

Reliability / Status

- Fixed PowerPick version display on the status page so ItemPath shows the configured or auto-saved version more reliably.
- Added reliability-focused fixes across ItemPath 3 background processing and connection handling to reduce avoidable operational confusion during troubleshooting.