2.9.9 - Data Pull Upgrades

February 6, 2024

Data Pull Confirmations

  • The following mapping types can be added to customize confirmation responses:
  • A confirmation setting for determining the HTTP method has been added, either POST (default) or PATCH.
  • When an "order line" mapping is used, the value will either be a single value (if there is only one order line in the order) or an array of order lines.
  • Grouping - for creating a nested structure
  • Text - specify the key and text value
  • Message - success or reason for failure
  • Status - queued or error
  • Mapping - select a data pull mapping to get the value

Data Pull "Auto-Detect Direction Type" Setting

  • If this setting is on and no direction type is passed when creating an order, the direction type will be determined by whether or not the quantity is positive (put) or negative (pick). If a direction type is passed and the order line contains a negative quantity, the direction type must be a Pick value("pick"/"Pick"/2/"2"). Order lines cannot contain a mix of positive and negative values.
  • This postive/negative quantity logic also applies when creating order lines with the ItemPath API.

Data Pull "Advanced" Mapping

  • There is a new "Advanced" mapping for combining fields into one field.
  • Values entered within quotation marks will be passed verbatim. For example, mapping fields orderName"-"orderLineNumber could output something like Example Order-1.

Patch 2.9.9.1

New Features:

Data Pull for Materials:

  • Validation rules are checked when creating new materials.
  • A "materialFamilyId" or "materialFamily" (name) key can be passed when creating a material.
  • These Material report column types have been added to mappings: Material Property, Material Property ID, Material Codes, Material Family Id, Material Family

Patch 2.9.9.2

New Features:

  • Location details can be set at the order level when creating orders. If location details are passed in at both the order and line level, then the line location details will be used.
  • A default material property when creating new materials can be set globally in Settings.
    • Material Data Pull integrations can also override this global setting at a per-integration level.

Patch 2.9.9.3

Bugfixes:

  • A timeout has been set for Oath1 API calls. Data Pull headers are removed from logging.

Patch 2.9.9.4

New Features:

  • A Material Code can be passed when creating an order line to set the material of the line (rather than a material name or ID). This should be passed with a key of "code".
    • This Material Code functionality is also available as a mapping in Data Pull.
  • Filters can be added to a Data Pull integration, to only pull records whose keys have a certain value.

Patch 2.9.9.5

New Features:

  • For Data Pull integrations, a setting has been added for choosing the date format of incoming date data, so ItemPath can convert it to the format PowerPick expects.
  • "materialCode" can be passed instead of "code" when creating an order line.

Bugfixes:

  • A bug introduced in version 2.9.9.2 causing ItemPath to fail to start without a MSSQL connection has been fixed.

2.9.8 - Consolidate Order Lines in Data Push

January 18, 2024

A new setting has been added to Data Push integrations: Consolidate Lines. When this setting is active, Data Push transactions won't be sent until the order line is complete.

When sending data for consolidated history records, with multiple transactions having unique data for a given key, the mapped value has a different structure. That structure looks something like this:

HistoryCreationDate: {"transactionId1" : date, "transactionId2": date}

New Features:

  • When selecting the log of a consolidated Data Push task, there is a link to the order line in the Explorer.

Patch 2.9.8.1

New Features:

  • If the warehouse limit of your ItemPath license has been exceeded, you will be navigated to a page where you can update your license credentials.
  • New Data Pull mappings types allow for more custom API responses for Data Pull:
    • Orders: This key designates where the array of orders is found
    • Order Lines: This key designates where the array of order lines is found
  • To activate a Data Push integration, the connection that it is associated with must be active.

Patch 2.9.8.2

Bugfixes:

  • General Data Push bugfixes.

Patch 2.9.8.3

Bugfixes:

  • General Data Push bugfixes.

2.9.7 - Explore & Edit Transactions

January 12, 2024

Transactions are available to be viewed and edited in the Explorer! Search, filter, or sort the columns to find the transaction you're looking for, then click to display its details.

