2.17 Summary

New Features

• ItemPath connections now support hash-based message authentication code (HMAC) authentication. As with other connection types, you will need to provide information from the service you are connecting with ItemPath, including:
  • Request header key/value pairs (optional).
  • The access key provided by the connected service.
  • The secret key provided by the connected service.
  • The app key provided by the connected service.
• The Orders table in Explorer now includes a Priority column and filter. The dropdown filter above the table displays text equivalents for priority numbers.
• The Transaction endpoint now supports an OR operator between query parameters (e.g., ?quantity=3 OR number=5;). This expands the previous OR logic, which only operated between values (e.g., ?quantity=[or]2;3). 
• Selectable rows in tables now provide visual feedback on mouse-over. When selecting a row opens another table, the original selection remains highlighted.
• We improved the appearance and frequency of system notifications (e.g., PowerPick MSSQL connection changes).

Bug Fixes

• We fixed an issue where trailing white space in material names prevented the API from creating orders or order lines. The order and order line creation methods now trim trailing white space.
• Data Pull now accepts order lines as either a array or an object. If you provide an object containing an array, Data Pull automatically converts it to a array.
• We resolved an issue in Explorer where updating a transaction's export state would occasionally trigger a 404 error. We improved error management within the transaction update workflow.

New Features

• User emails are now case-insensitive for login and password reset (e.g., "Email@example.com" and "email@example.com" are equivalent).
• We enhanced pagination for tables in apps, logs, and workflows throughout ItemPath.
• The system now stores the status code from a Power Pick connection check in the log's description column.
• Report filters now support "exclude" as a verb option, functioning as the opposite of "includes." When providing multiple values, the filter applies "and" logic.

Bug Fixes

• We resolved an issue where password resets failed to send an email containing the reset link. A backend error prevented access to the email service key.
• The system now applies "or" logic when using "includes" with multiple values in report filters, correcting the previous unintended "and" behavior. 
• We fixed an issue that prevented "Upload Date" and "Release Date" from appearing in the transaction schema.
• We improved the transactions endpoint's filter handling, enabling it to correctly apply multiple filter sets for Data Push queries. Previously, only one filter set was applied, sometimes incorrectly.
• We corrected an issue preventing pagination filters from applying correctly to the Order Builder revisions log table.
• The system now validates reportColumnId in snapshotSchema, preventing a React app crash that occurred when the snapshot type was not "count" and no column ID was supplied.

New Features

• The status page now displays the system time and time zone.
• Manual Power Pick connection tests now generate logs.
• The Logs table for your Power Pick connection offers improved filtering, allowing you to filter to manual tests..
• API Calls table query performance has been improved.
• Added support for filtering storage rules by material and bin IDs when using the GET /storage rules endpoint.
• App names have been updated:
  • "Philips Hue" is now "Lights"
  • "CSV" and "XLSX" are now combined as "Spreadsheets"
• Variance columns in reports now use the naming convention "[Integration Name] [Column Name]" to improve clarity when working with multiple Variance integrations.
• Data Pull integrations can now run without authentication during manual runs. Enable this option in Data Pull's Other Settings.
• Data Pull's Advanced Mapping now supports mapping keys nested within objects within lists. For example, you can now map an order's advanced mapping key located within its line items. The first matching instance will be used if multiple instances of the key exist.

Deprecations

• The Custom FIelds app is deprecated in versions 2.17.0 and later and will no longer be visible in the apps folder.

Bug Fixes

• Fixed an issue where Data Push integrations might be delayed in specific configurations. Previously, only one integration would run per polling cycle if history records were found. Now, multiple integrations can run concurrently.
• Corrected an issue where ItemPath cloud instance logs incorrectly displayed "http" for events. Logs now show the correct protocol used for API calls.
• Fixed: uncaught exceptions during /run endpoint calls were logged as API Calls, preventing the creation of task status and logs.