2.16 Summary

Bug Fix

• Some Workflows created in versions later than 2.15.0.0 would fail to trigger due to an unnecessary filter. The filter was removed and a "NO TRIGGER" message was added to logging to identify similar errors in the future.

2.16.5.1

Bug Fix

• When using Order Builder with cases where orders would contain large numbers of order lines (more than 125), orders with an initial status of "Ready to be Sent to Power Pick" would be sent before all order lines had been generated. We have introduced improved logging for the order creation process, adjusted the order creation logic, and adjusted the loading indicator to prevent unnecessary re-renders. ItemPath will now wait for all order lines to be created before sending orders to Power Pick.

New Features

• When setting an order to “allocated” through the API, the logic in our API will now accept the values: "true", "yes", and "1". Previously, it only accepted boolean values, true or false.

Bug Fixes

• A conflict between ItemPath version  2.16.3 and Power Pick versions preceding 4.17.0 resulted in an error when using the Storage Rules endpoint, as the alwaysUsenewLocations column was added to Power Pick 4.17.0 and following.  A conditional check was added to verify the version of Power Pick before including the alwaysUseNewLocation column.
• Passing location data at the order level would not set order line location data if there was no order line location data 
  (prior to the attempt to set the location data). We added new functions to better handle empty order line location data, populating it with order location data when necessary.

2.16.4.1

Bug Fixes

• The Work Order Line model was updated to resolve an issue that prevented access to the Location table.

2.16.4.2

Bug Fixes

• Added a default timeout of 10ms to connections using cookie based authentication. 

2.16.4.3

Bug Fixes

• When creating batches, the order of operations would occasionally result in the batch ID being cleared from the data before it would be returned. Improving the order of operations now ensures that IDs will be returned.

New Features

• Advanced Mappings in Data Pull are no longer displayed as a drop-down menu.
• Consolidated order logs in Data Push now link to the order in the Explorer.
• When consolidating lines or orders in Data Push, the History ID mapping is now returned as a list instead of an object.
• The Consolidate Orders checkbox in Data Push is now a drop-down menu under filters that lets you select from the following options:
  • Disabled: Orders will not be consolidated; each transaction will prompt Data Push to send data to your system (one confirmation per transaction).
  • Consolidate Lines: Data sent to your endpoint will be consolidated per order line (potentially multiple lines per order).
  • Consolidate Orders: Data sent to your endpoint will be consolidated per order (one confirmation per order).

Bug Fixes

• In Data Push, the comparison operator "Not Like" returned unexpected results in some cases. This was resolved by adjusting the logic.
   

New Features

• The REST API Connection options now support cookie-based authentication. This method uses HTTP cookies to store a session identifier, which the server uses to authenticate subsequent requests. To configure cookie-based authentication, you need to provide the following:
  • Login URI: The endpoint used to initiate the authentication process.
  • Authentication location: How the service expects credentials (headers, body, or query parameters).
  • Credential keys: The names of the parameters used for the username and password.
  • Cookie keys: The names of the cookies used for authentication, including the session cookie.
  • Session duration: The lifetime of the session token, including the duration and unit of time.
     

Patch 2.16.2.1

Bug Fixes

• Log calls that exceeded the character limit would result in the application crashing. We refactored the code for truncating values greater than 100 characters in length, which will now render the first 100 characters followed by "...".
• Due to the logic used by Data Pull, it was unable to find order line data residing in lower levels of a nested data structure. Updating the mapping logic within Data Pull corrected this issue, allowing Data Pull to correctly identify and extract order line data regardless of its nesting level.

2.16.0

New Features

• Various enhancements were made to the Dockerfile to improve security, update libraries, and enhance the organization and clarity of the file.
• Added support to handle multiple location types when mapping location data in Order Builder.
• Added support for multiple time formats for dynamic order names in Order Builder.
• Quantity is no longer automatically populated as a mapping for Count order integrations in Order Builder, since no quantity should be passed.
• Password input fields now have dynamic visibility management.
• Added "Current Time" variables in multiple formats to report column mappings in Order Builder.
• When selecting reports for Order Builder, users can now search for the desired report.

Bug Fixes

• Enhanced OAuth 2.0 authentication support in Connections, adding new configuration options, and ensuring Client ID and Client Secret token are properly passed in the headers of the login call.
• Resolved an error where token duration and unit of time were not saving correctly for some Connections.
• Users were unable to remove fields from the Order Builder mapping interface; this was resolved and fields can be removed.
• In Order Builder, after an order was sent to Power Pick, users could edit the Order Name field but not save changes. Editing is no longer enabled if the status is "Sent to Power Pick".
• In Order Builder, Internal Name is now a required field when saving an order.
• Users can no longer manually update Orders created by Order Builder to "Sent to Power Pick".

2.16.0.1

New Features

• Improvements were made to enhance ItemPath's ability to build and deploy our Docker images. There should be no noticeable changes to user experience.