In the transaction view, the Export State type can be updated from the dropdown pictured below. This is helpful for testing or in the case of an error, since ItemPath's Data Push tool checks for Export State type "2" to find transactions that are ready to export.

Explorer transactions export state

Initial Handling Units

If you're familiar with order processing in PowerPick, you've likely heard of handling units—especially because there are two separate things in PowerPick with the same name. Long story short, it's the name or number of a transport tote/container/cart used when processing the order or batch, but it's also the name of a unit of materials (similar in some ways to a kit). Needless to say, this got a little confusing when making orders with the API, and we deprecated the parameter.

Now, we're introducing a new initialHandlingUnit parameter at the Order level that allows you to set the handling unit value—that is, a tote id or cart number—when creating an order with the ItemPath API. This sets the initial default handling unit for each order line that can be updated as needed during processing, say, if the tote gets full.

New Features:

  • The initialHandlingUnit parameter that has been added to the Create Orders endpoint is also available in Order reports.
  • The IBM DB2 connection type is now available to be used with Data Pull. (For the DB2 connection to work, the Docker file for the API and Polling containers needs to be set to Dockerfile.deb.)
  • The list of transactions in the Explorer now allows a user filter by multiple type values, e.g. Manual Pick (2) and Order Pick (4).

Bugfixes:

  • Fixed a bug where report data could show datetime values in the wrong time zone.
  • Connections will not show a status until ItemPath has finished loading, to avoid potentially misleading information.

Patch 2.9.7.1

New Features:

  • The build pipeline now also generates a new image with the name ppgsupport/api-deb, which is used for IDM DB2 connections.

Patch 2.9.7.2

New Features:

  • The Status page now shows a list of connection names and the status of each one. If a connection is clicked, the user will be navigated to the connection tab in the Settings page.

Bugfixes:

  • Fixed a bug with the ItemPath API's logic where material names containing round or square brackets were not being found.
  • There is no longer a 500 error when logging in with an invalid username or email. We've modified the error message to notify users that their username and email are case-sensitive.
  • When the Web Services connection was not successful, the connection history chart on the Status page was hidden, replaced by an error icon. Now, the bar chart remains visible and a smalled "Disconnected" error icon is displayed above the chart.

Patch 2.9.7.3

New Features:

  • You can now click on the ID of a transaction in a Data Push integration (in the Logs and Failed Attempts tabs) to see the details of that specific transaction in the Explorer.
  • If a user does not add a default port to the Web Services URL/IP, the default port of 1353 will be added.
  • When a user navigates to the password reset page, the "Forgot your password?" link has been replaced with a link that navigates back to the login page.

Patch 2.9.7.4

New Features:

  • The Apps list now displays a list of additional apps that are not licensed but are available to purchase.
  • Data Pull has a new setting to choose the "Request" type to either "POST" or "GET" API calls.
  • The Confirmation field for Data Pull integrations now has you choose the connection as the base URL and then enter the path, mirroring how setting up Data Pull and Data Push connections are set up.
  • When selecting columns to add to a Report, the options are now sorted with columns related the report theme first, followed by other categories in alphabetical order.

Bugfixes:

  • When resetting a password with the emailed link from the "Forgot Password" page, the new password wasn't saving properly. This has been fixed!

2.9.6 - New Dashboard Charts, API Additions

October 24, 2023

Dashboard widgets got an overhaul! Not only is performance improved with faster live refresh rates, but there are also new chart types available. Plus, clearer help messages help you easily see what needs fixing in your widget settings. Give it a try!

  • Line charts are now available for all data, not just historical data.
Line Chart
  • New chart type: Calendar! Requires a snapshot "grouped by" a date column.
Calendar Chart
  • New chart type: Stacked Bar chart!
Stacked Bar Chart

