- Documentation
- Product Updates
- 2.15.3
Version 2
-
2.16
-
2.15
-
2.14
-
2.13
-
2.12
-
2.11
-
2.10
-
2.9
-
2.8
-
2.7
-
2.6
-
2.5
-
2.4
-
2.3
-
2.2
-
2.1
-
2.0
-
1.3
-
1.2
2.15.3 - Security Improvements
October 24, 2024
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.