10.0-CAP34.0 (26.05.2023)

Previously, when geo-coding an address, address state ID was used (as input parameter to PTV geo-coding interface). This worked fine in most cases but not in all cases (eg. the geo-coding was working correctly for Swiss addresses, but was not working optimally for Austrian addresses (which were geo-coded with very low matching level accuracy)). Newly, instead of state ID (eg 'N' or 'ZH') the system uses the state description (eg. 'Niederösterreich' or 'Zürich'). Which is working both for Swiss & Austrian addresses.

Previously, in the 'Means of transport type' form, there existed a parameter 'Geo service product', with following options: "None", "PTV xServer [1.x]" and "PTV xServer [2.x]". The parameter gave the impression that it is possible to process different means of transportations via different versions of PTV xServer (or even deactivate the PTV xServer for certain means of transport types). The parameter was actually not respected in the dispatching processes as it lacked further configuration (eg. setup of concurrent interfaces to different PTV xServers etc.). Thus the parameter 'Geo service product' was removed from 'Means of transport type' form.
Newly, the centrally parameterized PTV xServer is used for all means of transport types that do not have 'Timetable linked' activated.

This feature enables the user to setup differentcolors in GPB parameters, for the background of the different values in the columns:Transport type, SLA, Temperature and/or ADR to be shown in the GPB 'Transport orders /-legs' screen. Using thisfunctionality, transport legs with dangerous goods, different transport types, temperature-controlled transport orders and different service level agreement can be more noticeable for thedispatcher when working with the screen in GPB.

Key point:
- Parameterization of colors is done in GPB Parameters (in section 'Transport orders /-legs')

GPB screens and dynamic bar text/title configuration (ie. 'GPB GS text templates' form) were enhanced in the following way:
- to not show duplicated cities, in case the same cities occur next to each other on the tour stop sequence
- new data source 'Resource leg -> Vehicle' was added to 'GPB GS text templates' configuration
- new targe 'Applied on = Level 3 header' was added to 'GPB GS text templates' configuration
- for enum visualization in GPB, the enum value description is shown (previously sometimes the enum id was shown)
- Resource name was sometimes overlapping the side color side ribbon on tour overview (in GPB 'Tour Dispatching' screen)