New Features

  • There are 25 new report columns that are text descriptions of various "types" found in Power Pick models. These make report and snapshot data much easier to understand.
  • An endpoint for updating an untouched Order Line has been added. See it in the API reference to see what fields can be updated.
  • The timeout limit setting in a Data Push integration now has a maximum value of 90 seconds. Performance has been improved to reduce delay when waiting for API responses from external API connections.
  • The following fields are now included in the response from the GET /materials, PUT /material/id, and POST /material endpoints: currentQuantity, currentValue, expectedQuantity, netQuantity, pickQuantity, and putQuantity.
  • Passing invalid filter values in API calls no longer causes an error but instead ignores the filter. (E.g. passing "quantity"=sdfsdf or "materialId"=1 will be ignored.)

Bugfixes

  • Through a loophole when creating users with the API, it was possible to make a user without a role, which would cause permissions issues. Now roles are always required.
  • Updating a material's material property with an API call now works successfully.
  • We fixed a crash in PowerPick connection tests if there was no connection found.
  • When saving a new Data Push mapping, the submit button will now reset instead of continuing to appear loading.
  • A crash when adding mappings to grouping mappings in Data Push has been fixed.

Patch 2.9.6.1

New Features

  • Adds new MSSQL connection type. In this connection, a new Database field is shown. This is the name of the MSSQL database.
  • Data Pull SQL Integrations now have the SQL query auto-generated using the Data Pull mappings.

Bugfixes

  • New widgets weren't initially appearing when added to a Dashboard view until the view was refreshed. This has been fixed.
  • A few report column types were throwing errors, including material-base Dynamic Fields, but they have been adjusted.
  • Reports with lots of columns were having column positioning/ordering issues, which have been fixed.

Patch 2.9.6.2

Bugfixes

  • Checks for PowerPick version 4.17+ for Access Point history information.

Patch 2.9.6.3

New Features

  • "Netsuite" has been added to the types of connections that can be set up in Connection settings.
  • Enabled type-to-search in fields like report theme and materials in the Order Builder app.
  • Status page shows info about the length of time the connection status charts show. Also, a message shows if a user's time zone has not been set.
  • We modified the "Status" column in the user panel to display "Active", "Pending", and "Application" and added a new column to show the "Type" of user.

Bugfixes

  • The Light/Philips Hue connection form now allows new app credentials to be entered and saved successfully.
  • Some improvements were made to the UI of the Epicor app.
  • The setting in General Settings to set the URL path for links to ItemPath (for password reset links and such) went missing in a recent version, so we put it back.

Patch 2.9.6.4

New Features

  • Orders from a NetSuite restlet can now be pulled in and transformed into an order to be created through web services.
  • Data Push and Data Pull integration lists now show a Status column indicating if the integrations are set to "Active" or not.

Bugfixes

  • Data Push transactions would be slow to send if their was an unexpected issue downstream. Not only have we improved the way Data Push queries transactactions and queues them up to export, we've also added a process that checks for transactions that may be stuck "in progress".
  • The list of Failed Attempts in Data Push integrations is displaying properly again.
  • The Order Builder app is no longer incorrectly determining the Web Services session as "not alive" when it is.
  • Logs lists are showing the correct number of results, rather than always 100 items.
  • Cycle Counts logs are now selectable and sorted properly by date.

Patch 2.9.6.5

New Features

  • A new "Transactions" tab has been added to the Explorer, so you can search for and select individual transactions from the history table. From this interface, you can update the export state of transactions, used especially for testing Data Push.
  • When a software upgrade is applied to ItemPath, logged-in users will see a notification that a new version has been detected and they should refresh ItemPath to see the changes.
  • You may have seen that if the connection to the ItemPath API is lost, a red banner appearssaying "Connection with ItemPath API Failed. Trying to Reconnect..." Now, if the connection is still disabled after 30 seconds, it will redirect to a page indicating next steps.
  • We've made improvements to our search bars throughout ItemPath.
  • When creating transaction records on slower systems, PowerPick can take some time to calculate the Total Quantity value (the total quantity of the material in all locations after the transaction is completed). We've added a check in Data Push to make sure the value is not null before exporting the transaction.

