2.15 Summary

2.15.3.0

New Features

• Enhanced security and improved error handling in encryption management.
• The API will now return an error if the user tries to update any of the following fields of a history record:
  • orderId
  • orderLineId
  • orderName
  • binName
  • locationName
  • batchName
  • carrierName
  • shelfName
  • warehouseName
  • storageUnitName
  • materialName
  • stationName
  • costCenterName
  • userName
• The Show Location (/api/locations/[id]) endpoint now returns a "contents" key, which is a nested array of Location Contents belonging to that Location.
• In Data Pull SQL database integrations, users are now restricted to alphanumeric characters and underscores when defining a column mapping to prevent SQL injection.

Bug Fixes

• Resolved an error preventing the query client from updating after saving a mapping change in Data Pull.

2.15.3.1

Bug Fixes

• Resolved an issue that would prevent some Data Pull integrations from automatically running when turned on.

   

2.15.3.2

New Features

• Enhanced security and error handling for credentials relating to email and SMS functions

Bug Fixes

• In Data Pull integrations using advanced mappings, an issue occurred due to how ItemPath was handling trailing whitespaces in strings, resulting in a "Material [ID] is not valid" error message. The mapping process now removes trailing whitespaces, resolving the error.

   

2.15.3.3

Bug Fixes

• Additional improvements to the handling of trailing whitespaces in Data Pull mapping functionality.

New Features

• The Mappings tab in Data Push and Data Pull now includes updated drag-and-drop functionality.
• Reports can now be filtered by related app (for example, Variance).
• Added a tool tip explaining the "Pending" user status.

Bug  Fixes

• Validation errors on the new user form caused the Save button to become stuck in the submitting state. This behavior prevented users from making corrections and resubmitting the form. The Save button now resets correctly, which allows users to easily fix errors and resubmit the form.
• Date filters in a report were using integer comparison operators (is, not, greater than, etc.). This has been updated to use date comparison operators (before, after, days ago, etc.).
• Resolved an issue that prevented left, right, and outer joins from being properly completed by the Variance app.

2.15.1.0

New Features

Drag and Drop

• Enhanced drag and drop functionality in the application, introducing a new drag icon to better indicate the option when available (for example, in the Report columns interface).

Reports

• The "Location Count" (number of items of a Material in a location) report column type is now available in the following themes:
  • History
  • Job Line
  • Kit Line
  • Location Content
  • Location Content Breakdown
  • Order Line
  • Storage Rule
• Added validations for creating comparison columns:
  • Comparisons of string columns are no longer allowed
  • A column cannot be compared to itself

Settings

• Added a feature to assign full access to roles in user management. Roles must have a unique name.

Bug Fixes

• Activating/deactivating a toggle would sometimes update multiple toggles incorrectly when setting permissions for users/roles. This was corrected through introducing improved asynchronous handling on permission switch changes, so that only dependent settings would update.
• When editing an existing comparison column filter that compares date-time, report filters failed to show all the available settings for comparison columns. We enhanced the rendering logic to accommodate this case so that settings will properly appear. 

2.15.1.1

New Features

• Added new functions for order and line data validation in Order Builder.
• Improved integration handling logic for data processing in Order Builder.
• Improved the user interface for Order Status selection with clearer placeholder text.

Bug Fixes

• In Data Pull, grouping "flat" data structures by a mapping that contains a space would result in an error. A check and a safeguard were added to the logic allows ItemPath to perform aggregate calculations conditionally, and logs a warning if an Order Line mapping does not exist in the data.

2.15.1.2

Bug Fixes

• An issue occurred with grouping functionality when attempting to call columns that didn't exist. The way the back-end processes data was adjusted to ensure that only existing columns are handled.

New Features

Data Pull

• Added an integration type for deleting Orders based on status. This includes the new functionality for mapping and conditionally deleting Orders, the introduction of a new drop down for selecting Order creation or deletion types, and improved settings visibility based on the selected type.
• The Order deletion integration type will return an API call confirming the deletion.
• Added a "No Structure" option in the settings for data mappings, allowing users to select a flat mapping configuration. This will flatten nested structures, bring all fields to the same level.

Orders

• Enhanced the Order interface in Explorer to provide a clearer representation of Order timelines (using the modifiedDate field instead of createdDate).
• Updated the Descriptions section to accept more complex content types, allowing for richer data display.

Time zones

• Enhanced the user experience in forms by allowing the timeZone field to be optional.
• Implemented dynamic time zone retrieval for user forms, pre-filling the time zone based on the user's system settings.
• Added functionality to clear time zone selections in forms.

Variance

• Introduced new grouping and filtering capabilities in reports, allowing users to specify additional grouping columns and filter groups.
• Added support for enhanced join conditions (allowing for OR joins). 
• Introduced a new caching mechanism for managing integration jobs, including support for triggers in the integration component and a scheduling option for integration tasks every 20 seconds.
• Added an "advanced" mapping type option in the Mapping component.
• Introduced new comparison operators for filters in the variance report, allowing for "starts with", "ends with", and "includes" filtering.

Bug Fixes

General

• References to stale data would cause issues during report deletion, the report deletion function was modified to resolve this issue.
• If a user uses the back button in their browser from the 404 page, they would be redirected to the 404 page a second time.  The back button will take users back one additional step in their browser history, preventing the redirect from occurring.
• Orders would display incorrect dates, adjusted which field was used to display the Creation Date to ensure accurate data is displayed to users.

Data Pull

• Improved response messages when running data pull order deletion, adding a success indicator for deletion operations in the output results.
• Resolved an issue when flattening material data using material data would not be applied by enhancing the data processing logic.

Variance

• Resolved an issue where Left, Right and Outer join conditions were not properly joining tables.
• Filters on Variance report columns would not be applied if there is no data that can be joined. This was resolved by adding a step to collect all Variance columns, adjusting the filtering accordingly.

Patch 2.15.0.2

Bug Fixes

• Token based authentication would not properly refresh if the Last Updated column is empty, the internal calculation for refresh periods was improved to resolve this issue.

Patch 2.15.0.1

• New comparison operators are available in reports:
  • Sum
  • Ratio
  • Percentage
  • Modulus (yields the remainder)
  • Product