67704

POMS

Forwarding Order Persistence Error

Under certain circumstances, a newly created Forwarding Order was not stored correctly. This has been fixed.

64989

Air,Export

Inexplicable Consolidation Effects

When multiple users change a consolidation quasi-simultaneously, Scope's behavior is not immediately transparent to all users participating in this situation. This leads to errors and irritation. Scope is now making sure, all users have the same view on "the reality" of the current consolidation.

64235

Ordertracking,POMS

Order Tracking Email Templates: Main Transport Order Parameters for Forwarding Orders

E-Mails generated for Forwarding Orders can contain details about their routing legs.

67560

Warehouse

Handling Shipment: Prevent Recursive Consolidation

Scope prevents users from creating recursive consolidations of Handling Shipments.

64798

Forwarding,Sea

Sea: Show Port of Loading / Port of Discharge (Sea Ports)

Scope allows capturing of non-sea legs in the main transport order to the shipping lines. In the past Scope considered the first origin (last destination) as the port of loading (port of discharge). This is no longer true, so we adjusted the behavior to reflect only the first origin (last destination) of a sea freight leg. However, when communicating with shipping lines over INTTRA or other portals, these legs are not marked correctly from time to time, and users struggled with the way Scope interpreted this data. We have now implemented a more refined approach to dealing with port of loading and port of discharge in these cases.

64798

Forwarding,Sea

Sea: Show Port of Loading / Port of Discharge (Sea Ports)

Scope allows capturing of non-sea legs in the main transport order to the shipping lines. In the past Scope considered the first origin (last destination) as the port of loading (port of discharge). This is no longer true, so we adjusted the behavior to reflect only the first origin (last destination) of a sea freight leg. However, when communicating with shipping lines over INTTRA or other portals, these legs are not marked correctly from time to time, and users struggled with the way Scope interpreted this data. We have now implemented a more refined approach to dealing with port of loading and port of discharge in these cases.