New Features

• Improvements have been made to increase Web Services performance.
• A new Status page allows a manual restart of ItemPath and gives an overview of its performance. More status features to come here!
• All forms in ItemPath's UI now have validation checks, which helps avoid issues if required data is missed or the wrong kind of data is entered.
• Variables in our docker-compose.yml file have been updated for compatibility.
• Deactivated workflows may be manually tested.

Bugfixes

• We're in a time loop! After creating an order with Web Services, the order is not always immediately available in the PPG database. ItemPath now attempts to query the order up to 5 times, with a 1 second delay between the queries. If the order is still not found, then a 500 is returned—rather than on the first try.
• A Data Push bug has been fixed, where a temporary session created in PowerPick was not closing its connection to the MSSQL database because the session's engine was not being disposed.
• API access and refresh tokens could be viewed by logged-in users in ItemPath's logs in 2.9.4.0, but are now encrypted.
• The orderBy function has been added to Bins, Kits, Material Properties, and Stations so they can be sorted properly in Reports and the Explorer.
• An occasional bug when updating Data Push mappings has been fixed.

Patch 2.9.5.1

New Features

• Our new status page now includes info about the number of PowerPick warehouses in use, compared to how many are licensed in ItemPath. Also on the status page: PowerPick and ItemPath version numbers and performance statistics like API calls, running features, and files generated. Plus, there's a handy button to restart ItemPath when needed.
• When renaming a material via an PUT /api/materials/[id], we now check and update any order lines that have this material to also have the new material name. This mimics PowerPick's material renaming utility within material update API requests.
  
• For those using custom Report columns, the UI in the settings has been tidied up.

Bugfixes

• When ItemPath runs on a Windows device, it creates a lock file directory to prevent multiple instances of a cleanup process from running at the same time.
• An issue with the "Blank" template option when setting up a new Dashboard view has been fixed.
• We fixed pagination for several API endpoints when using "limit" and "offset" arguments.

Patch 2.9.5.2

New Features

• The set global time zone and user's time zone show on the status page.
• When upgrading from versions without permissions, Administrator roles are granted full permissions by default.
• Reports that do not use PowerPick data are accessible even when PowerPick a connection isn't present.
  
• A tooltip has been added to the API Logs page to help users easily identify what time zone the dates are being displayed in.
• Five new Report Column Types are now available for ItemPath Task reports: Workflow History ID, Snapshot ID, User ID, Workflow ID, and Integration ID.
• A user with no report permission and no report access will have an empty table of reports.
  
• If a user does not set a custom timezone, the global time zone is used by default.
• When adding or updating a report filter, the placeholder for 'none' is now 'Empty/None/Null'. This eliminates the issue of wanting to filter out a null value and a 'None' error message.
  
• The PowerPick Web Services connection requires a PowerPick database connection. Both the API and UI now return an error if trying to test the Web Services connection when there is no active MSSQL connection.
  
• Detailed logging has been added in a new tab in Connection for testing API connections
• Two new comparators can be used with query parameters, which can be used to hide API calls (e.g. refresh calls):
  • [like] - checks for the existence of substring
  • [notlike] - checks for values where the substring is not in the string
• The "Logs" page now has a switch that toggles a character limit to the body, error, and response column to a character limit of 100.
  

Bugfixes

• When resetting a user's password with a reset link, the new password was saving but not showing a confirmation message, which has been fixed.
• Date range search on API Logs page now converts to the set time zone instead of the one used locally.
  
• Some MSAL Single Sign-On bugs have been fixed.
  
• The ability to deactivate users was failing but has been restored.
• Adding filters to reports was showing a "required" message if the value was not manually selected, but now the field validates as values are typed.
• A bug preventing saving workflows that trigger at a minutely, hourly, or daily frequencies has been squashed.
• An issue where PowerPick connections could show as valid, even if no successful connection was being made, has been fixed.
• Missing "sorting" toggles for Explorer columns have been added.
• Passing the query parameter "search" now works with the following routes: "GET /batches", "GET /integrations", and "GET /order_lines".
  
• Some missing filters for /api/location_contents have been added, including "id", "warehouseId", "currentQuantity", "quantityExpected", "quantityPermitted", "shelfId", "carrierId", "creationDate", "countDate".
  
  

Patch 2.9.5.3

Bugfixes

• Testing successful PowerPick Web Services connections was showing a success in the UI but showing a returned an error code in the logs. This has been resolved so the logs show the true response code.
• The /api/location_contents endpoint now uses the "orderBy" function properly.
• For ERP connections, when getting headers for an API request, the content-type is only set to application/json if the user hasn't specified a content type.
• When a user tries to access just the "/api" endpoint (for testing or otherwise), they will be redirected to "/api/status" instead.