Following enhancements were done:
- The 'Process' tab (with Sequence optimization options) is now always shown and available
- If 'Tour sequence optimization in real time' main parameter is TRUE, then the 'Sequence optimization' is also set to TRUE by default, and 'Respect business hours' and 'Respect customer wish' options are initialized from parameters
- If user selects a route, then system asks if the user would like to initialize default values from the route. The sequence optimization settings are then also initialized from the route (ie 'Launch sequence optimization' & 'Unload all before load'

Following enhancements were added to the 'Deliver remainder' dialog:
- Automatic re-detection of the chain - as the first step of create/update transport order (directly or via the dialog), the system now re-detect the chain once again, making sure that all elements are linked to the shipment/transport order. Please note that re-detecting the chain happens in both directions.
By this it is ensured that all elements of the chain are identified when the shipment/transport order is created.
- New dialog for the remaining qty validation of the 'Deliver remainder' dialog was introduced for bulk items (also direct delivery bulk). Both when the qty is manually entered and when the Cancel qty button is used. The dialog pops up when the system tries to reduce the transactional qty below the total qty in transportation (confirmed inventory qty when available, inventory qty if confirmed inventory qty is not available).

Previously, after installing the Microsoft update 10.0.34, the CAPcargo module ISV license were misbehaving. Following symptoms were noted:
- When importing a license deployable package via LCS to a D365 system with Microsoft version 10.0.34, CAP solution doesn´t become visible. No warnings or errors can be seen in the deployment logs.
- When importing via command line, we see this warning : 04/27/2023 10:32:26: Warning: method: readISVLicense, message: License value for CAPcargo Transport and Logistics is incorrect.

This issue might lead also to disabling CAPcargo solution in systems where licenses have already been imported successfully.

This task corrects it and CAPcargo module ISV licenses are now compatible with Microsoft update 10.0.34

This task allows to populate a snapshot overview of toursand tour stops of a given date range, in tabular structure. Results can be easily exported, for example to import them to external systems, or to use them off-line (ie. whenhaving an on-call support shift at home).

Key point:
- new inquiry 'On call list' was added to TMS main menu (CAPcargo Transport -> Inquires -> On call list)

Previously, it was not possible to filter/sort by the street name in the load/unload address lookups on the 'Create transport order' dialog (and also on transport order header details form).

If the transport order is defined as ‘temperature controlled’ with the value in the ‘Temperature’ field, such information will be visible in the ‘All transport orders’ grid and in GPB 'Transport orders /-legs' screen. It will be also shown in the ‘Transport order’ form, as well as in ‘Default order’, ‘Pre-order’ and ‘Offer’. Functionality is also be enabled in the Customer portal.
Furthermore, in D365, the user is able to filter, sort and search the values entered in the ‘Temperature’ field. Like this it will be easier for the user to distinguish transport orders/legs that need special temperature conditions during the transportation.

Key points:
- New table/form 'Temperature codes'
- New activation parameter 'Allow temperature-controlled transport orders' in the transport type
- New field 'Temperature' on transport order header (and on transport order creation dialog)
- New column 'Temperature' on the transport order main grid
- Possibility to import transport orders (with 'Temperature' specification) via transport order EDI
- 'Temperature' field was also added to default order, pre-order, offer
- 'Temperature' information was also added to GPB screens and to Customer portal
- Possibility to define record background color for different temperatures in GPB (more information in color concept task 95373)

This tasks enhances the handling of dimensions in the TMS. Previously it was not possible to enter goods dimensions on order line. Now this is possible to enter length, width and height on order line (incl. measurement unit like cm).

The affected elements are transport order create, transport order line, order line import, default orders. Copy order (and its return order equivalent) will also copy the dimensions on order line if available.

Having the order line dimensions allows us also finally to calculate the plan unit which represents a volume (m3) for example.
Furthermore, the dimensions on the order line act as a vehicle to initialize the dimensions and measurement units in the package creation dialogue. Lastly, its possible to initialize package unit from the transport unit, instead of a generic parameter which was for most customers too limiting.

When a tour stop address is changed, the empties transactions on the tour stop are not handled correctly. They point to the tour line via TourId, TourLineId and AddressId, but the link breaks when address is changed. The transactions still stay in the database, but are not shown in Tour confirmation because the link is broken. They are however still shown in Driver app because there was no change in the Empties transaction.

Previously, for transport orders that were created via shipment builder (and their shipment building area is Sales order - Non WHS or Sales return order), then the trade order type was printed as suffix to the product name (eg. "Monitors - Return"). This was corrected and trade order type is now removed from item name and is now printed before the product name (eg. "Sales order - Monitors"). Also the trade order type is now used as a source, instead of shipment building area.

Following points were corrected in the transport order create dialog, in 'Passenger' tab:
- if a passenger can be selected directly in the lookup, this one shall be taken (and no need to select it via Passenger Search form). So design now allows a direct selection or to go via Passenger Search form.
- if selected via Passenger Search form, the earlier selected passenger should be taken
- "Create new passenger" button was moved next to the identification field
- if customer account is added after the passenger selection, both passenger name & identification ID are also removed (previously only identification ID was removed)

In Passenger form:
- Form pattern was changed, to be able to show more information in the left side grid overview section

Previously, when deactivating or deleting a contact person (that was already assigned to some existing transport order), then these transport orders could not be further anyhow modified/updated, as the validation prevented the saving of modified transport order. This was corrected in the following way:
- Deactivated contact person does not anymore block the change of existing transport orders (that has this contact person assigned)
- Deletion of contact person (in master data) is newly possible only when contact person is not assigned on any transport order