2.9.5

August 2, 2023

A shift in how we handle Web Services connections will eliminate potential errors caused by multiple services running (causing PowerPick license limit errors) and session issues. Instead of closing Web Services' sessions, ItemPath logs out, making it possible to reuse the session ID which is cached for 2 minutes.

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.

Patch 2.9.5.6

Bugfixes

  • We've been working on our user permissions and fixed some errors caused by the order of the API calls we use to check permissions.
  • The "Edit" permissions have been fixed so users without them can't delete reports or report filters.
  • Adjust the label for the report filter value of "Empty/None/Null" to "No Value" to distinguish from results containing the word/string "None".
  • Changing the sort of the report data table no longer causes a crash.


Patch 2.9.5.7

New Features

  • The new Status page now features connection status chart! The top charts show PowerPick connections' status over the past 24 hours, and the bottom chart shows API calls over the last 30 days, sorted by HTTP code series (e.g. 400 and 500 errors).
  • Log reports now have Connection Name, Status, and Type columns available to be added.

Bugfixes

  • Fixed a bug with our new snapshot caching where the duration was getting set to 24 hours. The default refresh time is now 30 minutes, or less if data is grouped by hour (5 minutes) or by minute (1 minute).


Patch 2.9.5.8

Bugfixes

  • The "No Value" filter for reports wasn't playing nicely when combined with other selections, but this is fixed.
  • The URL Path setting in Data Push integrations was looking for a full URL. Now it just expects the path.


Patch 2.9.5.9

New Features

  • A new PowerPick Time Zone setting on the Settings page enables proper conversion to the local time in the UI, when the machine running PowerPick is not using UTC.

Bugfixes

  • Viewing Dashboard views on mobile or other screen sizes was causing layouts to save new positions, which has been fixed.
  • Updates to user permissions fixes the order of some permissions checks, which previously could limit the number of viewable reports.
  • The footer was not showing on the login page in recent versions, but this has been restored so the "Forgot Password" link is accessible.
  • "Put" history records were incorrectly returning the Location name rather than the Storage Unit name. This is fixed for Data Push mappings.
  • Using the "orderBy" filter for GET calls to the /api/storage_rules endpoint now works.

2.9.4 - Better API Logs and a New "Images" Endpoint

July 19, 2023

Checking Logs is Easier than Ever

If you've had to check your API logs, you might have had some trouble finding the right error codes you're looking for, or filtering by the right time frame. Or, you may have wished you could save your search settings. We've made some big improvements to the API logs to make it easier to find what you're looking for.

We've added more information to the logs, including the duration of the request and a more readable response. You can now filter your logs by multiple HTTP status codes, so you can see different kinds of errors at once. (This matches what's in the Data Push logs.)

API Logs

Plus, you can save time by using the same search settings again and again, using an API Calls report. For example, you could filter by 400- or 500-series HTTP codes within the last week, and save that report. Then, you could export the report automatically with a Workflow, so you never miss an error message.

API Call Report

Check out everything we've added and improved since 2.9.3.3. We'll keep adding to this list online as we release more patches.

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.

2.9.3

May 18, 2023

New Features

  • Updating ItemPath license will refuse an invalid license
  • Report rows generate faster
  • Logs, tasks, and workflow histories are saved for 100 days instead of 30

Bugfixes

  • Added "type" field to SHOW /order-lines API call
  • Fixed Excel files erroring because of a time zone issue
  • Added Access Points to History and Max Drive Speed to Material Property conditionally based on PowerPick version
  • Fixed an error caused by NaN values in reports, now replaced by null values


Patch 2.9.3.1

Bugfixes

  • Added "taskNumber" field to SHOW /order-lines API call