Patch 2.9.5.4

Bugfix

• Connection settings (used for connecting to an ERP endpoint for Data Push) have been updated with content headers for compatibility with Oracle.

Patch 2.9.5.5

New Features

• If the PowerPick database is disconnected, an indicator will show on the new status page where the PowerPick version and number of warehouses are displayed.

Bugfixes

• "warehouseName" now works as a filter in API "GET" calls
• Updating Cycle Count integrations was causing 404 errors because of a mishandling of the integration ID, which has been fixed.
  
• The ability to restart ItemPath with an authenticated API call has been restricted.

New Features

• A "Supplements" (also "Images") endpoint has been added to the ItemPath API. These are for adding supplemental images of your materials. Take a look at the endpoint details in the API reference here.
• In the back-end, we've been implementing a data validation tool called useQuery to clean up our code. You might not notice the difference, aside from getting better help messages if you've entered invalid data somewhere.
• We're slowly rolling out some permissions for our UI, but it isn't all ready yet. We'll let you know when we've fully launched user permissions!
• An overhaul to our API logging means there's a lot more information in the logs, including duration and easier-to-read responses. You can also filter by multiple HTTP status codes (e.g. all errors). We also added a friendly warning if you're about to clear your logs.
• There's a new Report type for "API Calls" reports. This lets you save your search settings and export error messages in files—rather than grabbing them from the API logs—plus use them with Workflows.

Bug Fixes

• Sped up how long it takes for snapshot data to generate.
• Caught a few bug reports that were slipping through the cracks of our internal reporting system.
• Increased running performance by adding more "workers" in the background.
• Improved handling of updates to PowerPick MSSQL credentials.
• Adjusting the date range on the API logs wasn't always updating, but we fixed that in our overhaul.
• In workflow triggers, monthly triggers now accept numbers of the month. Also, brand new triggers show the correct "Next Trigger" time.
• Added zoneId and isMarkedFull to the API endpoint for locations, which fixes a bug in the Locations section of the Explorer.
• For users with the PDF export option, we fixed a bug where the PDF wouldn't export properly if the filename was too long.
• Searching reports when not on the first page now works properly.
• Added better support for customers using Dynamic Fields.
• Fixed a few columns in Reports and the Explorer that were missing sorting logic.

New Features

• A pie chart Dashboard widget with one snapshot using the "group" feature will show different colors for each group/slice of the pie.
• Reports can now have filters that use the "equals" operator with "None" to filter out null values. Using "None" twice will filter out both null and empty string values.
• Data Push's performance has been improved by using multiple threads to push data in bulk. Data Push's logging has also been improved by combining the logs into one file and using a backup log file.
• The "Test" button in Data Push is disabled if there are no history records to push.
• For Data Push connections test (usually to a /ping endpoint), the self-signed SSL certificate check is overridden. This test also has better error messages.

Bugfixes

• Some users were having errors with Microsoft OS compatibility with ODBC 18 because of a TLS mismatch, so we've downgraded to ODBC 17 for now.
• Some Data Push transactions were getting stuck at Export State Type 3 because of an error, which has been resolved.
• Fixed a bug when resetting a password using the password reset link.
• "Station" was missing from the history table in Data Push but has been added.
• Fixed a crash caused by a missing port in a PowerPick connection and fixed the SWL port check.
• Fixed occasional errors when deleting dashboard views and reports.
• Because there can be multiple stations with Web Services either enabled or disabled, the "Test" button in the Web Services connection settings now checks if any station's Web Services parameter is set to "true".

Patch 2.9.2.1

New Features

• Added Motive Type filter to Data Push integration filters
• Increased performance of Data Push by using multiple threads
  
• Combined Data Push logs into one log (instead of two, for sent and response)
• Added backup file for Data Push logging
• Reworked Data Push failed attempts page
• Added Parameter Values to the Explorer
• Overriding self-signed check for Web Services connection test only
  

Bugfixes

• Added Station column type with History baseTable and added Station Name to parameter values
  
• Fixed Dashboard view deletion error
• Fixed error on password reset
• Web Services connection checks all station parameters to see if any are installed
• Fixed limit for GET queries that were using "pageSize" instead of "limit"
• Limited unnecessary re-rending of proxy setting every time a connection is tested

Patch 2.9.2.2

New Features

• Added HTTP status code to Data Push logs

Bugfixes

• Set exportStateType to 4 if HTTP status code is any success code in the 200-series, not only 200

Patch 2.9.2.3

New Features

