2.18 Summary

New Features

• Data Push and Data Pull now manage mappings better by tracking the positions of mappings and automatically reordering them after removing a mapping.

Bug Fixes

• Reports with the batch line theme now prevent users from adding these material columns: Material Net Quantity, Material Pick Quantity, Material Put Quantity. These columns could cause issues with batch line reports.
• Fixed an issue where form elements initially displayed IDs instead of values.
• Fixed an issue where duplicate transactions appeared when viewing failed transactions in Data Push.

New Features

• Data Push — Awaiting Approval view improvements:
  •  Changed "Requested Quantity" to "Confirmed Quantity". 
  • The "Material Name" now links to the corresponding material in Explorer. 
  • Improved the accordion indicator UI. 
  • The "Transaction ID" column now changes to "Order ID" based on the Consolidate Transactions setting (from the Data Push integration settings).
• Array and Grouping mappings are now collapsible.  

Bug Fixes

• Fixed an issue where the cached default warehouse value didn't update when changed in the Settings menu. This caused orders without specified warehouse information to be assigned to the previous default warehouse. Improved cache functionality to resolve this. 
• Resolved an error that occurred when passing status=queued as a parameter on a LIST request for the Work Order Line and Order Line endpoints. 
• Fixed an error that prevented error messages from appearing when saving an expired ItemPath license.

2.18.1.0

New Features

Workflows

• When workflows create files from a report, the log entry now includes a green arrow that links to the report's Export tab

  

Order Builder

• When creating order lines using the Builder tab:
  • You can now assign a Cost Center to an Order Line.
  • You can now search by the Material Name or Info1 fields.
• The Warehouse Name is now displayed instead of Warehouse ID in the Order Details section.

Data Push

• Data Push Mappings now support Array and Boolean mapping types. Array mappings do not require a key.
• The UI of the transaction list under "Awaiting Approval" has been updated to display additional fields in an expandable section:
  • Order Line Number (this links to the Explorer page for the Order Line)
  • Material Name
  • Requested Quantity
  • Deviated Quantity
• Text mappings in Data Push now include a "Private" checkbox. When selected, this masks the mapped value in the user interface.

Reports

• ItemPath now includes a Batch Line report theme.

• Reports now support adding multiple columns in a single "Add" action. When selecting columns to add, use checkboxes to select multiple columns. If you select a report theme, all columns from that theme will be added.

  

• The Report creation form now dynamically assigns positions to new columns based on their order..

Batch API Endpoint

• The LIST endpoint for Batches is now filterable by creationDate, deadline, and priority.
• Batch type 1 is now available for creation, as well as Batch type 2.

Bug Fixes

• Resolved an issue where an error occurred when a user attempted to update a batch name to its current name via the API.
• Resolved an issue that resulted in an error when updating a batch's deadline via the API.
• Updating an email attachment action in a workflow would fail if the parent action was also being updated. This was resolved by improving the update process to ensure actions are applied correctly.
• If a workflow generated files, it could not be deleted. This was resolved, and you can now delete workflows that have generated files.
• Transactions with an export state of 12 did not render in the Awaiting Approval table of Data Push. This occurred due to the filter management logic, which we have corrected.
• An error occurred when fetching queued orders due to changes in the Work Order Line model. This has been resolved by updating the appropriate queries.
• An error prevented adding additional grouping properties when importing/exporting report themes. This was resolved by improving associated importing functions and schemas. Import/export functions now work correctly with multiple groups
• Report themes were displaying incorrectly for some themes. This was updated to correctly display Report Theme names.

2.18.1.1

Bug Fixes

• Fixed an error in Order Builder that occurred when loading iFields by adding index checks before loading fields.

2.18.1.2

Bug Fixes

• Improved error handling when a user enters an incorrect license for ItemPath.
• Fixed a cache issue where the warehouse limit cache was being retrieved searching for the default warehouse. This would result in errors when creating orders without passing warehouse information. A new key prefix prevents the error from occurring in the future.

2.18.0.0

New Features

New features are available in Connections, Data Pull, Order Builder, Reports, and Variance:

Connections

• Values for private headers are now hidden with * marks after you enter the header value.

Data Pull

• You can now set how frequently Data Pull integrations fetch data from external systems. This is currently available as a global setting for the Data Pull app, available in Settings > Apps > Data Pull. By default, Data Pull fetches data every 10 seconds.

Order Builder

• You can now select the location identification type and add multiple locations based on ID or name.
• The schema for creating count orders via Order Builder has been expanded: If location data is passed in the order body, order lines are no longer required. Instead, order lines are generated based on the location information passed. ItemPath then creates a line for each location specified.
• Work orders and work order lines are created as part of this method.

Reports

• Grouping by date range is now available for Reports. When you select a date column to group by, new input options appear to specify the unit (hours, minutes, etc.). Note that the "floor" time value from the range is used in the resulting rows (for example, "1:00 PM – 1:59 PM" appears as "1:00 PM" in the resulting group row).

Variance

• The Variance app has been enhanced to better support different connection types:
  • The SQL Table option appears only if the connection is a SQL connection.
  • For REST or GraphQL connections, you can now specify Path (URL path for the endpoint), Verify (whether SSL certificates are enabled), and Timeout (number of seconds before the connection times out) properties.

Bug Fixes

• Applying a filter to a count column sometimes caused slow report loading times or failed to be applied altogether. This issue has been corrected by adjusting how filters and count columns are applied.
• Integers produced by count columns included in comparison columns resulted in N/A or blank values. This issue has been corrected by adjusting how Reports handles comparisons and counts.
• When modifying the headers for a connection, the validation check ran if no values were applied to the text boxes. This has been adjusted so it shows only when you select Create a Header.
• Cookie-based authentication failed when cookie keys specified in the connection settings didn't match the cookie returned from the external connection. This occurred because of a failure to properly re-fetch cookies after expiration. This was resolved with improved error handling and authentication checks.

Removed Features

• The Order creation mode in Order Builder is no longer available. Previously, this mode created one order per report row.

2.18.0.1

New Features

• Data Push now includes a maximum records setting that lets you control the maximum number of records processed per second. This can be helpful when working with larger datasets.
• Workflow log descriptions now include a report ID (if an event is generated from a report).
• A database qualifier setting is now available for IBM DB2 connections. This qualifier specifies the database schemas (libraries) to include in the search path for this query.

Bug Fixes

• When using workflows to send email, an error in action order prevented attachments from being added to the email. By adjusting workflow processing, child actions are now correctly associated with parent workflows, ensuring that attachments are added to the email.