What's new in version 2601.3.0.0

Enhancements/Modifications

With this release of the Aptean Transport extension,

• You can define how long to retain skipped transport requests using the Skipped Requests Deletion DF field on the Transport Setup page. This field specifies the age (for example, 1 week or 1 month) after which the system deletes skipped requests automatically. To know more, see Set up transport.

• The system automatically deletes skipped transport requests based on the retention period defined in the Skipped Requests Deletion field on the Transport Setup page. It removes requests with a Skipped status, no transport order assignment, and a fully posted and deleted source document using the Delete Skipped Transport Requests report, which can be scheduled through a Job Queue entry.

UI/UX changes

The Skipped Requests Deletion field has been added to the Transport Setup page.

Resolved issues

The following issues have been resolved in this release.

ID	Description
361197	The system incorrectly assigns the route code on the Sales Order page when a customer is assigned to multiple transport routes for different days of the week. This issue occurs when the Auto-calculate Shipment Date toggle on the Transport Setup page is turned on, the system evaluates only the first matching route assignment and does not consider other routes that may be valid for the shipment day.
357941	The system does not validate the relationship between the Shipment Date and Delivery Date in the Sales Order page. It currently allows the Shipment Date to be set to a value later than the Delivery Date, resulting in inconsistent date data within the order.
356693	The system fails to delete transport planning lines with status Skipped from the Transport Planning page where the source document is fully posted and removed.