• Added check for valid URL when testing a connection
  
• Added configurable settings to Data Push integrations for timeout, max retries, SSL-verification, max records
  
• Data Push records can be retested in bulk by entering multiple IDs separated by commas
• Data Push logs are now filterable
• Workflow action can retry Data Pushes using a History report

Bugfixes

• Fixed workflow deletion failing
• Fixed pickZone and putZone relationships

Patch 2.9.2.4

New Features

• Add Access Points to API, Reports, and Data Push

Patch 2.9.2.5

New Features

• Added "warehouseName" to Location Content API calls

Bugfixes

• Fixed failed redirect to login page on first user creation
• Fixed some Data Push bugs, including an error with the Refresh button in the Failed Attempts page
• Improved some connection settings storage and deletion

Patch 2.9.2.6

New Features

• Added defaults and placeholders to Data Push settings UI
  

Bugfixes

• Re-added orderName to GET /order_lines API call, in the order line's transactions
  
• Ensuring http:// exists at start of connection string when testing and generating connection string

Patch 2.9.2.7

New Features

• Fixed error with workflow & snapshot run times by comparing the trigger time with current UTC time

Bugfixes

• Fixed error with workflow & snapshot run times by comparing the trigger time with current UTC time
• Fixed List /order_lines API call failing if "status" parameter wasn't passed

Patch 2.9.2.8

New Features

• Added Permissions View for User Groups

Bugfixes

• Fixed snapshot subgrouping errors
• Fixed errors when changing user details
• Fixed custom DateTime field so format is ISO 8601

Patch 2.9.2.9

Bugfixes

• Fix groupby datetime snapshots
  

Patch 2.9.2.10

New Features

• Added getCount to all services

Bugfixes

• Passing a storageUnit now works when creating an Order Line with the API, as well as Order

Updated May 9, 2023

New Features

• We've shifted the way to add filters to reports. Rather than separating multiple values by commas (which is still supported), values can be entered individually and checked or unchecked from a dropdown. Additionally, we now support filtering by "null" in reports.
• You can set a default warehouse in the settings page, which will be used if no warehouse is specified during order creation.
• Querying parameters in API calls is now case insensitive, which is especially helpful for Info fields, which previously had to be capitalized.
• Dashboard widgets will show an error message if the snapshot data fails to load.
• If a snapshot is set to inactive, it won't show an an option to be added to a widget.
• We added a verification check to TLS certificates.

Bugfixes

• We made some fixes to our usage of PowerPick's new "Count Empty Permanent Locations" feature. This includes an issue that could happen when allocating a count order with this feature enabled.
• As part of the fix for the above, we also improved our PowerPick version-checking method.
• A bug that was preventing the new Export State Type of some Data Push transactions from being committed has been fixed.
• Snapshot date groupings will always show in chronological order.
• It was possible to add an email attachment to a workflow without entering the rest of the required fields. This has been updated so all fields are required.
• We fixed some issues with checking ports for PowerPick connections. Testing connections is also faster.
• Exporting some report files wasn't resolving, so we've improved the way we handle this.
• Pagination in reports was sometimes not working correctly. This has been fixed.
• An error caused by missing report types has been fixed.
• We're continuing to make improvements to snapshot data generation.

New Features

• For compatibility with PowerPick 4.20, the "countEmptyLocations" field is now available in the API for creating count orders. Setting this value to "true" will include empty locations in the count. (By default, the value is "false".) An error will be returned if used with an older version of PowerPick.
• Users can log in to ItemPath using either their email address or their username.
• Password reset emails have a different message if no URL path has been set in ItemPath's general settings.
• The POST /api/orders endpoint accepts many more location attributes, including "locations", "storageUnits", "zones", "areas", "carriers", and "shelves".
• "directionType" is not a required field when creating a new order. PowerPick will automatically set empty directionType fields to 2 ("Pick").
• Filtering orders by priority, status and direction type accepts number or text description.
• Object IDs can be passed in PUT calls. ItemPath will ignore the value to prevent an error.
• Data Push testing is disabled if there are no history records found.
• API calls to create orders will now check that PowerPick Web Services is installed.
• Web Services settings have a checkbox to allow or disable a proxy SSL connection.
• License status warnings include the license expiry date.
• Variance reports now can optionally ignore capitalization when comparing materials.

Bugfixes

• Cleanup of old snapshot data is now broken down into smaller, more frequent cleanup jobs to prevent database locking.
  