Patch 2.9.3.2

New Features

  • Improved the performance of saving generated data for snapshots with a subgroup

Bugfixes

  • Made behind-the-scenes improvements to debugging snapshots and workflows
  • Fixed timezone comparison for workflows' "last triggered" times

Patch 2.9.3.3

New Features

  • Started adding permissions and access restrictions for Reports. Based on the permissions enabled for each role, users can be restricted from viewing, creating, editing, and deleting reports. Permissions can be enabled per report. More to come!

Bugfixes

  • Fixed a conditional statement that could cause a bug with report column types with a baseTable as well as dynamic columns
  • Included in a significant amount of code cleanup in this patch in an improvement to our "Test Connection" functions

2.9.2 - Pushing Big Data with the ItemPath API

March 24, 2023

Having a Motive: Data Push Retries & Filters

Users of the Data Push app can now see more details about transactions that had an export error. When resending these from the Failed Attempts tab of an integration, the status will update as the transaction is re-exported. Refreshing will remove successful transactions from the list.

Data push failed attempts

In the settings of each Data Push integration, users can also filter transactions by Motive Type. This can be used to exclude transactions that are not relevant to the integration, such as deletions or cancellations.

Data push settings filters

As with the History Type filter, you can select multiple values from the dropdown for the motives you wish to include. Leaving the selection blank will include all transactions. (To view a list of all Motive Types in the API reference, click here.)

Data push motive filters 2

Exploring PowerPick Parameters

The Explorer view now includes a "Parameter Value" tab, which shows valies obtained from PowerPick settings. This is useful for seeing what ItemPath reads from PowerPick, for checking PowerPick rules, and for troubleshooting.

Explorer parameter values

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

2.9.1 - Visualizing Targets, New Favourites, and Subgroups

February 16, 2023

Targets Acquired

You can now create multiple "trend lines" on widgets that use bar charts, giving them a name and amount so you can see if you're hitting your goals! In this example, you can compare your daily order processing rate to your target rate at a glance, using colour coded lines to see if you're on track. Check out the documentation here to set it up on your dashboard.

Target line 5

Your Personal Favourites

You can now toggle a report as a favourite, which will add it to a list of your favourite reports. This is a great way to keep track of the reports you use most often. You can also add a report to your favourites from the report's settings.

Report favourites

Snapshot Subgrouping

We've improved a feature of snapshots that allows you to group data by a field, and then further group that data by another field. This is useful for widgets that can show data grouped by date field plus a secondary field. For example, here you can see how many orders were processed per hour, and then see how what types of orders those were.

Subgrouped snapshot

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.

2.9.0 - Quicker Snapshots & Dynamic Fields Support

January 9, 2023

Improved Performance for Snapshots

Some of our users have experienced delays when loading snapshots data in reports or dashboards. We've made some changes to improve performance, so loading is quick and responsive. We've also added some checks to help users identify what kinds of snapshots might slow things down, and how to adjust them to prevent this.

For example, a snapshot that updates every minute, counting thousands of rows, takes some time. Often a user will set this frequency to get a quick update, but it can slow down the entire application. Now, you have the option to disable a snapshot that isn't in use. Also, snapshots that group data by a date field (e.g. pick transactions grouped per hour) show a warning that they might also slow down the application.

Snapshot grouping warning

Extensive Testing

We've introduced a new automated testing framework that checks for stability, changes, and data integrity. That means putting out releases with confidence that you're getting a stable product.

Dynamic Fields

For users with the Database Configurator module enabled in PowerPick, we've added the use of Dynamic Fields to the API and the Data Push app.* The names of these custom fields are set in PowerPick. They're available in Orders, Order Lines, and Transactions endpoints, which means they can be mapped in Data Push integrations. Dynamic fields can also be added to reports.

*This does require the Custom Fields app in ItemPath.

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.
1 2 ... 7

Subscribe to Software Release Notes