• Some data was missing in the Explorer. This has been added in, as well as search functionality for the data.
• When first creating a snapshot, the time selector was not always showing. This would prevent the snapshot from being created but has now been resolved.
• Snapshots for material reports weren't able to group by location count, but this is now fixed.
• An error causing importing report templates to fail has been fixed.
• Filtering between two dates in the API logs now works correctly.
• A successful connection test will update the status of the connection.
• An occasional error when setting a connection test endpoint is fixed.
• New user forms would sometimes hang if no license was entered, but this is fixed so licenses aren't required at this stage.

New Features

• When creating Order Lines in the API, either a material ID or a material name can be used. There are also better checks for unique order line numbers and unique serial numbers.
• When creating Orders in the API and setting the directionType or priority, either integers or strings can be used. Those values are listed here.
• Material reports and API calls now include a Location Count (locationCount) value, which calculates the number of locations (bins) the material is found in. This can be helpful for making free space.
• Reports show their creation date, which is helpful for sorting.
• On-premise SQL server connections can now use more versions of TLS/SSL certificates.
• Testing Web Services connections generates logs, which available on the logs page and in reports. There are also better log error messages when failing to connect.
• Data Push testing shows clearer error messages, such as if the history ID is invalid.
• New API endpoints for handling units have been added to the ItemPath Postman collection.

Bugfixes

• Several report columns weren't sorting because of missing tables. This fix also fixes "orderBy" queries that weren't working in the API. Also, some report columns weren't deleting properly, but that's also resolved.
• Resolved a potential issue where snapshots failed to run because of other snapshots running for too long.
• Reports with Allocated Quantity values can use those values with report filters.
• The time to load the /api/reports GET call is reduced to about 5% of what it previously was.
• There are better checks in place for snapshot triggers, making sure the update frequencies are valid to avoid errors.
• Stacking bar charts in the dashboard can always set unique colours for each snapshot, so you can clearly see each one in the stacks.
• In odd cases in dashboard widgets where a snapshot's data is a null or erroring value, a "-" will show to indicate this. Before, this might have caused the dashboard to crash.

New Features

• In the ItemPath API, when creating or updating an order, the priority can be set either using an integer (1-4) or a text value ("low", "medium", "high", "hot"). Note: This is also true for setting order direction types (e.g. 2 or "pick").
• Another improvement to API error messages is a message returned if the body of the request contains escaped characters.
• When searching for a report column to add to a report filter or snapshot grouping, you can type to search for the column.
• For users of the Epicor app, if importing orders from a CSV files, ItemPath checks that no orders get imported twice to avoid errors.
• In Material reports, there's a new LocationCount column that we've created to check on number of locations a material is stored.
• In LocationContentBreakdown reports, there's a new Pick Quantity and Put Quantity columns for serial/lot numbers.
• TLS certificates are enabled for the Web Services connection in ItemPath.

Bugfixes

• Searching reports and workflows would sometimes not return the right results. Now you can easily filter these lists again.
• Updating a report filter saves correctly instead of returning an empty value.
• Snapshots calculating a sum of column values can now be shown properly in dashboard widgets.
• A rare case of snapshot data getting stale and not updating has been fixed. Snapshot data storage is now smarter about its self-cleaning.
• Some compatibilities with PPG 5 have been fixed, including some database columns being renamed (for example CountEmptyLocations).

New Features

• Material codes (a material's alternate lookup codes) can now be updated using the /materials API endpoint. Updating a material's codes deletes previous codes and replaces them. Click here to see how in the API reference.
• Snapshots now have a setting to generate data at a specific time of day and day of week/month, depending on the frequency.
• Snapshot caches reset when snapshot settings are updated, so the new settings are applied immediately instead of waiting for the next scheduled trigger.
• Loading animations have been added in several places throughout ItemPath's interface to indicate that data is being retrieved.
• An indicator across ItemPath's header indicates whether it is a production or development environment.

Bugfixes

• The API call to create a new material was requiring the "isBlocked" field. This field is now optional, because PowerPick will set this to "false" by default if nothing is specified. Also, errors around setting the "materialProperty" field have been fixed.
• Dashboard widgets can no longer reposition themselves when loaded in a different size of window.
• New user groups weren't saving properly due to a missing field.
• An error occurring sometimes when updating user passwords has been fixed.

New Features

• The dashboard has some improvements to make it more responsive. You can expect faster load times and clearer help text.
• Data Push integrations show transactions that failed to send and allow you to retry them.
• Widgets in the dashboard now display a message if an invalid chart type is chosen.
• Snapshots can now be generated at a specific set time (every day/week/month/year).

Bugfixes

• Settings to connect the Lights (Philips Hue) app have been updated.
• Exported files now convert the date to the user's time zone, or the global time zone if no time zone is set.
• Fixed errors in pie and number charts.